This is not a mistake, we just listed different options for one to try his luck.
It is still a buggy mystery (to me at least). In theory, this 4 should not be needed anymore, so the update removed it. But then some users reported a problem and had to revert the change. Why is still unknown. For most of the people, me included, the new config (without the 4) works fine.
Youāre right, but I didnāt write that it was a mistake, but unclear (at least for me).
Perhaps, not surprisingly, the statement that was not entirely clear was the one made by the bot.
That is true if your kernel supports it. Why you think 6.12+ series was suggested. Older may need the SUID flag still.
2 Likes
Hi, Iām getting the following error while trying to update:
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libdisplay-info (0.3.0-1) breaks dependency 'libdisplay-info.so=2-64' required by wlroots
removing wlroots seems not an option (too many deps)
At least on XFCE the only dependency is labwc, and all the wayland stuff is experimental and optional anyway, so this is not a problem. If you are on a different DE i do not know.
Yeah, Iām on sway, a lot depends on wlroots thereā¦
A post was split to a new topic: Upgraded my old laptop after almost 5 years untouched
Are your mirrors fully synced? There are 3 versions of wlroots, and those 3 versions are the same across all 3 branches according to Branch compare for Manjaro - wlroots
A quick check shows all 3 versions of wlroots now require libdisplay-info.so=3-64, which is provided by the libdisplay-info package. That package is v0.3.0-1 across all 3 Manjaro branches.
pamac info wlroots0.17 wlroots0.18 wlroots0.19 | grep -E Name\|Version\|libdisplay
Name : wlroots0.17
Version : 0.17.4-4
Depends On : libdisplay-info.so=3-64 libglvnd libinput
Name : wlroots0.18
Version : 0.18.3-1
Depends On : libdisplay-info.so=3-64 libglvnd libinput
Name : wlroots0.19
Version : 0.19.2-2
Depends On : libdisplay-info.so=3-64 libglvnd libinput
So, make sure your mirrors are fully synced before updating.
I had paused updates around the āpreviewā released batches in Dec, which left me back on Octoberās releaseā¦ things looked good reading through this release, so I gave it a go.
The only āfailureā / manual intervention required (beyond normal) was the updates to the keying for pacman-mirrors ā¦ which was well documented in the āknown issues & solutionsā section.
I normally update through the terminal (or TTY) via pacman, and experienced no polkit issuesā¦ I didnāt update AUR packages via pamac until after rebootā¦ and the GUI had no issues prompting for my pwd to proceed.
Iāve had the install-grub package/hook installed for a while nowā¦ and the Dec grub updates applied without any intervention on my part.
Even decided to try the new LTS kernel and have had no issues while gaming the last 2 daysā¦ so great work Manjaro Team!
6 Likes
Previously (and mainly still) rock solid system for 2 years+, 4070, 5950x, 64gb 3600cl16, KDE, 6.12 and latest kernel:
A reboot/crash now eventually occurs every time I lock the desktop and turn the screen off (turn off with Esc key not by pressing the button on the monitor), when I come back itās on drive decryption password entry. Thereās nothing in the logs from sudo journalctl -p 2 about these crashes ever.
Since this behavior started, this system has never crashed while the screen is on and unlocked. 100% all core, hard single core, running LLMs, games, idling whatever, no problems.
I also have every possible power saving feature completely turned off, everything on max performance (had nothing but problems with all power saving features for years).
Iām expect this is an nVidia driver issue and not much can be done (the performance improvement in the one game I play from that driver is HUGE though, so Iām not downgrading over this).
It also wouldnāt surprise me if itās something to do with some KDE default behaviour being changed and actually borking something, only considering this because both the previous updates had KDE forcing random wierd bug-like behavior onto users, so I donāt know what to expect anymore, or how theyāre going to try and mess with my system.
For now my solution is to simply leave my monitor on and the pc unlocked 24/7 (this worked for 3 days, straight, and yesterday I forgot and locked the screen and pressed Esc to turn off monitor, and sure enough I came back to password entry and no logs).
After the update, Kalarm would crash when trying to create a new alarm or editing an existing one. Reinstalling, downgrading, trying a new user, nothing would stop the crashing. Searches came up empty at that point but this evening I tried another search and found this page ā
which then led me to this page ā
and a stopgap solution was mentioned (downgrade ktextaddons ver 1.9.0 to the earlier 1.8.0) so I installed and used the manjaro-downgrade utility to do that. However, the list of possible ādowngradesā also listed the newer ver 1.9.1-2, so I decided to give that a try.
It worked.
1 Like