https://bugzilla.suse.com/show_bug.cgi?id=1206690 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |saweber@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1206690 https://bugzilla.suse.com/show_bug.cgi?id=1206690#c2 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |dmueller@suse.com, | |fvogt@suse.com Severity|Normal |Major --- Comment #2 from Fabian Vogt <fvogt@suse.com> --- This is probably fallout from the recent _multibuild migration. util-linux has: %attr(-,uuidd,uuidd) %dir /var/lib/libuuid %attr(-,uuidd,uuidd) %ghost /var/lib/libuuid/clock.txt but does not have Requires: user(uuidd). uuidd has %attr(-,uuidd,uuidd) %dir /var/lib/libuuid %attr(-,uuidd,uuidd) %ghost /var/lib/libuuid/clock.txt but also Requires: group(uuidd). Not including /var/lib/libuuid in util-linux should therefore fix this issue, this is also how it was previously. However: I had a look at the context and it's not clear to me how this state directory should actually be handled. While the directory is owned by uuidd, the clock.txt file is actually used by libuuid, both read and written to. This means that not only uuidd creates it, but any other process running as root (e.g. uuidgen -t) might. If clock.txt was created by root, uuidd would no longer be able to use it due to missing permissions. FWICT the only way to make this reliable is to always create clock.txt as the uuidd user, the directory must not be created empty. Just not creating /var/lib/libuuid/ is probably close enough. -- You are receiving this mail because: You are on the CC list for the bug.