https://bugzilla.novell.com/show_bug.cgi?id=816942 https://bugzilla.novell.com/show_bug.cgi?id=816942#c28 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com --- Comment #28 from Lars Müller <lmuelle@suse.com> 2013-06-03 14:41:15 CEST --- (In reply to comment #27)
But I think I may have found the culprit: plymouthd!
For some reason plymouthd is started when I run "init 5" and seems to cause this. If I rename /usr/sbin/plymouthd (so it can't start) the problem doesnt occur: the session gets registered correctly and the ACLs get set (and that's reliable across ~10 reboots now). Can somebody else confirm that this helps?
Yes. I've moved /usr/sbin/plymouthd away and then the first login gave the wanted additional ACL. Even when going from runlevel 3 to 5 and login. In a next step I've removed these plymouth packages: plymouth plymouth-branding-openSUSE plymouth-scripts Booted into runleven 3, called init 5, and got the intended ACL with the first login via kdm. One further observation I did: Before I did the quick hack/ check and renamed the plymouthd binary I mistyped by accident the password. plymouthd before but no longer afterwards. But even in the case of a no longer running plymouthd I didn't got the additional ACL set with the first login. The any later it worked. Has anyone tested the same with openSUSE Factory? I'm adding Marcus as he's marked as the bugowner for plymouth in oS 12.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.