Thanks for your advice. Damn this release and those who did it! Iāve been in hell for days now! Nothing works. The computer freezes, the picture freezes at the most unexpected moments. To get to the desktop manages to 15-17 times. All this time like a fool sitting and restarting the computer. Coolers are constantly cranked to 100, LA system 2.4-2.9. @philm What the ā ā ā ā is going on?
@zo0M and @xaGe: to figure out what happend you may need to provide more info about your installation. Like which Desktop Environment and Kernel are used. Also the content of /var/log/pacman.log with the info of your last updates might help to understand which packages got actually installed/upgraded. [HowTo] Find system information
I downloaded an image of the latest version of Manjaro GNOME, reinstalled the operating system and NOTHING has changed - if Iām lucky and the monitor doesnāt freeze when the OS boots, I get to the login screen 5-7 times, and thatās usually where everything freezes - I see only the background and the cursor looks like X symbol. No user selection for login is displayed, nothing else is displayed at all! All the coolers of my laptop start spinning at full power, and I canāt even switch to the 2nd console! The computer goes into a coma and is frantically spinning the fans trying to take off, apparently.
Hey man, thank you, philm. I havenāt had the time to look into this fully until this morning and have fixed it after looking over the pacman.log as you suggested. I found this from that Monday upgrade.
[2023-11-06T14:56:58-0500] [ALPM] error: problem occurred while upgrading plasma-workspace
[2023-11-06T14:56:58-0500] [ALPM] upgraded plasma-workspace (5.27.8-2 -> 5.27.9.1-1)
Despite declaring an error, says it updated the package. Not sure why it failed, but that could definitely be the issue looking suspicious I just reinstalled that package, rebooted, logged right in and everything was working as it should.
As a 10+ year Manjaro user, I appreciate your continued efforts!
Maybe, but it doesnāt make sense anymore. As I said, I needed to work, not ā ā ā ā around with a broken operating system, so I just rolled back to the previous version.
Saw references to updated Kernels and ZFS packages:
linux510 5.10.199-1 (5.10.197-1) core 79.3 MB
linux510-headers 5.10.199-1 (5.10.197-1) core 30.8 MB
linux510-nvidia 535.129.03-2 (535.129.03-1) extra 53.2 MB
linux510-virtualbox-host-modules 7.0.12-2 (7.0.10-15) extra 175.5 kB
zfs-utils 2.2.0-2 (2.1.13-1) extra 32.0 MB
linux510-zfs 2.2.0-2 (2.1.13-1) extra 1.4 MB
linux515 5.15.137-1 (5.15.133-1) core 104.9 MB
linux515-headers 5.15.137-1 (5.15.133-1) core 33.4 MB
linux515-nvidia 535.129.03-2 (535.129.03-1) extra 55.2 MB
linux515-virtualbox-host-modules 7.0.12-3 (7.0.10-15) extra 265.7 kB
linux515-zfs 2.2.0-2 (2.1.13-1) extra 1.6 MB
linux61 6.1.60-1 (6.1.55-1) core 145.5 MB
linux61-headers 6.1.60-1 (6.1.55-1) core 35.5 MB
linux61-nvidia 535.129.03-2 (535.129.03-1) extra 55.6 MB
linux61-virtualbox-host-modules 7.0.12-3 (7.0.10-20) extra 298.1 kB
linux61-zfs 2.2.0-1.0 (2.1.13-1) extra 1.8 MB
pamac completed updates, no issue. Rebooted. No Issues.
$ uname -a
Linux dldsk01 6.1.60-1-MANJARO #1 SMP PREEMPT_DYNAMIC Wed Oct 25 13:06:34 UTC 2023 x86_64 GNU/Linux
$ zfs --version
zfs-2.2.0-1
zfs-kmod-2.2.0-1
Thank you for the support!
Iām a Manjaro ZFS on Root user using Refind and ZFSBootMenu. Highly suggest ZFS users to run away from GRUB based ZFS usage. ZBM provides a working boot environment to create snapshots, clone/promote snapshots, and should you need it a chroot environment. If you donāt need that, it just loads up Manjaro. Be sure to enable pacman hook to take ZFS snapshot.
Would just like to add, in my own experience, ZFS is working well on linux 6.6.0, much appreciated.
Just to confirm, ZFS is still classed as deprecated despite the laudable efforts by @philm within this thread?
Manjaro green is now blue in gnome-shell.
Was able to open gnome-tweaks from term & change appearance > shell back to custom-accent-colours. Luckily I had a terminal icon in the dock!
Looks good here. Update went smooth, after each reboot in my two kernels, everything can be loaded. Iām on Manjaro cinnamon. My DE of choice. So glad oberon does such a good job here.
After this update, with the new Plasma 5.27.9, I get this weird monitor brightness dimming issue. I have my PC running Manjaro connected to my monitor and a Windows laptop also connected though one of the inputs on that monitor. I can switch which input gets displayed using the monitorās built-in KVM.
Screen dimming was set to happen after 5 minutes of inactivity in KDE. This morning, I switch to my Windows laptop and noticed that the monitor would dim after 5 minutes (while displaying the Wondows UI on my monitor). I realized it was related to the Plasma brightness dimming because as soon as I moved my desktop PCās mouse (which restores the default brightness), then on Windows the brightness was also restored.
Workaround: I disabled brightness dimming in the Plasma energy saving settings.
kde gwenview fails to load since it is linked to (removed) libKF5Kipi.so.32.0.0. The .so was previously provided by kipi-plugins which is an AUR package. kipi-plugins will get uninstalled during the update since is has pkg dependency kio which is now gets changed to kio5. You cannot reinstall kipi-plugins after the update since even if you change the pkg dependency to kio5 you end up dependency hell. kipi-plugins was made defunct some time ago which is why it is in aur. Not clear why the executable is linked to the .so and whether it is a Manjaro, Arch or KDE issue, or possibly something I messed up on.
If you did not remove all gnome extensions, as suggested (it happened to me because I just deactivated them) and you are using X11, you can end with a desktop that crashes on login, probably due to the shell bug on restart.
Just enter in console mode in your user, and remove everything under $HOME/.local/share/gnome-shell/extensions (or rename the directory to some other name) and the next login will work.
