I’m sorry, but I don’t understand what you’re telling me to do. As far as I know, I can only access a GRUB command line, and chroot doesn’t work there.
Is there a thread/website that explains this process in more detail?
Edit: It was linked in the post right above me. Now I feel a little silly. Thanks anyway!
boot into live usb of manjaro, connect to internet and chroot: manjaro-chroot -a
rerun update: pacman-mirrors --fasttrack 5 && pacman -Syyu
if no errors reinstall kernels: pacman -S linux515 linux60
if no errors, exit chroot: exit
reboot and see if it helped
everything else seems fine, but plasma keeps finding new ways to surprise. When i have a window in full screen and the monitor goes to sleep, when i return and login it is non-fullscreen and immediately maximizes back. Makes for a pretty “busy” login, but not an actual problem.
I got the message “signature from “Manjaro Build Server <build_at_manjaro_dot_org>” is unknown trust” for kernel Linux515. I do not know why the new manjaro-keyring was not included in my update?
So:
Update via Pamac hung up, 1/515 checking integrity. I waited for 20 mins before killing the process. After reboot, it complained about a bunch of stuff not loading, NFS etc, like 5 different things. Pacman would not work, complained about GPGME, readline shared library error.What I tried to do was extract the readline + lib32-readline from /var/cache/pacman/pkg. Extracted the .zst-file with zstd -d and then tar -xvf . Moved them to /usr/lib. I was supposed to do a pacman -Syu --overwrite readline.so.8.2 or something but I couldn’t figure it out. What I did was remove the softlink to readline 8.2 (sudo rm libreadline.so.8) and made a new one pointing to readline8.1 (sudo ln -s libreadline.so.8.1 libreadline.so.8). libhistory got the same treatment as libreadline. This way I could at least run pacman.
I refreshed keys for good measure, following Oneno’s instructions
Now I got booted into Manjaro after reboot, graphics and all. So this time I updated via terminal and all went fine. I might have set myself up for future failure.
I was copying files back and worth, thinking it must be the 8.2 version failing and renaming it *.bak. 8.1 version worked. The install must have made that link, I didn’t. Then again, I was sleepy and fell asleep during the pacman-key --refresh-keys part. Yeah, I don’t sleep long. Got maybe an hour in.
Had an issue with mouse clicks on multiple virtual screens in Virtualbox 7.0.2 with Win10 guest after update. Seems like something to do with Nvidia drivers since there were older posts with the same issue on other versions: quick workaround is to disable extra displays in the guest, fix seems to be switching pointing device type from USB tablet to PS/2 mouse in VM settings.
Hello, I am experiencing a KDE Plasma issue after some time using the computer. All the activities becomes mixed up, the apps still work, but their windows stay freezed, so it is not possible to properly see, change programas. The only thing I am quite able to do is to switch to Ctrl+Alt+F2 and reboot. So I can work for a few more hours before it happens again.
UPDATE: I had replaced plasma with the local 5.24.7 version, but the issue was still happening. So I updated back to 5.26.2. Not sure exactly the issue relies, but it started after this Stable Update 2022-11-02.
Apparently, I tripped over an audio cable in my rush to make a dramatic exit. Looks like the joke’s on me in the near future…
I want to formally apologize to anyone whom I may have insulted with my immature hit-and-run mic drop moment. My pride hurts like hot coals against my face.
Thank you so much Zeitt, you fixed the problem for me
I just renamed the file for backup case (but wasnt needed) and restarted the OS.
I was remembering the zsh change, few month ago… where i had to changed the Terminal Setting to old school Bash again.
And i have to say, its not needed to revert it to zsh… locale issue is gone and the Terminal is working with Bash again.
My only issue was with Virtualbox. The new notification panel appeared momentarily with some error message regarding adding the user to vboxusers. Logging out and back in did not resolve the issue, removing & reinstalling Virtualbox also did not resolve the issue. So the last resort was to detach the virtual disk and attach it to a new vm installation as a second drive to get access to any files left behind.
After last update my dual display configuration doesn’t work anymore on KDE.
Dual screen is fine at boot but the main monitor (DP-0) stop working after login and the second one HDMI-0 (DELL U2415) becomes the only one active.
In KDE control panel (System Settings/Display and Monitor) I see my DP-0 monitor (AUS PA278QV) that appears and disappears every few seconds but I can’t enable it.
In /var/log/Xorg.0.log I noticed many connection’s attempts:
you are not the only one, there are others affected with the same multimonitor setup issue…
you can delete/rename the kscreen folder in your $HOME/.local/share, then reboot and see if it helped