Bug#1076728: elogind: privileged operation with polkit fails
Andrew Bower
andrew at bower.uk
Wed Jan 8 09:24:59 GMT 2025
On Wed, Jan 08, 2025 at 08:49:28AM +0000, Andrew Bower wrote:
> Control: tags -1 patch
>
> On Wed, Jan 08, 2025 at 07:33:31AM +0000, Mark Hindley wrote:
> > On Tue, Jan 07, 2025 at 09:28:48PM +0100, Thorsten Glaser wrote:
> > > >> before mounting cgroups there. So, adding elogind to LSB header 'Should-Start'
> > >
> > > >I just tried exactly this with syvinit and it works! Docker also works.
> > >
> > > So maybe an X-Start-Before in elogind?
> >
> > Thanks. I always forget ordering can be specified that way as well.
> >
> > Andrew,
> >
> > If you can verify that works as well we can fix this in elogind without
> > reassigning.
>
> That works, too, thanks!
>
> diff -Nru elogind-255.5/debian/elogind.init elogind-255.5/debian/elogind.init
> --- elogind-255.5/debian/elogind.init 2024-08-05 10:57:36.000000000 +0100
> +++ elogind-255.5/debian/elogind.init 2025-01-08 08:32:44.000000000 +0000
> @@ -3,7 +3,8 @@
> # Provides: elogind
> # Required-Start: dbus $remote_fs $syslog
> # Required-Stop: dbus $remote_fs $syslog
> -# X-Start-Before: $x-display-manager
> +# X-Start-Before: docker $x-display-manager
> +# X-Stop-After: docker
> # Default-Start: 2 3 4 5
> # Default-Stop: 0 1 6
> # Short-Description: start elogind at boot time
Corresponding patch proposed for runit, which might help the OP's case,
although I don't recall if I ever saw this go wrong under runit,
personally:
https://salsa.debian.org/debian/runit-services/-/merge_requests/17
More information about the Debian-init-diversity
mailing list