<div dir="ltr"><div dir="ltr"><div>Hi Everybody,</div><div>I'm Lorenzo Puliti, a Debian Sid user.</div><div>During the last year, in order stay away from systemd and at the same time have a "Hey, my desktop is working again!" experience, i somehow manage to build an usable elogind.</div><div>Now i'm using v239 with a packaging similar to the one posted by Mark Hindley.</div><div>Among the differences, in control file i have also a Breaks+Replace: systemd-shim , Recommends: dbus-x11 + xserver-xorg-legacy and also i'm starting and managing elogind with runit.</div><div><br></div><div>Ian Jackson wrote:</div><div>> Is there anyone here with the kind of desktoppy knowledge who could</div><div>> debug this ?</div><div>I'm afraid you mean a developer, and i can't really debug this, but I have some info about Debian and Elogind I would like to share.</div><div>Some or all the things i'm about to write may result pointless or obvious to you, nevertheless i feel like making other people waste their time to find out what I already know is worst that sending one email with pointless info.</div><div> </div><div>As far as I can tell, from almost 1 year of everyday use in Debian Sid:</div><div> </div><div> - LXQT and KDE/Plasma: basic stuff like shutdown/reboot/suspend , plug in a usbpendrive and be able to mount/umount as user, edit root files with a graphic text editor like kate/kwrite, inhibitor logic, all works fine for me.</div><div><br></div><div> - usable display managers I have tested are Lightdm+gtk-greeter, Sddm and Slim (Slim works but has no logind code)</div><div> </div><div> - ACL's: have not tested this since my user is in video and audio groups, but log looks promising to me [see full-log]</div><div><br></div><div> - Pulseaudio/ Wayland: can't tell, never used/ tested</div><div><br></div><div><br></div><div> About Lightdm error:</div><div> Peter Maydell wrote (in attachment):</div><div> > That's sufficient that basic lightdm and MATE work, though the</div><div> > shutdown/restart/etc menu items in the greeter are greyed out.</div><div> > ....</div><div> > * there are some errors in the log about "no session 'foo' known".</div><div> > This is my current best guess for why the shutdown items aren't there.</div><div> </div><div>I have the ' Failed to release session: No session 'c4' known ' error as well but</div><div>lightdm shutdown/restart/suspend buttons are not grayed and works as expected. </div><div>Since you said that your elogind create a session, my best guess is that </div><div> * you forgot to enforce the right boot order (dbus --> elogind --> lightdm ) or</div><div> * something went wrong when you rebuild polkit-1</div><div>You can check the latter with dbus, once you have logged in with your user in MATE,</div><div> $ dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanReboot</div><div> the reply should say "yes"</div><div><br></div><div>and MATE:</div><div> Matthew Vernon wrote:</div><div> > Relevant bugs include</div><div> > <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909192">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909192</a></div><div>already wrote a reply there, but I forgot to mention that, just to make things worst, since v239-10 systemd has 'conflict:consolekit' and v239-4 drop the patch for the shim.</div><div> Peter Maydell wrote (in attachment):</div><div> >* mate-power-manager Depends on systemd|consolekit, so it</div><div> > won't install. I think this is laptop battery info, not</div><div> > shutdown/restart related, though.</div><div> ....</div><div> >* Recommends in the dependency chain for packages like</div><div> > 'mate-desktop-environment' and 'gdm3' have a tendency to</div><div> > want to toss out elogind and pull in systemd. I had to</div><div> > do a lot of --no-install-recommends.</div><div>I tried to install and test MATE, I had to rebuild mate-power-manager (just changing Depends into : systemd|consolekit|elogind) and following backward the chain of dependency and recommends i found out that, even if one has libpam-elogind that provides libpam-systemd, there are still 'gvfs-backend' and 'gnome-keyring' left that keep pulling in systemd. Installing those two with --no-install-recommends fix the problem.</div><div>Suspend, shutdown and mounting a usb pendrive tested, looks like it's working.</div><div>About the power-manager, i don't have a laptop to test brightness or lid-close events, but it's setting one inhibitor with elogind's code, so</div><div>there is some hope.. [see mate-lightdm-log]</div><div><br></div><div>Other problems i see are:</div><div><br></div><div>* I don't have this with v238 or v236, I already reported upstream as a v239 bug [ see full-log]</div><div> auth.err: Nov 4 18:05:06 elogind[2395]: Failed to register SIGINT handler: Device or resource busy</div><div><br></div><div>* each time i do 'su' in console i have this (but su works anyway) [ see full-log]</div><div> authpriv.debug: Nov 4 17:05:59 su: pam_elogind(su-l:session): Cannot create session: Already running in a session or user slice</div><div><br></div><div>* Gnome3/gdm: systemd is a hard run time dependency for some component, so they need to be rebuilded. </div><div> I'm not a Gnome fan so i've not experimented with this, but if you're interested in, there is a Gentoo related project about this on github</div><div> <a href="https://github.com/dantrell/gentoo-project-gnome-without-systemd">https://github.com/dantrell/gentoo-project-gnome-without-systemd</a></div><div> also there was a post on Devuan forum</div><div> <a href="https://dev1galaxy.org/viewtopic.php?id=1581">https://dev1galaxy.org/viewtopic.php?id=1581</a></div><div><br></div><div>* Xorg and startx [see Xorg-log]:</div><div> Since when rootless Xorg was introduced in Debian,i'm not able to start X with 'startx' from a VT console: I suspect that, </div><div> even if Xorg-legacy is used, xorg requires that the user that start Xorg belong to a session, otherwise it fails.</div><div> Now the problem is that elogind doesn't manage VT user sessions, so it's impossible for the user that is starting Xorg</div><div> to be part of a session. Maybe can be workaround with a Xorg rebuild, I had no l luck with that..</div><div><br></div><div>Hope this will help to bring Elogind in Debian,</div><div>Lorenzo</div></div></div><br><div class="gmail_quote"><div dir="ltr">Il giorno lun 29 ott 2018 alle ore 20:40 Ian Jackson <<a href="mailto:ijackson@chiark.greenend.org.uk">ijackson@chiark.greenend.org.uk</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Andreas Messer writes ("Re: [chiark.chat] Re: RFH: sysvinit etc. in Debian"):<br>
> Any patches, help or git pull requests are welcome. I also have the feeling,<br>
> that the current Devuan elogind package repo is not in the best shape<br>
> regarding its structure. It was actually my first package and I'm still <br>
> a beginner in this.<br>
<br>
Your package pretty good to me. I reviewed the packaging pretty<br>
carefully and everything was as I would have expected, or else had an<br>
explanation.<br>
<br>
> I'm currently going to clarify with the Devuan guys, how the packaging <br>
> workflow shall be for future devuan version, one of them has clear idea of<br>
> this but i did not understand it yet. In parallel I'll start<br>
> a small guide document on how a package repo should be structured <br>
> and handled. Mostly to remind my self of that but maybe this is usefull<br>
> for others as well<br>
<br>
I think that for good sysvinit support in Debian it is important that<br>
not only the sysvinit package is in shape (I'm glad to see that people<br>
are working on that) but also that the desktop support is in good<br>
enough shape that people don't find the dependencies keep pulling in<br>
systemd.<br>
<br>
To fix that we need to upload elogind and/or consolekit to Debian,<br>
figure out what the dependencies should look like in all those<br>
packages, and file bugs in Debian (where we can't use virtual<br>
packages). We want to get all of that into the Debian freeze.<br>
<br>
Peter already gave some instructions on how to test this and we have a<br>
first cut of a package, but there are still some problems and things<br>
we don't know how to do, as discussed earlier.<br>
<br>
Is there anyone here with the kind of desktoppy knowledge who could<br>
debug this ? Or maybe who has some contacts (within Devuan or Debian<br>
or elsewhere) ?<br>
<br>
Ian.<br>
<br>
-- <br>
Ian Jackson <<a href="mailto:ijackson@chiark.greenend.org.uk" target="_blank">ijackson@chiark.greenend.org.uk</a>> These opinions are my own.<br>
<br>
If I emailed you from an address @<a href="http://fyvzl.net" rel="noreferrer" target="_blank">fyvzl.net</a> or @<a href="http://evade.org.uk" rel="noreferrer" target="_blank">evade.org.uk</a>, that is<br>
a private address which bypasses my fierce spamfilter.<br>
<br>
</blockquote></div>