Joe Salmeri <jmscdba@gmail.com> writes:

On 12/10/23 16:50, Berthold Höllmann wrote:

...

Patrick Shanahan <paka@opensuse.org> writes:

...

* Berthold Höllmann <berthold-tumbleweed@höllmanns.de> [12-09-23 16:13]:

...

Since updating to tumbleweed 20231206 pokit does not start on boot.

similar thread "solved" on opensuse-pack. your answer is probably there. Yes it was. Permissions for the config dirs were wrong, which was no problem until 20231206.

Is there a released TW build which has this problem fixed ?

I guess, the problem was on my side. I had to restore my system a few month ago. I tried to restore my settings from an faulty backup. My system, beeing evolved over severl years had different ids for standard users and groups. It was quite a hassle to get the system running again. I guess I overlooked the mismatch in group assignement for the polkit configuration directories: ,---- | chown polkitd:root /etc/polkit-1/actions/ | chown polkitd:root /usr/share/polkit-1/actions/ | chown polkitd:root /usr/share/polkit-1/policyconfig-1.dtd | chown polkitd:root /usr/share/polkit-1/actions/* | chown polkitd:root /usr/share/polkit-1/rules.d/* `---- fixed the problem for me. The reason, I think its a problem specific to my computer is the slightly changed start up process for my fvwm2 desktop environment. For the last month I had to provide my password somewhere along the setup of all my windows, this query is gone after fixing th file and dir permissions as shown above.