A total of four openSUSE Tumbleweed snapshots were delivered this week to rolling release users.

Tumbleweed has consistently been releasing daily snapshots; a four-day period between two snapshots this week is the longest duration between snapshots since the fall of last year. Impressive.

The most recent snapshot, 20220330, updated just one package. The tiny update of perl-Mojolicious to version 9.23 enabled gzip compression by default with the Mojolicious renderer.

Snapshot 20220329 has several packages. Among the packages to update in the snapshot was ibus 1.5.26. The intelligent input bus for Linux enhanced Emoji features, enhanced compose keys and fixed the forward key keycode for GTK4. An update of strace 5.17, which is a diagnostic, debugging and instructional userspace, made some improvements and implemented a few decoding commands. Linux Bluetooth protocol bluez 5.64 removed a patch and created a fix for building with old glibc. The update of the INI file parser by kiwi Ben Hoyt to inih 55 improved the quality of shared objects by explicitly defining symbol visibility; it was updated from version 53. The snapshot also brought several Python Package Index updates. Two of those were python-cryptography 36.0.2, which updated operating systems to compile with OpenSSL 1.1.1n, and toolkit python-ipython 8.2.0, which allows auto-suggestion.

Updates of sudo and systemd came in snapshot 20220328. The 250.4 systemd copies holes when archiving Btrfs journal files and explicitly handles file systems that do not support hole punching. Some new options with sudo 1.9.10 will attempt to prevent passwords from being logged if log_passwords is disabled. Mozilla Firefox 98.0.2 fixed an issue preventing users from typing in address bar after opening a new tab and pressing cmd + enter. It also fixed an issue in session history that caused some sites to fail loading. Text shaping engine harfbuzz 4.1.0 had various bug fixes and libzypp fixed a possible hang. Packages gtk3 3.24.33+12, libsolv 0.7.22, xlockmore 5.69 and glib2 2.72.0 were some of the many to update in the snapshot.

The snapshot starting off the week, which was a day after GNOME 42 landed in Tumbleweed, was 20220324. There were a few 1.20.1 gstreamer packages to update in the snapshot. The GStreamer package fixed a gtk video sink involving a rotation not being applied when paused and various fixes to the webrtc-sendrecv. Text editor vim had a large amount of community contributions moving from version 8.2.4542 to 8.2.4602 and fixed some build failures with a combination of features. Gamers and musicians will appreciate the 0.4.9 pipewire update as surround sound in some games is now exposed properly and some bluetooth features were added and fixed. An update of the filesystem snapshot manager snapper 0.10.0 adjusted a transfer filelist to alleviate the message size for dbus.

Hoy entrada rápida que mi vida se acelera. Os invito a conocer una poco más a fondo el simulador de fí­sica de KDE de la mano de Lista de ví­deos de Step que he encontrado y que me parece interesantes compartir con vosotros. A ver qué os parece.

Lista de vídeos de Step, el simulador de fí­sica de KDE

De la mano de José Pérez he encontrado esta lista de ví­deos de Step en el que podréis encontrar un poco de todo lo que puede hacer esta fabulosa aplicación educativa. Hay que destacar que no es la primera vez que aprece Sep en el blog ya que le he dedicado alguna que otra serie como la de enseñar gráficas MRU y MRUA con él.

¿Qué es Step?

Para los que no lo conozcan , Step, es un simulador de mundos fí­sicos en 2D, con el que podremos recrear la realidad en condiciones controladas.
Con Step se puede, entre otras cosas:

A ver si en un futuro le dedico más tiempo a esta increíble aplicación que, lamentablemente, parece que está necesitada de algo de amor pero que tiene un potencial fabuloso tanto a nivel de secundaria como en cursos superiores.

La entrada Lista de ví­deos de Step, el simulador de fí­sica de KDE se publicó primero en KDE Blog.

My favorite and most used service for developers is the openSUSE Build Service (OBS). This is where I build syslog-ng packages first, before anywhere else. OBS is open source, highly flexible software to build software packages, and the instance at https://build.opensuse.org/ is free to use for anyone to build open source software. Best of all, it supports multiple architectures, including POWER.

Open Build Service

Actually the OBS acronym stands for two things. The software itself is called Open Build Service. It is open source and you are free to install it on your own network. You can use it to compile any software you like. The openSUSE Build Service is a public OBS instance. It is accessible to any registered user to build open source software.

OBS can be used not just to compile individual software packages, but to maintain and publish complete repositories. It can also build various images from the software compiled: both ISO images and disk images for different virtualization solutions.

The original focus of OBS was i586 and openSUSE. Soon other architectures and Linux distributions were introduced to OBS. While I only use it for openSUSE and SLES packages, many more are supported, including Fedora, RHEL, Ubuntu, Arch, even Raspbian on x86, ARM and POWER.

You can access the OBS both through its web interface and a command line client. In theory you should be able to configure everything from either of them. I tend to use both of them. I configure repositories through the web interface, but submit new builds using the CLI. If you want your software project to get compiled for POWER, it is just a few mouse clicks away. You add a distribution version to your project and then you can configure architectures. If you add an architecture only later, you do not have to re-submit packages as OBS automatically compiles all packages for the new architecture as soon as you click on “update”.

POWER

While the focus of POWER support in OBS is PPC64LE, meaning little endian 64 bit POWER, you can also use it to build both 32 bit and 64 bit big endian POWER architecture packages. There were times when the build capacity for POWER was relatively small. You had to wait long for POWER builds to complete. However, early this year the openSUSE received a huge hardware donation from SUSE and IBM: fast, new IBM POWER 9 servers. Building packages on POWER are blazing fast now, compiles finishing often before any other platforms. You can read the announcement at https://news.opensuse.org/2022/01/25/os-gains-new-hardeware/

If you take a look at https://build.opensuse.org/monitor you can see that there are now close to 300 POWER workers in OBS. 1.5x more than just a couple of months ago. They are often working close to full capacity (most likely when Factory is being rebuilt), but it seems that there are always some resources left free for random incoming jobs from users.

Why OBS?

I keep mentioning, that POWER is just one of the architectures supported by OBS. Then why I write my first blog after introducing myself as an IBM POWER Champion about the openSUSE Build Service? Because it is quite rare that you want to build a software only for a single Linux distribution on POWER. In that case OBS gives you tremendous speed and flexibility: you do a single submit and it gets compiled on a dozen of different Linux distributions and possibly also on a dozen of different architecture variants.

Session recording has been available in sudo for many years, however not many people are aware of it. Even less well-known is that you can save not just the terminal output, but also what the user types. That way you can analyze what the user is doing within a shell session. Recordings may also include user passwords, which is not always desirable. Version 1.9.10 of sudo allows you to hide passwords in session recordings if it recognizes a password entry.

From this blog you will learn how to turn on session recording in sudo, how to enable or disable hiding passwords in session recordings, and how to view the results: https://www.sudo.ws/posts/2022/03/sudo-1.9.10-hiding-passwords-in-session-recordings/

A Decentraland que movimenta compra e venda de terrenos, agora proporcionou um desfile de moda de grandes grifes entre os dias 24 e 27 de março. O Fashion Week ganhou uma versão virtual e imersiva. O espaço recebeu várias marcas, e claro com comercialização de NFT de roupas e acessórios presente nos desfiles. Existe possibilidade de compra de produtos para o mundo virtual e físico, como jaquetas, moletom e outros. A tendência deste mercado é movimentar 50 bilhões de dólares até 2030, segundo a instituição financeira Morgan Stanley.

For people planning on attending the openSUSE Conference 2022 in Nuremberg, Germany, from June 2 – 4, there are certain health and visa requirements that need to be met for travelers.

The openSUSE Conference will follow the Bavarian Ministry of Health’s requirements and posture regarding COVID. An FFP-2 mask and social distancing may be required. These regulations my change before or up to the day of the conference.

Those who are not a citizen of a Schengen country that are planning to attend should view the overview of visa requirements/exemptions for entry into the Federal Republic of Germany, which can be found at the Federal Foreign Office website.

Please note: the Travel Support Program has no provisions to cover the cost of a visa, so it’s the travelers responsibility for covering the additional cost.

For citizens who are not a citizen of a Schengen country, you may need a formal invitation letter that fully explains the nature of your visit. An alphabetical list of people from nations that require an invitation letter can be found on the Federal Foreign Office website. If the letter is needed, please contact the conference organizers.

In this blog post I’m gonna show you, how you can enable https for your openQA instance using dehydrated and the internal SUSE CA. The same procedure should also work for Let’s Encrypt.

There are multiple ways in syslog-ng to limit message rate. The throttle() option of syslog-ng destinations tries to make sure that all messages are delivered without exceeding a specified message rate. The rate-limit() filter introduced in syslog-ng 3.36 drops surplus log messages, making sure that a processing pipeline or destination is not overloaded with log messages.

Read the rest of my blog at https://www.syslog-ng.com/community/b/blog/posts/the-difference-between-throttle-and-rate-limit-in-syslog-ng

Tal y como estaba previsto en el calendario de lanzamiento de los desarrolladores, hoy martes 29 de marzo la Comunidad KDE ha comunicado que ha sido lanzada la cuarta actualización de Plasma 5.24. Una noticia que aunque es esperada y previsible es la demostración palpable del alto grado de implicación de la Comunidad en la mejora continua de este gran entorno de escritorio de Software Libre.

Lanzada la cuarta actualización de Plasma 5.24

No existe Software creado por la humanidad que no contenga errores. Es un hecho incontestable y cuya única solución son las actualizaciones. Es por ello que en el ciclo de desarrollo del software creado por la Comunidad KDE se incluye siempre las fechas de las actualizaciones.

De esta forma, el martes 29 de marzo ha sido lanzada la cuarta actualización de Plasma 5.24, la cual solo trae (que no es poco) soluciones a los bugs encontrados en esta semana de vida del escritorio y mejoras en las traducciones. Es por tanto, una actualización 100% recomendable.

Más información: KDE

Las novedades de Plasma 5.24 LTS

Aún tengo pendiente el resumen de las novedades pero he aquí la lista preliminar de ellas.

• Mejoras en las funciones de KRunner con el asistente de ayuda.
• Desbloqueo de la pantalla y autentificación de las aplicaciones con tus huellas dactilares.
• Nuevo y espectacular fondo de pantalla de Ken Vermette para Plasma 5.24 ?Honeywave?
• Breeze amplía la función que permite elegir los colores de acento (introducida en Plasma 5.23) y ahora permite elegir cualquier color que desee, en caso de que los colores preseleccionados no sean de vuestro agrado.
• El tema por defecto Plasma Breeze ha recibido un refresco visual para que se ajuste más al estilo de Breeze de las aplicaciones, mejorando la coherencia visual entre ellas.

• Para que las notificaciones críticas de Plasma destaquen, ahora vienen con una franja naranja en el lateral para distinguirlas visualmente de los mensajes menos urgentes.
• Muchos widgets han recibido nuevas funciones y mejoras sutiles que mejoran su aspecto, la relevancia de su información y la facilidad para navegar por ellos.
• Los menús contextuales del Administrador de tareas se han aclarado y simplificado.
• Retorno de la la vista general para gestionar todos los escritorios y aplicaciones

• Se han añadido mejoras al Color Nocturno, a la hoja de pruebas de los altavoces en la página de Audio de los Ajustes del Sistema y a la función de límite de carga de la batería.
• Discover da la opción de reiniciar automáticamente después de que se haya completado una actualización., haciendo click en la casilla de verificación situada en la parte inferior de la página de Actualizaciones.
• Wayland continúa a buen ritmo con un gran número de mejoras, como la compatibilidad con colores de más de 8 bits, auriculares de RV con un rendimiento óptimo y tabletas de dibujo.

Más información: KDE

La entrada Lanzada la cuarta actualización de Plasma 5.24 se publicó primero en KDE Blog.

The openSUSE Community is proud to announce its new Code of Conduct as approved by the openSUSE Board.

The openSUSE Code of Conduct was written during several community meetings as a collaborative project and reports were sent to the project mailinglists. The input from the openSUSE community members was sent to the openSUSE Board and discussed at length during two public openSUSE Board meetings.

During the February 28, 2022, public Board Meeting, it was recognized that openSUSE did not have an adequate Code of Conduct; as such, the board asked if any attendees were willing to take the initiave to work with the community to develop one. Through the regulary scheduled community meetings, one was written, and subsequently proposed to the Board.

We hope that by having a clear and concise Code of Conduct for the project that the openSUSE Community can continue to grow and prosper in the years to come.

The openSUSE Code of Conduct can be found at https://en.opensuse.org/Code_of_Conduct.