[Stable Update] 2022-09-12 - Kernels, LibreOffice, KDE Gear, KDE Frameworks, Firefox, Thunderbird, Pipewire, Mesa

Announcements Stable Updates
,
160

An empty desktop environment and plasmashell using 100% of cpu.

Manjaro KDE with two panels. (one fixed on right, one autohide on left)
After update, found an empty desktop environment and plasmashell using 100% of cpu.
Wallpaper was present, but no icons. Outlines of panels, but no buttons or widgets.
Completely blank and not responsive to any clicks.
Various attempts at restarting kwin and plasmashell, clearing cache, logging off/on, rebooting etc… did not fix.
By using krunner, kupfer, and konsole, I kept the somewhat hobbled DE running in a regular use pattern until I had time to fix it.

My fix was to remove all plasmashell configuration files and restart.
Resulting in a vanilla plasma panel at the bottom.
+30mins~ to manually reconfigure.

161

I don’t know why, but my Thinkpad started not to boot after this upgrade. Once I typed the LUKS password, I got a black screen with a blinking cursor.
According to the journalctl:

Sep 14 22:54:01 rotor gnome-session-binary[1131]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Sep 14 22:54:01 rotor gnome-session-binary[1131]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Sep 14 22:54:01 rotor gnome-session-binary[1131]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep 14 22:54:01 rotor gdm-launch-environment][1081]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:01 rotor gdm-launch-environment][1154]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:01 rotor gdm-launch-environment][1191]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:01 rotor gdm-launch-environment][1242]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:01 rotor gdm-launch-environment][1293]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:01 rotor gdm-launch-environment][1317]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 14 22:54:27 rotor kernel: watchdog: watchdog0: watchdog did not stop!

Once I removed the splash option from the grub config (and run update-grub) the problem was gone, so the issue is somehow around the display of the splash screen…

162

I did reboot, but thanks for the tip. :slight_smile:

163

I agree, I have six autostart entries, all of them working as before.

1 Like
164

With luck you won’t need it, but a tip for that sort of situation is to just remove ~/.config/plasma-org.kde.plasma.desktop-appletsrc before logging in (the desktop writes it dynamically so if you remove it while logged in it won’t help.

It may be that restoring that file from a recent backup could clean things up, if the problem was something just caused at the time of the update. Again, make sure you restore it while you’re logged out. Though this won’t help if for some reason one of your applets has become incompatible with the current Plasmashell (this happened to me a while ago when the webslice applet became broken and just made the whole desktop crash).

2 Likes
165

After the update, every time I restart my PC my default keyring disappears out of seahorse and gets replaced with kdewallet. To “Fix” it, I need to create a new dummy keyring, close seahorse, reopen seahorse and then ONLY the default keyring reappears. Hopefully someone finds a permanent fix for this.
The problem is that the kdewallet keyring doesnt work with apps like nordpass or minecraft so it’s pretty much useless for me.
I use Manjaro Plasma

166

you can disable kde wallet from system settings, and hopefully it helps

167

I have an autostart issue. One autostart entry works as usual - just starts Mullvad VPN automatically on login. The other is a bash script that launches three instances of Conky - that one does not autostart.

1 Like
168

Same issue here on my DELL XPS.
I had to boot in fallback and update grub. No issues after that.

1 Like
169

Update broke my polybar. I have no idea how, since I don’t think polybar updated :upside_down_face: I am using stable XFCE.

error: background_manager: Failed to copy slice of root pixmap (XCB_MATCH (8))
error: Fatal Error in eventloop: XCB_MATCH (8)
notice: Termination signal received, shutting down…
error: /usr/src/debug/polybar-3.6.3/src/components/eventloop.cpp:187: libuv error for ‘uv_loop_close(m_loop.get())’: resource busy or locked

170

I have problems with autostart too. I have said it before but I only get 2 answers if I remember correct that was telleing the same as us.

172

update borked my nvidia drivers somehow, main screen now stuck at 480p and is not recognized as before (it’s just identified as “NVIDIA”). Nvidia-utils is installed. Tried to re-install graphics drivers via “Hardware Configuration” system settings, got

error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency ‘nvidia-utils’ required by cuda
Error: pacman failed!
Error: script failed!"

One reboot fixed it, curious why rebooting the first time after the update apparently didn’t count. I still should have been able to re-install my drivers via the system settings though, that definitely seems like some bug in the script.

173

remove cuda first … and if you are not using cuda, dont install it again, its several gb big, so it just wastes your space…

175

That is weird. I have Arch with 5.25 and I dont have issues. Maybe its the upgrade path itself?

I still do not get update notifications…

176

I solved my autostart problem by editing the bash script that starts Conky. I added a 30 second delay and it starts properly.

#!/bin/sh
sleep 30
conky -q -c /home/user/.conkyrc-date-time &
conky -q -c /home/user/.conkyrc &
conky -q -c /home/user/.conkyrc-todo & exit
177

conky command has -p or --pause= option to add a time delay

so this command could be used instead of first two commands

conky -qp30 -c /home/user/.conkyrc-date-time &
178 
conky -qp30 -c /home/user/.conkyrc-date-time

This command works fine when I type it in Konsole, but does not work from a bash file. I’ll stick to the sleep option since it works for me. Thanks!

179

I just found this cause and possible solution: (for autostart problems) https://www.reddit.com/r/archlinux/comments/ves6mh/comment/inf2mwq/

According to that, the reason for autostart stuff breaking is due to the change to use a systemd approach. That said, I think “Autostart” in the KDE system settings should still work as expected regardless of the underlying technology powering it.

The linked comment has a command to go back to the old behavior, but I haven’t tried it yet. I’ll be waiting a bit more.

EDIT: here is the solution in that reddit post:

kwriteconfig5 --file startkderc --group General --key systemdBoot false

and it did actually work for me, too.

2 Likes
180

yes, I can confirm the same. I made a reset default configuration as well

181

steam games broke for me this update. cant get any game to launch