Several packages were updated this week for openSUSE Tumbleweed as was expected after the holiday season. Five snapshots of the rolling release have been delivered so far this week after passing the rigorous testing applied by openQA.

The releases are trending incredibly stable with trending or recorded ratings abovea 96 rating, according to the Tumbleweed snapshot reviewer.

The most recent snapshot, 20200112, updated Xfce desktop environment with an update for xfce4-session 4.14.1 and xfce4-settings 4.14.2. Various developer visible changes were made with Google’s 20200101 re2 library for regular expressions updates. GNOME’s application for managing images with a users Flickr account, frogr 1.6, removed the deprecated use of GTimeVal. The open source platform for the scale-out of public and private cloud storage, glusterfs 7.1, fixed storage rebalancing caused by an input error and fixed a memory leak in the glusterfsd process. ImageMagick version 7.0.9.14 optimized the special effects performance of Fx and virglrenderer 0.8.1, which is a project to investigate the possibility of creating a virtual 3D GPU for use inside qemu virtual machines to accelerate 3D rendering, added some patches. The snapshot continued to update packages for KDE Applications 19.12.1 that started in the 20200111 snapshot. Improvements to the scroll wheel speed was made for KDE’s Dolphin, the video editing software Kdenlive had multiple fixes and an adjustment for faster rendering, and obsolete code was removed from Applications’ diagram package umbrello. Most of the KDE Applications packages also updated the Copyright year to 2020.

In addition to the  KDE Applications 19.12.1 packages that began arriving in snapshot 20200111, KDE’s Plasma 5.17.5 also arrived in the snapshot. The updated Plasma fixed a regression in the “Port the pager applet away from QtWidgets” and fixed the drag from Dolphin to a virtual desktop switcher widget. The Plasma NetworkManager also had a fix for a crash when changing advanced IPv4 configurations. The much-anticipated fix for the security vulnerability in Firefox was made with the Mozilla update to Firefox 72.0.1; there were eight Common Vulnerabilities and Exposures (CVE) fixes in the update from the previous 71 version included in Tumbleweed, but the 72.0.1 fixed the bug that hackers could use to access a computer of anyone using the browser because of incorrect alias information in the IonMonkey JIT compiler. LibreOffice 6.4.0.1 added a patch to fix a button that allowed the wrong ordering of a Qt interface and curl 7.68.0 had a lengthy amount of fixes and changes to include adding a BearSSL vtls implementation for the Transport Layer Security (TLS). openSUSE’s snapper 0.8.8 version had a rewrite of a subpackage from Python to C++ and several YaST packages were updated, which included the fixing of an error during an upgrade if /var/lib/YaST2 was missing when using Btrfs.

Troubleshooting tool sysdig was updated in snapshot 20200110; it fixed a memory leak as well as updated the use of Kubernetes APIs to support version 1.16.vMany GNOME packages were updated to version 3.34.3 and the fwupd 1.3.6 package for updating firmware added a new plugin for working with embedded MultiMediaCard (eMMC) devices. A drop of python3-setuptools dependencies from rpm-build was made with the update of rpm 4.15.1 and Optimized Inner Loop Runtime Compiler (orc) 0.4.31 fixed various PowerPC issues.

Snapshots 20200109 and 20200108 had a minimal amount of package updates, but the Linux Kernel was updated to version 5.4.7 in the 20200108, which provided a large amount of updates from the previous 5.3.12 kernel Tumbleweed was running. Updates for Btrfs in the kernel were plentiful and there were about a handful of fixes in the kernel for IBM’s s390 and for the file system ext4.

I was in the openSUSE Board for 2 years in the past and I have enjoyed this time to bring along the openSUSE project.
I want to run for the openSUSE Board again after a short break about 1 year. I am happy that the existing openSUSE Board has proceeded my idea with the foundation so successfully. But I would be happy about being allowed to finalize this/ my topic together with the other Board Members as my old idea.
Additionally, I have watched the decreasing reputation. Public representations of openSUSE have been missing by the openSUSE Board in the last year. I would increase that on the same way I have done that at our university.

My main activity at openSUSE is the Coordination of the global Localization Team besides my studies. However, that is not the sole task. I contribute to QA, give presentations, update the wiki (English and German) and create PRs on Github. I would be able to contribute some code as a Computer Scientist, too. But SUSE does not want to see any Computer Scientists from our university. Therefore, my focus is on improving our study plan with open source development.

I love to represent openSUSE. So I have decided to run for reelection.

Do you want to know more about my goals and thoughts? You can find more about my goals for these openSUSE Board elections on my openSUSE Board election platform.

Email: sarah.kriesch@opensuse.org

Blog: https://sarah-julia-kriesch.eu (my blog)

facebook: https://www.facebook.com/sarahjulia.kriesch

LinkedIn: https://www.linkedin.com/in/sarah-julia-kriesch-16874b82

Connect: https://connect.opensuse.org//pg/profile/AdaLovelace

I wish all candidates good luck, and hope that we‘ll see lots of voters!

• 
• 
• 
• 

The post Running for the openSUSE Board again or: reelect (Sarah); first appeared on Sarah Julia Kriesch.

I recently purchased a new Logitech wireless keyboard for my kitchen computer because the Bluetooth keyboard I previously used was driving me nuts. Mostly for the keyboard layout and sometimes because it didn’t want to connect. Possibly due to hardware failure or bad design. It also doesn’t have media keys so I thought it best … Continue reading Solaar | Application for Logitech Unifying Receivers and Devices on openSUSE →

The title describes everything. This is not only for FOSS conferences but events in general. Attending a conference means to meeting friends (usually you meet once a year) and have fun in general.

The organizers are responsible for everything that happens during the conference hours. We are grown people, so we have to be responsible for the rest of the day. Sometimes bad things might happen (bad: the critical meaning is health issues). Although the organizers aren't responsible for that, they are the key people, who know the system in their country and it's a good and human thing to help the person with the problem. Everyone wants to have fun and be happy at the end of the conference.

Being an organizer and volunteer, I felt the frustration of having everything covered. I lived a couple of times the health crisis during the conference.

Here are some points to cover before and during the conference. Please leave a comment if you want to share your experience.

Before the conference:

0. If the conference takes place within European Union, you can ask the European citizens to get the European Insurance Card. It doesn't cover everything, but at least you'll avoid some stupid bureaucracy. If they're not EU citizens or they don't have insurance, ask them to buy one for their trip. Usually, when you buy a plane ticket, they suggest buying medical insurance. Do it, because it will save you from a lot of trouble.

1. During the online registration, ask for emergency contact (ask for a name and phone number). It will help you and doctors just in case they need the medical history of the person, allergies, etc.

2. If they're not feeling comfortable providing their name and number, ask them to enable a feature of emergency call on their phone or even better to install a program with the emergency call and some medical history and their medication. Personally, I have the Medical ID (Free) installed (you can choose other). It will help the doctors because it has a field to add your medical history so they can treat you correctly.

3. This might be very personal, but ask them to enter where they will stay. You might need to go to their hotel and bring a special medication they "forgot" to bring with them. And that leads to another issue. Ask them to bring the medication to the conference with them.

4. During registration, it's good to have a field for write down a disease that the attendee feels comfortable sharing. There is a code of conduct committee that can guarantee this information. For example, if the attendee has epilepsy, it's good for the organizers to know and be prepared. Usually, people with epilepsy tell that information to their friends, so they won't be surprised just in case of a seizure.

5. During registration, ask for special types of food. It's not the only religion that prohibits some kinds of food but there are some other categories such as vegan, vegetarian, gluten-free, etc. Some of them are just a way of life but others are health-related.

6. Gather information and write on the website everything health-related that the attendees must know because usually there are some illnesses that come up after the attendees return back home. A special quote is if there are special vaccines that the attendees have to be vaccinated. It's better for the locals to write down

7. Gather information and write on the website what everyone has to be careful about. Examples are, don't drink tap water, buy water from kiosks and that costs ..., don't walk alone after midnight at that place because you might get robbed, smoking pot is illegal, traffic police violations. Find out what the attendees need to know so they won't end up either at the hospital or police station.

8. Every country has a different health system. Make sure that you find out the hospitals that accept emergencies and also the pharmacies that are open during the night. Make a list with details (address, phone number, specialties, etc) for the days of the conference. It's better not to use it rather not have it at all.

9. Gather all addresses and phone numbers of embassies and consulates of the attendees. It's the place they have to call if they have a problem and there are people who speak the same language that can help them.

10. On the name tags, write down the emergency phone numbers (like 112). In my country it's different for the police, fire department, ambulance. Also, buy a disposable cell phone number and put the number on the name tags, so attendees can call a local that knows the system and can help.

11. Contact Red Cross volunteers. I guess there are different organizations for every country. You can search for their information. They might be present during the conference for free. They are people with jobs and they are volunteers, so if they cannot join you, ask them to train someone for some basics.

12. Write a document "Protocol if we have to call the authorities". That includes everything from fire to ambulance and from the police to traffic police. Of course, you cannot include everything (because you never know) but at least you can act for some basic situations.

During the conference:

1. Keep a central booth for Red Cross volunteers. They usually carry a bag with heavy equipment. Ask them how they want to have communication for emergencies. Usually, many venues have defibrillators (I think it's called like that). So help them to find one. Ask the volunteers what else they need to operate. Don't forget they are volunteers, so please make sure they have free food and water, and maybe you can give them a T-shirt of your project for free.

2. Make sure you have a private room that the Red Cross volunteers can examine someone. That can be an office. Nothing fancy. Usually, people don't like to be examined in public. Also, the Red Cross Volunteers are more concentrated when the place is quiet.

3. If you don't have a Red Cross volunteer, try to train someone or find a key person (name and phone number) who knows CPR, how to use a defibrillator, etc. He might save a life before the ambulance arrives.

4. Have an Emergency mobile number that an attendee can call you when he faces a problem. Have in mind that everything will happen during the night (because people tend to do stupid things during the night). So be prepared to go to the police (got robbed or had a fight with a local etc), go to a hospital (got hit by a local or got a bicycle and fell, etc). As I wrote, the organizers aren't responsible for what happens after the conference hours. But leaving someone who doesn't know how the foreign system works, will be bad for you and the organization in general. So make shifts for locals on-call :-)

5. Try to pass everything as quietly as you can. It's not good to make a fuss out of the incident. The person with the problem doesn't like everyone to see and ask if he's OK or feel pity for him. That's why the private room helps.


If you have an idea that I forgot, please leave a comment. Please share it with people that organize conferences because it might give them some tips.

Some of the above ideas are overdone. It's better to be prepared rather than be stressed.
I hope following all or some of the above will lead you to a successful conference.

Low genetic differentiation despite high fragmentation in the endemic serpentinophyte Minuartia smejkalii (M. verna agg., Caryophyllaceae) revealed by RADSeq SNP markers vojta Po, 01/13/2020 - 10:46

Fedora is a Linux distribution that has been around since the beginning of my Linux adventure and for which I have incredible respect. I have reviewed Fedora before, and it was a good experience. Last time I used Fedora, I used Gnome and since I am kind of Gnome fatigued right now, I thought it … Continue reading Fedora 31 | Review from an openSUSE User →

The killer feature of the Plasma Desktop has been the KDE Personal Information Manager, Kontact. I have been using it since 2004 time frame and although we have had a tenuous relationship over the years, specifically the switch to the Akonadi and the pain that came with it in the early years. I actively use … Continue reading Kontact | Akonadi Reference →

Komunitas openSUSE Indonesia (openSUSE-ID) mengucapkan terima kasih atas antusiasme peserta pada #KuisLiburan2019 kali ini. Dari 127 jawaban yang masuk, kami harus mengkurasi jawaban yang salah maupun kurang tepat. Tersaring 42 jawaban yang tepat dan kami harus mengundi lagi untuk menentukan siapa peserta yang beruntung. Peserta yang beruntung adalah sebagai berikut.

Peserta yang beruntung untuk mendapatkan new SSD 120 GB adalah Sabilil Maromi.

sementara untuk peserta berikut mendapatkan bingkisan menarik dari openSUSE ID

• Arif Setyo Nugroho
• abi permana
• Heru Juwardi
• Aji Revaldi
• Surya Handika Putratama
• Yaumul Majid
• Muhammad Rofi
• Wuri Nugrahadi
• Arif Dermawan
• A Mu’ammar Afinas
• Rizal Amrr
• abdi weef
• Kristian Valent
• Rokib Munawir
• Satrio Adi Prawiro
• iqbalfr@nevtik.org
• gatoti
• lazuardi senja
• Muhamad Andhika Prasetya

Diharapkan kepada seluruh pemenang untuk mengirimkan informasi alamat dan nomor handphone di tautan berikut ini selambatnya tanggal 14 Januari 2020, jika sampai waktu tersebut tidak mengisi form pemenang maka hadiah dinyatakan hangus.

Bingkisan menarik akan dikirimkan oleh tim openSUSE-ID secara gratis! Jangan lupa bagi para pemenang untuk memposting bingkisan tersebut ke media sosial dengan tagar #KuisLiburan2019 #openSUSE dan mention ke @openSUSE dan @openSUSEID (di Twitter).

Selamat dan sampai jumpa lagi di Kuis berikutnya!

Salam,

Coming back strong in 2020… no… not coming back… I haven’t been gone, just delayed. 12th Noodling, a dozen, a foot or a cup and a half of crap? AMD System from Yester-Years Parts I recently posted about my computer build. In short, this is a computer build on parts that are in no way … Continue reading Noodlings 12 | Lighting the Emby Server with Kdenlive →