[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

Hi, thank you for your help. I had different problem - I could see the media, but I couldn’t mount it.

Problem was, as I figured out, in fstab file. There was a line for /dev/sdc what was completely wrong and also I don’t know why there was this line.

Repairing fstab file solved problem.

Absolutely. The description of the program from their readme in gitlab:

Secrets is a password manager which integrates perfectly with the GNOME desktop and provides an easy and uncluttered interface for the management of password databases.
(…)
Features:

  • :star: Create or import KeePass safes

It asks you to create a KeePass file once, saves its location in dconf, and then never asks you about it again if you don’t want to. That’s how I forgot about the location of said file. Since the program changed its name, the schema also changed.

Searching the forum, I’ve found a similar issue:

I’ve not the 40-libinput.conf inside /usr/share/X11/xorg.conf.d. So, I understand that I should create it, however I don’t know what stuff I should put in it (in addition of the suggested solution, of course).
Any idea? :smiley:

Hi! Can not use subshell in mc (MidnightCommander) with ctrl+o after the latest update:
Subshell closing immediately after pressing any key and mc returns it’s panels…

 >>> mc --version                                                                                                                     
GNU Midnight Commander 4.8.27
Built with GLib 2.70.2
Built with S-Lang 2.3.2 with terminfo database
With builtin Editor
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
With ext2fs attributes support
Virtual File Systems:
 cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs
Data types:
 char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

Wanted to show a gif or a video of a bug, but don’t know how to attach it here…
Also, if any additional info is required, please, mention…

1 Like

I’m not familiar with the internal workings of KDE. I don’t see kdebase-runtime as a user or group. What did you remove, exactly? Thanks!

kdebase-runtime is an old and long since removed KDE4 package. You can remove it:

sudo pacman -Rs kdebase-runtime && sudo pacman -Syyu

Issue with sound is fixed by
creating a file ~/.config/pipewire/pipewire-pulse.conf.d/pipewire-pulse.conf

stream.properties = {
    channelmix.normalize  = false
}

and restarting the services

1 Like

You could also uninstall it with the assumption that it is installed, so that you don’t actually uninstall its dependants.

sudo pacman -Rnus --assume-installed dunstify dunstify

Followed by upgrade immediately

sudo pacman -Syu

Black screen after reboot after update is complete. But on the next reboot it worked.

I’m merging /etc/locale.gen with /etc/locale.gen.pacnew after the update. What kind of can of worms goes open when one would uncomment C.UTF-8 UTF-8?

It’s a bit sad that the syntax of that file supports comments, but upstream lacked to document the need of the C “locale” in locale.gen in place. Also trailing spaces :face_vomiting:

1 Like

Since updating my KDE install that I created only a few months ago, the system tray is present, but pamac, syncthing-gtk etc. no longer appear like they used to. They also aren’t present in the Entries tab as Hidden.

EDIT: Also, other than Firefox, everything is very slow to open. And no, CPU is not fully utilised, it is less than 20% and same with memory. Seemed to not effect GTK apps, but only QT/KDE

EDIT 2: Using a timeshift backup, I can confirm that something broke in the update, as everything is working now. Backup was from the 25th of Feb as I hadn’t used it in a bit.

EDIT 3: Installed the updates again, same thing occurred. Created a new user and everything is working again, so obviously something changed in the user configurations.

@wo80 @koshikas

2 Likes

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.

Nope. The 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.

1 Like

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.

Me too.
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.