Edit: A little more context. In my case I have Brave in full-screen mode (F11), I choose a rectangular region and press save or copy (doesn’t matter). The Screenshot will be taken, but the hole screen jumps upwards, so only the lower 20% of the formerly full-screen browser are visible at the top of the screen. F11 or F5 don’t solve the Problem, I have to restart the Browser.
The grub thing is run automatically in most cases. On my install it actually run 2 times, i guess there are 2 different trigger hooks somewhere.
No idea why it did not work in your case.
First off, I’d like to thank btrfs, snapper and btrfs-assistant for providing easy rollback recovery.
On my first try, I had 782 updates and my pamac window closed on its own after just 2-3 minutes. I usually watch the scroll, but I didn’t this time, so I don’t know what step it was on. I re-opened it, tried to update again and it said there was an update already running. I waited 20 min for things to clear and rolled back my snapshots to try again.
On the second try, I dragged the update windows out of the center in case a popup came up that might be blocked by them. I watched scroll, but the window did not close this time. It paused while building a browser and gave the error, “authentication failed”. It was probably 8-10 minutes in, so I thought perhaps pamac uses sudo and it timed out. I rolled back, updated the sudoers to add a 30 min timeout and rebooted just in case, to make sure the change went into affect. I have a decent system, so reboots are plenty fast with nvme and a AMD 5900X. I noticed on this attempt that there were 796 packages being updated, not the 782 that it started with.
On the third try, I still got an authentication timeout, so I am not fully trusting the update. I waited a few minutes after the error and clicked the reboot button from pamac. There were no other errors. On that boot, pamac had 11 more packages to update, so I updated those. I did not get any errors. I tested 4 browsers, ollama/rocm (w/6700 XT) and two games and despite Cyberpunk not loading on the first two tries swapping between proton 10 and experimental, it ran fine for a few minutes on the third try. The pamac system tray icon still says there are 5 updates waiting, but opening pamac says the system is up to date.
I’ve found that the install-grub hook also goes through the update-grub steps… my guess is this is to cover a scenario where only the install-grub hook is run… maybe if grub gets updated but not the kernel?
Just a guess, but I just look at it as redundancy.
Minor issue with both Pamac and pacman unable to update due to libopenshot versions – since I never use Openshot I just uninstalled it and updates went ahead. Looks like Openshot was removed from the repos at some point.
Update worked without problems, until i tried hibernation(suspend to disk) via KDE lockscreen.
For some reason Hibernation fails when triggered via KDE’s lockscreen, but still continues to work when using systemctl hibernate (which is run via Konsole while in a kde session).
When triggered via KDE’s lockscreen, the error indicates X tasks(X ranging from 47 to 54) refusing to freeze and the only kde related warning for this i could find is kwin_wayland: Failed to delay sleep: Sender is not authorized to send message (and above dbus-broker: A security policy denied :1.22 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Hinibit to org.freedesktop.login1. I do not recall having manually messed with dbus permissions before and it was working fine before the update.
I have also already ruled-out kernel issues (tried latest 6.18.0, 6.12.61 and before-upgrade kernel 6.12.48)
PS: for some reason KDE tries to automatically log me in after a resume, which in this case had already led me to be locked-out (faillock).
About
Operating System: Manjaro Linux
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 16 GiB of RAM (15,1 GiB usable)
Graphics Processor: Intel® Arc
Manufacturer: LG Electronics
Product Name: 17Z90SP-G.AA78G
System Version: 0.1
Journalctl cut-out
systemd-logind[678]: The system will hibernate now!
NetworkManager[674]: <info> [1765291411.3904] manager: sleep: sleep requested (sleeping: no enabled: yes)
ModemManager[718]: <msg> [sleep-monitor-systemd] system is about to suspend
NetworkManager[674]: <info> [1765291411.3906] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
ModemManager[718]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
NetworkManager[674]: <info> [1765291411.3917] manager: NetworkManager state is now DISABLED (ASLEEP)
dbus-broker[673]: A security policy denied :1.22 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
kwin_wayland[950]: Failed to delay sleep: Sender is not authorized to send message
systemd[1]: Reached target Sleep.
systemd[1]: Starting Set Battery Threshold on boot...
systemd[1]: Starting System Hibernate...
sh[4753]: 80
systemd[1]: battery-charge-threshold.service: Deactivated successfully.
systemd[1]: Finished Set Battery Threshold on boot.
systemd[1]: session-2.scope: Unit now frozen-by-parent.
systemd[1]: user.slice: Unit now frozen.
systemd[1]: user-1000.slice: Unit now frozen-by-parent.
systemd[1]: user@1000.service: Unit now frozen-by-parent.
systemd-sleep[4751]: Successfully froze unit 'user.slice'.
systemd-sleep[4751]: Performing sleep operation 'hibernate'...
kernel: PM: hibernation: hibernation entry
kernel: Filesystems sync: 0.041 seconds
kernel: Freezing user space processes
kernel: Freezing user space processes aborted after 0.000 seconds (47 tasks refusing to freeze, wq_busy=0):
kernel: OOM killer enabled.
kernel: Restarting tasks: Starting
kernel: Restarting tasks: Done
kernel: efivarfs: resyncing variable state
kernel: efivarfs: finished resyncing variable state
kernel: PM: hibernation: hibernation exit
systemd-sleep[4751]: Failed to put system to sleep. System resumed again: Device or resource busy
systemd[1]: user@1000.service: Unit now thawed.
systemd[1]: session-2.scope: Unit now thawed.
systemd[1]: user-1000.slice: Unit now thawed.
systemd[1]: user.slice: Unit now thawed.
systemd-sleep[4751]: Successfully thawed unit 'user.slice'.
systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
systemd[1]: Failed to start System Hibernate.
systemd[1]: Dependency failed for System Hibernation.
systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
systemd-logind[678]: Operation 'hibernate' finished.
It’s because this update/upgrade contains the same versions of the packages in the 25.1 Anh-Linh ISO, which is itself not yet in its definitive state.
Or, it could be that, because @philm decided on some last-minute changes he was still working on, he decided to call it a preview and forgot to edit the thread title after committing the changes.
Either way, the new name is only going to be an update to manjaro-release away.
It is a preview as not all packages are in the stable branch yet. There will be a Plasma 6.5 update and KDE Gear 25.12 update. Also we may find some issues the users of stable branch may report. So expect newer packages and newer ISOs by next week. If you don’t want to wait, simply switch to testing branch …
OK, still bewildered by the inability to open any Chrome (Chromium, Brave, Vivaldi) browser after the update. Running KDE Plasma Wayland and all updates are current. Brave/Chromium ran great before the update but not after. Firefox runs normally. I am also getting a “no connection” on Pan.
It’s a problem caused by your EFI stubs being out of sync. Install install-grub from the repos. It’s a script that will synchronize your EFI stubs, and it gets run after every update.
This, of course in anecdotal, but I have those browsers (with the exception of Brave) working as expected – no issues such as you describe.
I wonder if you would create a new User account (for testing) and see if the condition persists with those browsers in a fresh environment. It’s certainly possible that these issues are limited to your current account – this would be invaluable information to help isolate the problem.
In my installation, install-grubdidn’t work because the EFI partition was formatted as exFAT (instead of FAT32). (Somehow, this doesn’t seem to have been a problem for the last few years.)
I’ve now changed it to FAT32, and since then, also refind finally works properly for me (and of course, I ran install-grub manually.)
