Called systemd-boot 
I had not used CMake-gui for a month but today when I started it:
❯ cmake-gui
cmake-gui: error while loading shared libraries: libQt6Widgets.so.6: cannot open shared object file: No such file or directory
Edit 1: qt6-base is optional dependency of cmake and it resolves the problem.
sudo pacman -S qt6-base
Why? Is there a specific fix?
Another issue is that Kate has disappeared as a select able menu item in the Gnome panel. I can still run it from the terminal. Reinstalling it from pacman -S did not seem to affect it.
Kate does show in the menu tool.
Kwrite still shows up in the Gnome menu like any other app.
Not sure what to do at this point.
Edit: I toggled Kate off and on in the menu tool and it showed normally for a moment, was able to open it, but the icon no longer shows after a few seconds in the GNOME menu.
Edit2: I Installed the same iso to two different machines. One of which I did not update. Can confirm that Kate shows normally on the one that did not update.
Sure… But Bootctl is mandatory to automate updates.
I’m not before my gear right now but would appreciate to have some directions with that mess.
Obviously, the kernel modules are not loaded (else mount would not fail).
Any idea on that regard?
Having problems with wine after the last 2 updates.
I suspect Akonadi not working has to do with KCoreAddons (and several other KDE packages) being installed from git (from the community repo) instead of the actual release.
How do I make sure everything goes back to an actual release in KDE, instead of git packages?
Firefox would not start at all ( I could not go in and disable hw acceleration because it was just not starting ) I downgraded back to Firefox 87 and started with backwards compatibility to recover my profile.
This seems to be broken for a lot of nvidia and intel users. Kind of a surprise this was allowed to get into stable.
I have a similar problem here with plymouth, sddm + kde. Boot gets stuck just before showing the loginscreen, no reponse to keyboard, no switch to tty, no ctrl-alt-del. Only emergency power off helps.
System reaches login when I press ESC early enough to exit plymouth before login.
Install plymouth-git from AUR,it fixes the problem
Yeah, I’ve been using git version since a year or two as well, when it turned out that repo version is completely broken.
2 Likes
Yup, manually identifying all *-git KDE packages and replacing them with normal proper release seems to have solved my issue.
Can you please post the link of the issue at the VBox Forum as well?
Error updating packages, rubY files exist
Dont know how to scroll up in tty, im using tty because x server wont start so i tried updating
This error is general … more information about the problem is on next lines.
Often it can be mix of Virtual Box and Extension Pack versions … but it’s just a blind hint 
It might be a slippery slope. Don’t know if you use KDE or gnome, but when I started getting error messages like that, removing db.lck, running pacman-mirrors or turning to pamac for updates inside GUI, things went horribly wrong along the way and my system eventually crushed. See the solution post here for the close-to-fool-proof way to go about updating. Pacman and TTY are your friends!
Hi,
got issues, mainly with firefox and akonadi. Both crash on launch. Call from a terminal for firefox log a bus error, with core dumped. Coredumpctl show same errors for Firefox, Akonadi, Whatsapp-linux, and Midori, with a signal, and always the same stacktrace (for lines 0 to 5) from coredumpctl info :
Stack trace of thread 8194:
#0 0x00007f4aea656153 memset (ld-linux-x86-64.so.2 + 0x24153)
#1 0x00007f4aea63a40a _dl_map_object_from_fd (ld-linux-x86-64.so.2 + 0x840a)
#2 0x00007f4aea63b82d _dl_map_object (ld-linux-x86-64.so.2 + 0x982d)
#3 0x00007f4aea645f6c dl_open_worker (ld-linux-x86-64.so.2 + 0x13f6c)
#4 0x00007f4aea20db38 _dl_catch_exception (libc.so.6 + 0x139b38)
#5 0x00007f4aea645ade _dl_open (ld-linux-x86-64.so.2 + 0x13ade)
#6 0x00007f4aea5df34c n/a (libdl.so.2 + 0x234c)
lines 1-26
It’s far away from my competence to debug this kind of errors…
I have the same issue after EVERY major Manjaro update. (never happens during normal reboot)
It tries to mount and unmount disks in circles. The system never reboots after update – I am forced to turn it off physically.
system info:
RAZER Blade 15 (2018)
dual boot with Win 10
GNOME 40.0.0