[Stable Update] 2022-02-27 - Kernels, Mesa 21.3.7, Plasma 5.24.2, Frameworks 5.91, Pipewire 0.3.47, Toolchain, Gstreamer 1.20, Nvidia 510.54
I just noticed my gnome is showing 41.3 and not 41.4. Anyone else notice this? A UI bug?
Did this command “gnome-shell --version” That shows 41.4 just shows 41.3 when you check settings. So a UI bug. All good.
gmome-shell version doesn’t define the GNOME version in Settings,
gnome-desktop does. Not all packages will have new versions for point releases. Remember, we have 42 just around the corner.
My wallpaper disappeared … nothing terrible obviously.
mhm … when I click on “Change Wallpaper…” in plasma quick settings nothing happens. However I can successfully set the wallpaper by righ-clicking on an image file with dolphin.
@philm @AlanP This problem was already tracked by KDE devs in 449789 – Impossible to change the user avatar
The real problem is coming from accountsservice package, for now with v22.08.8 the change is reverted to fix the problem, but only Arch repo has that fix while Manjaro unstable/testing/stable repos are still using 22.07.5
If you had the default wallpaper set as background image then after upgrading you will get the new default one, to retain all old wallpapers try installing plasma-workspace-wallpapers package.
Concerning “Change Wallpaper” config window, for me it launches and works fine. What I encourage you to logout then access any terminal tty and delete your user .cache folder then return to tt1 and login again, or if you want to do it safely just create a new user and test with it.
I have to use kernel 5.4.
With the 5.4 the problem happens about once in 15-20 restarts.
For me, the problem arise from long ago.
I created two keyboard shortcuts to toggle touchpad OFF and then ON.
On KDE System Settings → Shortcuts → Touchpad.
Lenovo Thinkpad here.
I’ve had a small issue where openconnect starts to show a lot of logging on stdout. This includes the username, password and token information which I prefer does not show on my console. Not sure how to lower this (new) default level of logging.
If you’ve got filesystems defined with things like /dev/sdc[0-9], /dev/sda[0-9], etc, you’re likely to have occasional problems as the same disc won’t necessarily be given the same path on reboot.
Ideally, you need to replace the filesystem paths with UUIDs instead, as these will be constant whatever you do. You can get the UUID for any filesystem with the blkid command.
We will look into the matter.
Ok. The problem come from accountsservice and not from KDE. Hope to see the V22.08.8 package in Manjaro repositories soon.
Since this update, my login sound (Oxygen-Sys-Log-In-Short.ogg) not working, even when enabled in:
System Settings > Notifications > Applications > Plasma Workspace > Configure Events > Login
But I can play it in the dialog box “Configure notifications”* by clicking on his test button…
I only hear at login the notification that my WhatsApp messaging is out of date, whereas before these two sounds followed one another.
All other notification sounds (empty trash, logout, etc.) work fine.
*My interface is in French, so I’m not sure about the title of the dialog box in English.
Since this update I am having issue with my monitors. If I switch input to my monitor*, immediately removes it, and moves all open windows to the 2nd one. It was happening before, but it was removing the monitor after 1-2 seconds, so I had time to do it. Now it is removed as long as I press the button.
*I have 2 monitors, with 3 inputs. My primary is connected via HDMI to desktop and via DP I have my passthrough VMs displaying there.
edit: KDE Plasma, X11. Also, the windows moved to the 2nd screen, are out of screen bounds and I cannot move them (I am using a “move” shortcut")
For some reason the workaround stopped working today and I’m completely stuck without WiFi.
Running the Manjaro GNOME flavor on a ThinkPad T14s (Intel). After this update I began experiencing issues waking the machine up from suspend, similar to those described by another user in this older thread. I haven’t had an opportunity to sit down and do any thorough debugging yet. My first measure has been to update to a newer kernel version (5.10 LTS → 5.15 LTS), though the older kernel has never produced any similar problems in the past.
UPDATE Mar 12:
Went into the BIOS and changed Config ➜ Power ➜ Sleep State from “Windows 10” to “Linux”. Wasn’t even aware this was a setting option before. In any case, fingers crossed that it will produce a fix. Will report back in a few days.
A post was split to a new topic: Apg: error while loading shared libraries: libcrypt.so.1
A post was merged into an existing topic: Cannot update due to ffmpeg4.4
Please, someone could help… Right after this update, I cannot mount my nfs shares anymore. I didn’t change anything in /etc/fstab but now they are not mounted at boot. If I try to do sudo mount -a from terminal nothing happens, really nothing, no error messages, nothing…
PS: alreay tried to uninstall and reinstall nfs-utils