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

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.

I received a kind donation from a member of the Destination Linux Community, Bill, which has become a fantastic addition to my ensemble of machines doing various jobs, daily. This machine is a Fujitsu Lifebook T725 that was manufactured on or about 2015 based on the documentation available. The BIOS release date on my particular […]

Submitting bug reports related to openSUSE’s traditional release over the years had some abnormalities as reporting bugs for Leap’s distribution had SUSE Linux Enterprise considerations.

As the distribution evolved from the Leap 42.1 hybrid to the binary compatible Leap 15.3 release and exorbitant reporting was necessary. The abnormalities of the process before caused contributors to be unable to see bugs referenced as fixes for SLE, which made it into Leap, but were not able to view them in bugzilla.opensuse.org.

That has now been streamlined, according to an email from Leap release manager Lubos Kocman.

“I’m excited to inform you that the days when developers were struggling to find Public SUSE Linux Enterprise * Bugzilla products (where all bugs are by default visible to the community) are finally over,” Kocman posted to the developer’s mailing list. “Public SLE products can be now seen in the default “Enter new bug” dialog at bugzilla.opensuse.org.”

The change of the bug reporting policy introduced larger utilization and amount of publicly accessible bugs in both Leap and SLE. Bugs against all Leap packages inherited from SLE should be reported in these Public SLE Products.

“We believe that this effort will increase the transparency of what exactly is being fixed in the update for Leap,” he wrote. “As in the past, … most of (the) referenced bugs in patchinfo were simply created as non-public by default. We’re not taking that option away, but rather identified spots where we can be “open” by default. Namely openQA and now all bugs coming from Leap and SLE Beta testers that were not checked as private during creation.”

Leap release manager thanked members of the community for helping and progressing the efforts. The reporting change adds clarity and transparency for contributors.

Dear Tumbleweed users and hackers,

Once again we were able to demonstrate the power of OBS and openQA by allowing the GNOME maintainers to bring the shiny new GNOME 42 into a snapshot ‘the day it is published upstream’. GNOME 42 was released on March 23, 2022, and snapshot 20220323 already contains it. But of course, this is not all that happened during the last week. After all, we had a total of 6 snapshots published (0318…0323).

The main changes in those snapshots include:

• NetworkManager 1.36.2 & 1.36.4
• Linux kernel 5.16.15
• librsvg 2.52.8
• GNOME 42.0
• VLC 3.0.17.3
• Kubernetes 1.23.4 & 1.22.7

There is a change in the build system that might be of general interest: The default builrdoot when building against openSUSE:Factory no longer contains the packages hostname and iputils2. Those have just been carried around for internal requirements of OBS, which are no longer valid. There are a few packages around that blindly relied on those packages being present that might be filing now.

Things that are currently being forged to become ready for consumption are:

• Move ot use Java 17 openjdk instead of Java 11 openjdk by default
• timezone 2022a: causes a failure in a python module; https://github.com/pganssle/zoneinfo/issues/114 any help is welcome
• systemd 250.5
• podman 4.0
• Linux kernel 5.17: another python module failing: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:O/python-psutil/standard/x86_64
• transactional-update 4.0.0 (rc2 is will be shipped)
• GCC 12 work keeps on progressing

openSUSE’s rolling release quickly gave Tumbleweed users the freshly released GNOME 42.

This highly anticipated release from GNOME contributors landed in the 20220323 snapshot.

GNOME 42 has a new global dark User Interface style preference and comes with a redesigned screenshot feature. The core GNOME 42 apps have been ported to GTK4 and provide next generation capabilities. GNOME 42 includes a valuable set of performance improvements like videos now use modern OpenGL widgets with hardware accelerated decoding; the input handling has been significantly enhanced, which results in lower input latency and improved responsiveness. Improvements in how fullscreen apps are rendered result in reduced energy consumption for video playback and increased frame rates for games. VLC 3.0.17.3 was updated in the snapshot and fixed a regression that could cause a lack of audio for adaptive streaming playback. Several other packages updated in the snapshot including NetworkManager 1.36.4, GTK4 4.6.2, webkit2gtk3 2.36.0, yast2-installation 4.4.50 and more.

The previous day’s snapshot, 20220322 provided three package updates. The Ethernet and IP address pairings package arpwatch 3.2 added a configure option to specify the path to sendmail. The aws-cli 1.22.65 updated the spec file and had some Application Programming Interfaces changes like adding an operation for custom plugin deletion DeleteCustomPlugin and adding Hybridcast as an available profile option for Dash Origin Endpoints. The python-pip 22.0.4 package updated; the package is not compatible with Python 3.6 and is not suitable for openSUSE Leap 15. However, the package fixed an issue where pip did not consider dependencies. There were a significant amount of updates from the previous 20.2.4 version that was in the rolling release.

Another three packages were updated in snapshot 20220321. This snapshot provided a minor update for GNU Compiler Collection 11, which had a patch to fix the miscompiling of an embedded premake of game 0 A.D. on i586 processors. The C/C++ code analysis tool cppcheck updated to version 2.7.1. The tool made various checker improvements and added support for container views; the view attribute has been added to the container library tag to specify the class is a view. The lifetime analysis has been updated to use this new attribute to find dangling lifetime containers. The other package to update was rpm-config-SUSE, which changed his version structure and updated from 0.g96 to 20220317.

The snapshots continued to be released over the weekend as snapshot 20220320 updated fifteen packages. This snapshot updated gnome-software to version 41.5 to add several appstream-related fixes; the update also disabled the scroll-by-mouse-wheel on the featured carousel. The update of container-selinux from 2.171.0 to version 2.180.0 provided several added options and allow container domains to be used by user roles. An updated of libstorage-ng 4.4.94 no longer blocks blkdiscard on extended partitions and whois client 5.5.12 updated the .pro top-level domain server. Other notable packages to update were librsvg 2.52.8, python-kiwi 9.24.29, yast2-installation 4.4.49 and more.

The NetworkManager 1.36.2 update in snapshot 20220319 now loads all the known plugins found in the plugin directory. NetworkManager also converted iproute2 and iputils from requires to recommends. Flatpak 1.12.7 updated in the snapshot and has a change that will allow apps built with Flatpak 1.13.x to export AppStream metadata in share/metainfo, which might be discussed in the upcoming Linux App Summit. The 5.16.15 Linux Kernel appears to have provided a few arm fixes and listed a fix for CVE-2022-0886, which is a duplicate of CVE-2022-27666.

The snapshot that started the week last Friday was 20220318. The snapshot reverted rubygem-formatador from 1.1.0 to 0.3.0. There was a cargo.lock update int he gstreamer-plugins-rs 0.8.2 release and several hundred translation were made in the sixth month desktop-translations 84.87.20220316 update 9301f89b. Other updates in the snapshot included fwupd-efi 1.2, p11-kit 0.24.1 and yast2-packager 4.4.26.

Quite a few people asked me recently how I deal with anxiety. I seem to be less anxious than people around me. First of all: I also have anxiety, just like anybody else. The recent company acquisition & reorganization, the COVID-19 pandemic, the upcoming general elections, or the Russian attack all make sure that once a problem is over, there is a new problem already to worry about. However, sport, music and spending less time reading the news all help to keep my anxiety at bay.

Disclaimer: I’m not a medical expert. I just share my own experiences. I can only guess why these work for me, but I enjoy the results. Your mileage may vary.

Music

Let’s start with a less obvious one: music. It seems to help both when music is just put in the background and also when listening to music without doing anything else.

When I play music in the background, it helps focusing on what I’m working on in multiple ways. It keeps noises out, so there are less distractions. It also keeps part of the mind busy, so my mind has less capacity to think about the problems, and thus anxiety is reduced.

I also like listening to music not as background noise, but as a focused activity. In the first few minutes, I still might think about problems, current events, but then music takes over. When focusing on music, I can always hear new details even in songs I listened to hundreds of times already. Listening to music also clears my mind. And it seems to have a long-lasting effect, as I feel refreshed even hours after listening to music.

Sport

Doing some kind of sport regularly also seems to reduce anxiety levels. Of course, I can rarely do some kind of sport each and every day, but I still try to exercise. Half an hour for five days a week seems to be an achievable goal. And you do not have to think about anything special or needing lots of preparation, just something like walking or biking for half an hour in the neighborhood. When it’s too cold or raining, just jump on the exercise bike. My favorite activity is hiking. It needs a bit more preparation: driving there and driving back. But this is also the most rewarding one, thanks to the fresh air far away from the city.

Doing sports regularly helps to improve anxiety-related problems, like blood pressure and heart rate. Better physical condition also seems to reduce anxiety. As an added bonus, all these activities help to control weight as well :-)

And a few more obvious tips

I am a news maniac. I was reading the news whenever I had a little time. Not anymore. I can follow the reactions of my body when reading the news from Ukraine and it is brutal. My blood pressure and heart rate improved drastically when I skipped reading the news completely for days. Just reading the headlines and even those just 2-3 times a day allowed my situation to improve. Going back to the old me and reading everything for two days canceled the effects of two weeks of slow improvements. Reading the news is not worth your health. Donating to a charity organization helping Ukrainian refugees instead can help your anxiety a bit, and also the people in need.

Leaving social media behind as much as possible can help as well. Up until a few weeks ago, we were surrounded by COVID experts. The unfortunate events in the Ukraine changed this. One of the most unpleasant experiences is when a friend whom you admire for his technical knowledge suddenly starts pushing Russian war propaganda. Luckily, the last US elections taught me to spend less time reading Facebook and Twitter. Instead of reading the feeds, I started to just sample them. I try to post hiking and flower photos to break the constant feed of terrible news, and I got plenty of feedback that it helps those people who still read most of the posts.

I hope that my tips and tricks helped you a bit. However, remember to see a doctor if you cannot handle your anxiety!

Most of syslog-ng works perfectly well on MacOS; however, there is no native driver to collect local log messages. Due to this, in the past, the system() source did not work on MacOS, thus the default syslog-ng configuration failed to start. Version 3.36 of syslog-ng includes a workaround: it follows /var/log/system.log.

You can read the rest of my blog at https://www.syslog-ng.com/community/b/blog/posts/the-system-source-of-syslog-ng-now-also-works-on-macos