Usually with those warnings you follow the package unless you know better.
I’ve downgraded filesystem back to 2023.09.22-1 and plymouth back to 22.02.122-14 due to issues with the new Plymouth version 23. They both must be downgraded at the same time as the two packages are interdependent on one another.
What about us who don’t use plymouth? Best to downgrade anyway? I see other packages relying on filesystem.
If I’m correct the only change on filesystem was adding a logo to it.
Yes. plymouth depends on filesystem. There were changes with the newer versions that go together, so both must be downgraded together to match.
Not quite. The logo was moved from plymouth to filesystem, that’s why the old and new packages must be downgraded / upgraded together.
750 is correct in this case. So we have to figure out which package is not matching that folder via pacman -Qo /usr/share/polkit-1/rules.d
1 Like
On my both laptops, I installed 3 years ago Manjaro KDE via Minimal ISO,
But now I don’t find plymouth installed nor configured in /etc/default/grub nor HOOKS in /etc/mkinitcpio.conf
Even /var/log/pacman.log doesn’t contain any install/remove/upgrade related to it,
Was it added later ? And should I add it to avoid problems ?
plymouth is entirely optional, in fact it sometimes causes problems, and is one of the first things I would remove.
4 Likes
I’ve just made major changes with plymouth 22.02.122-17 that removed the old unneeded cruft in preparation for the new upstream v23.51.283:
WARNING: The plymouth-encrypt and sd-plymouth hooks no longer exist in the package. You should replace them with encrypt and plymouth hooks in your mkinitcpio.conf. The lxdm-plymouth.service, lightdm-plymouth.service and sddm-plymouth.service systemd service files no longer exist in the package. You should enable lxdm.service, lightdm.service or sddm.service instead.
/usr/share/polkit-1/rules.d/ is owned by fwupd 1.9.10-1
/usr/share/polkit-1/rules.d/ is owned by gamemode 1.8.1-1
/usr/share/polkit-1/rules.d/ is owned by geoclue 2.7.1-1
/usr/share/polkit-1/rules.d/ is owned by gvfs 1.52.1-1
/usr/share/polkit-1/rules.d/ is owned by polkit 123-1
/usr/share/polkit-1/rules.d/ is owned by systemd 255.1-1
The only matching package that got updated in that moment was gamemode.
Well, nothing changed with Arch packaging with gamemode 1.8.1-1. 
I haven’t dug into the upstream changes.
Yes, I was wondering the same 
there seems to be something with that directory maybe?
( 9/37) upgrading gamemode
warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750 package: 755
I know the answer to my thing is [Unstable Update] December 2023 Edition - #44 by philm
I just meant it’s the same directory and gamemode
this indicates that the permissions are wrong. Someone should open an issue at Arch to change the permissions of that folder to those of the polkit package.
I see reports upstream. And it doesn’t seem to work right at the moment anyway. gamemoded -t fails for me as well. User intervention required to restore functionality, it seems.
That has been the case for a long time, at least it was in the wiki +5months ago when I installed it because I remember adding me to the group when installing.
This feature requires the user to be in the
gamemodeuser group to work.
https://wiki.archlinux.org/title/Gamemode#Renicing
But there IS a bug, that I also reported to the github, that shows gamemode as inactive in mangohud while in reality it actually works.
You can test by starting the game and then type gamemoded -s in a terminal to confirm it is actually active (even though it will say that it is off in mangohud).
Edit
Although, I have no problems reported by gamemoded -t, seems to me a you thing,
gamemoded -t
: Loading config
: Running tests
:: Basic client tests
:: Passed
:: Dual client tests
gamemode request succeeded and is active
Quitting by request...
:: Passed
:: Gamemoderun and reaper thread tests
...Waiting for child to quit...
...Waiting for reaper thread (reaper_frequency set to 5 seconds)...
:: Passed
:: Supervisor tests
:: Passed
:: Feature tests
::: Verifying CPU governor setting
::: Passed
::: Verifying Scripts
::: Passed (no scripts configured to run)
::: Verifying GPU Optimisations
::: Passed (gpu optimisations not configured to run)
::: Verifying renice
::: Passed (no renice configured)
::: Verifying ioprio
::: Passed
:: Passed
: All Tests Passed!
1 Like
The reply I linked apparently fixed that user’s problems.
gamemoded -s only reports if gamemode is running or not. It doesn’t comment on issues like mentioned in the issue report. Here’s what my journal has to say:
joulu 22 17:45:16 jp-gentoo pkexec[66839]: jp: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/home/jp] [COMMAND=/usr/lib/gamemode/cpugovctl set performance]
joulu 22 17:45:16 jp-gentoo gamemoded[66839]: Error executing command as another user: Not authorized
joulu 22 17:45:16 jp-gentoo gamemoded[66839]: This incident has been reported.
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: External process failed with exit code 127
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: Output was:
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: Failed to update cpu governor policy
joulu 22 17:45:16 jp-gentoo pkexec[66844]: jp: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/home/jp] [COMMAND=/usr/lib/gamemode/procsysctl split_lock_mitigate 0]
joulu 22 17:45:16 jp-gentoo gamemoded[66844]: Error executing command as another user: Not authorized
joulu 22 17:45:16 jp-gentoo gamemoded[66844]: This incident has been reported.
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: External process failed with exit code 127
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: Output was:
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: Failed to update split_lock_mitigate
joulu 22 17:45:16 jp-gentoo gamemoded[1140]: ERROR: Skipping ioprio on client [66838,66838]: ioprio was (0) but we expected (4)
Perhaps being added to the group is a requirement for governor switching now as well.
Yeah, mods are prob going to split it into its own thread, that is a you thing, check my edited post above.