So would you recommend to restart apparmor.service, like it was suggested in the update log? Could that cause problems?
Or are there any streps/precautions I need to take, before doing this?
Thank you so much for your help!
If you reboot, then it’ll be restarted already. You should not continue working without a reboot after updating your system.
You should adjust your workflow so that you get all of your work done before you update your system, so that you can immediately reboot right after the update.
3 Likes
Since last update i have an issue with Screen Locking (KDE Plasma).
I can type my password in the lock screen but nothing happen when i hit enter or i click the icon,i stay stuck on this screen.
I have to login in a TTY to reboot (there may be less extreme solution 
)
Does anyone has this issue too?
I tried on unstable branch, it works with 6.4.3
man loginctl
1 Like
Oops, thanks, i did not know this one. 
1 Like
I did have the same problem on two different machines.
In my case it was solvable by adding the org.freedesktop.secrets.service via automatic dbus activation as described in the arch wiki KDE Wallet page and rebooting. The service did not seem to exist beforehand.
1 Like
Well, I’ve tried that, but it failed to start and threw an error message. Furthermore, the Arch Wiki only talks about kwallet5, not about the current kwallet.
Either way, the problem is solved now, albeit that I did lose all my passwords, and I had to enter them all again.
Now I’ve updated, I was worried about the kwalllet but no problems.
Learning from your mishap I exported my kwallet passwords first. Export was not needed but I saw I had quite a few old passwords I should probably remove.
Not for me:
[h2@h2-imedias1800 ~]$ wine: created the configuration directory '/home/h2/.wine'
002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc0db3f
wine: could not load kernel32.dll, status c0000135
1 Like