I can’t hide Opera web-browser(official, community). The browser can be closed or resized its window, but when I want to hide its window, it opens at once.
I’ve tried reinstall it or use Snap and it wasn’t fixed
When I shutdown PC, it shows me at last second:
Is this good, bad or normal? Should I close my eyes on it or fix it? I hadn’t seen this before.
That helped with sddm. If by color scheme you mean the theme color available in quick settings, I’ve chosen the dark theme. Now there’s only this tiny annoyance in contrast with the dark theme choice:
What an update! 
Updated innocently in the background while working on other stuff and then…
Everything is in Hindu (I think) language now 
Never had such an update
At the console, go to Settings, Edit Current Profile then Appearance and select the Breath theme. This is how I fixed it…
A reboot fixed it. At least something unusual and unexpected happened 
That was brought by
[ALPM] upgraded opera (81.0.4196.54-1 -> 82.0.4227.23-1)
and was reported upstream, which was linked in the testing branch of updates: [Testing Update] 2021-12-07 - Mesa 21.3.1, Breath 21.2, Gnome 41.2 - #10 by alven
This release broke kscreenlocker, i run yay --Syu --noconfirm and when i came back screen show
“The screen locker is broken and unlocking is not possible anymore. In order to unlock…”
This is log from journalctl
Dec 11 20:48:05 spqapc kscreenlocker_greet[5727]: Qt: Session management error: networkIdsList argument is NULL
Dec 11 20:48:05 spqapc audit[5727]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5727 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1
Dec 11 20:48:05 spqapc kernel: QQmlThread[5734]: segfault at 7f2b0c317004 ip 00007f2b38ce9e01 sp 00007f2b29cf5050 error 4 in libQt5Qml.so.5.15.2[7f2b38b2d000+2f7000]
Dec 11 20:48:05 spqapc kernel: Code: b7 53 2e 8b 43 30 48 8d 14 52 4c 8d 24 03 48 8d 0c d0 4c 8d 2c 0b 4d 39 ec 75 0f eb 34 0f 1f 40 00 49 83 c4 18 4d 39 e5 74 27 <66> 41 83 7c 24 06 09 7>
Dec 11 20:48:05 spqapc kernel: audit: type=1701 audit(1639230485.175:301): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5727 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet">
Dec 11 20:48:05 spqapc kwin_x11[1561]: kwin_core: XCB error: 152 (BadDamage), sequence: 33952, resource id: 27278798, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Dec 11 20:48:05 spqapc kscreenlocker_greet[5742]: Qt: Session management error: networkIdsList argument is NULL
Dec 11 20:48:05 spqapc audit[5742]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5742 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1
Dec 11 20:48:05 spqapc kernel: QQmlThread[5748]: segfault at 7f89d718e13e ip 00007f89b2100e01 sp 00007f89a2ffc050 error 4 in libQt5Qml.so.5.15.2[7f89b1f44000+2f7000]
Dec 11 20:48:05 spqapc kernel: Code: b7 53 2e 8b 43 30 48 8d 14 52 4c 8d 24 03 48 8d 0c d0 4c 8d 2c 0b 4d 39 ec 75 0f eb 34 0f 1f 40 00 49 83 c4 18 4d 39 e5 74 27 <66> 41 83 7c 24 06 09 7>
Dec 11 20:48:05 spqapc kernel: audit: type=1701 audit(1639230485.439:302): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5742 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet">
Dec 11 20:48:05 spqapc kscreenlocker_greet[5751]: Qt: Session management error: networkIdsList argument is NULL
Dec 11 20:48:05 spqapc audit[5751]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5751 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1
Dec 11 20:48:05 spqapc kernel: QQmlThread[5757]: segfault at 7f91132c588a ip 00007f90c0109e01 sp 00007f90b1392c70 error 4 in libQt5Qml.so.5.15.2[7f90bff4d000+2f7000]
Dec 11 20:48:05 spqapc kernel: Code: b7 53 2e 8b 43 30 48 8d 14 52 4c 8d 24 03 48 8d 0c d0 4c 8d 2c 0b 4d 39 ec 75 0f eb 34 0f 1f 40 00 49 83 c4 18 4d 39 e5 74 27 <66> 41 83 7c 24 06 09 7>
Dec 11 20:48:05 spqapc kernel: audit: type=1701 audit(1639230485.689:303): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5751 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet">
Dec 11 20:48:05 spqapc kscreenlocker_greet[5760]: Qt: Session management error: networkIdsList argument is NULL
Dec 11 20:48:05 spqapc audit[5760]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5760 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet" sig=11 res=1
Dec 11 20:48:05 spqapc kernel: QQmlThread[5766]: segfault at 7f3e31fc913e ip 00007f3e0dc99e01 sp 00007f3dfeebb050 error 4 in libQt5Qml.so.5.15.2[7f3e0dadd000+2f7000]
Dec 11 20:48:05 spqapc kernel: Code: b7 53 2e 8b 43 30 48 8d 14 52 4c 8d 24 03 48 8d 0c d0 4c 8d 2c 0b 4d 39 ec 75 0f eb 34 0f 1f 40 00 49 83 c4 18 4d 39 e5 74 27 <66> 41 83 7c 24 06 09 7>
Dec 11 20:48:05 spqapc kernel: audit: type=1701 audit(1639230485.952:304): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=5760 comm="QQmlThread" exe="/usr/lib/kscreenlocker_greet">
/usr/lib/kscreenlocker_greet --testing show segmentation fault but sudo it worked fine
I have tried restart, “lookandfeeltool -a org.kde.breeze.desktop”. Nothing work
This error appears every time i lock the screen
@frost19k No it will be included in 5.15.8 kernel/git/stable/linux-stable-rc.git - Linux Stable -rc releases
Backport can be possible
Do not want to cite the message fully? Try this solution: “to fix this problem you need to…”
Does the solution work for you?
Well turns out there are several ways to customize it … i used “oh-my-zsh” and powerlevel10k to change it. I will stick with zsh for now.
The full message is like
The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
log in and execute the command:
loginctl unlock-session 2
Afterwards switch back to the running session (Ctrl+Alt+F1).
Following the instruction brings me back to my session but it does not solve the problem though. When i lock the screen, the message appear again
Yeah, well you specified it must go on on it’s own and not check, confirm with you. I hope you learnt a lesson from this.
Boot with live media, chroot into the system and fix with pamac.
pamac update
Also, read the announcements, so you know what to expect.
Sync/update with pamac, merge any .pacnew files and report back.
Thanks, that helped it. Just noticed that my lock screen is still looking off from it’s colors like the login prompt was.
Edit: That got fixed by just reapplying the lock screen theme.
Edit #2: My issues are all fixed now (on my main laptop at least). Thanks everyone for helping. Rest of my installs (2 other machines) should have quite similar setups, so I don’t expect very different issues on those, except ZFS on one but that is always an issue if I try to update the kernel too quickly.
Got kernel panic on a stable channel, 5.10 LTS kernel Plasma installation.
I had to chroot into the installation and re-install linux510 to make it work again.
Is it me or Manjaro stable updates are getting buggier with every new release?
Mm i thought the same, the list with issues is growing rapidly.
This is only my thoughts though, i use the cinnamon version and have no problems sofar but i haven’t installed this updates jet.
Edit: Just installed the updates, all mint-y-dark themes are missing! They can’t be selected anymore
Why is this happening?
Nothing’s wrong. Just habit you know 
No problem.
It’s not really problems, but only a change of the KDE desktop decorations. Then you just have to use your head a bit and make some settings/adjustments and everything is good again. I myself had almost no problems with this update since I now update with pamac in the console, since it is recommended as far as I know.
Kind regards SchulzX777
I am not sure, but low possibility of kernel-alive package suspected here (discussion Please use kernel-modules-hook instead of kernel-alive! and it is not a suggestion to switch, for now it is a try to find relations only).
Just to collect statistics, please post your complete output of:
pacman -Qi kernel-alive kernel-modules-hook | grep "Version"
one issue here, I think it started from the previous update (I guess it’s fine to post it here)…
it’s a window (re)drawing problem of a sort, as I could tell
KDE (I also run XFCE, works fine, so only on KDE)
firefox
4K monitor if any relevance (HDMI, I think 1060 card if not mistaking, graphics wise all working fine).
and since it’s 4K I have scaling on (something at 225%)
I keep FF maximized (without the titlebar, just tabs)
once I close/quit the FF and restart - it draws the window as in non-maximized (restored) mode - but funny thing is it doesn’t react on mouse at all - I’ve figured out that the window is actually maximized (i.e. if I click blindly at the top I can restore it) but shows like restored, i.e. it’s totally screwed (visuals vs mouse coordinates is out of sync). The way out of it is to r-click on the icon, more actions, get it out of max-mode and then it starts working normally.
(I don’t think this is scaling issue, as win size is not like 1/2 or 1/4 or anything like that it’s just slightly smaller restored/non-maximized)
Anyone else seen this?
It’s no big problem, but it is a bit ugly,
thanks guys for all the work
I find it quite unacceptable that the default settings in the user space were changed with an update, i.e., attempting to change the shell to Zsh along with other settings in Konsole.