You are not logged in.
Pages: 1
Hi All,
After a couple of days searching for answers I now seek everyone's help.
Running 6.9.6-arch1-1 Plasma 6.1 Nvidia + Wayland - all working perfectly before.
On the 25th this month I ran
Pacman -Syu which got half way through and then my monitor suddenly went blank and keyboard was unresponsive. After waiting some time I did a hard reset. I booted fine into my desktop but now I can't open Konsole, Timeshift, Ksystemlog, my clipboard also shows 'stuff' in it yet it's empty.
I checked Pacman logs using tty - and on the 24th it says my locale is not set and its reverting to default "C" - then on the 25th it shows a whole bunch of packages (mainly qt6 stuff, kwin, libjuice etc etc) 'upgraded' - right before the crash.
Pacman -Qk shows these packages as empty folders with no missing files.
from the journal I have
user@1000.service Missing 'D-Bus Service' section in service file '/usr/share/dbus-1/services/org.mate.panel.applet.MateXAppStatusAppletFactory.service'
user@1000.service Missing 'D-Bus Service' section in service file '/usr/share/dbus-1/services/org.x.StatusNotifierWatcher.service' When I try to open Konsole I get
user@1000.service app-org.kde.konsole@66fa5195d88f46d0ac301c2664b375f8.service: Main process exited, code=exited, status=127/n/a more general QT6 errors
user@1000.service kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected user@1000.service couldn't load "/usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNotifier.so" because "Cannot load library /usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNotifier.so: libpackagekitqt6.so.1: cannot open shared object file: No such file or directory" when i try to open Dolphin
user@1000.service app-org.kde.dolphin@2828bc9e9cb6420db02199a1ab444f83.service: Main process exited, code=exited, status=127/n/a
user@1000.service app-org.kde.dolphin@2828bc9e9cb6420db02199a1ab444f83.service: Failed with result 'exit-code'. locale Shows everything has en_us_8UTF set but LC_ALL is empty.
I also uncommitted en_gb-UTF8 in my locale.conf - as I live in the UK.
Running
paccheck --quiet --md5sum gives me a smallish list of packages (loads of qt6 packages, kwin, layer-shell-qt, libjuice, libnm, xapp, shiboken6 etc etc all with warnings "mtree data not available (invalid argument).
running
pacman -S kwin (for example) results in "errors occurred" and "no packages were upgraded"
Any ideas as how best to proceed?
Thanks
Last edited by Field_Master_111 (2024-06-26 14:53:07)
Offline
What's the exact output from the "errors occured" pacman run?
Generally speaking you've done some good analysis, you'll have to reinstall all the packages with broken mtrees and empty libraries (mtrees means the pacman DB got corrupted, reinstall the affected packages with --dbonly following an actual reinstall, so picking your example
pacman -S --dbonly kwin
pacman -S kwinand you'd best do that for the entire list you got from paccheck with regards to mtree errors.
That should be able to get you back to speed in this regard...
As for why you crashed during the update. Sadly there seems to be an interaction bug between the nvidia 550 series of drivers and systemd when systemd gets updated which can lead to corrupted kernel memory and thus a full on kernel panic. If your GPU is Turing+ you could try to go with nvidia-open which shouldn't be affected or going to the 535 line of drivers on the AUR: https://aur.archlinux.org/packages/nvidia-535xx-dkms (note for a DKMS kernel module to work you need to have linux-headers installed) see https://bbs.archlinux.org/viewtopic.php?id=293400 for more information when this first surfaced.
Offline
Hello, Thanks.
Okay so slowly moving through the list and re checking each time with
paccheck --quiet --md5sum that that package was fixed - worked!
After all packages were fixed I rebooted to a fully working system.
As for the NVIDIA interaction bug the only time this has happened was on this system upgrade, otherwise my terminal has never crashed. Yesterdays was the only 'issue' Ive had so far.
Thanks once again!
Last edited by Field_Master_111 (2024-06-26 14:08:36)
Offline
Well you should generally be weary of this, and a crash during an update with more vital components, e.g. pacman or dependencies of it (or your shell) could leave you with an unbootable or otherwise annoying to repair (without a live disk) system. Hopefully these bugs are getting fixed, but from what I've heard they're still not quite there yet, AFAIK 560 should be the next stable series, hopefully these issues can get ironed out on the nvidia side.
In any case, if you consider this [SOLVED] please mark it as such by editing the title in your initial post.
Offline
I hear you, thanks once again.
I keep a live USB to hand but do feel I have gotten lucky with this crash as you rightly say it could have been a lot worse.
I'll look into the open drivers.
Offline
Pages: 1