On Sun, Jan 17, 2021 at 19:04:17 +0100, Michael Biebl wrote: > On Thu, 2 Jul 2020 13:57:55 +0100 Mark Hindley <[email protected]> wrote: > > These dependencies are not updated. Please don't close and archive > > unresolved > > bugs without notification or explanation. > > The situation regarding inhibitors has not been resolved (despite the false > claims in #40).
What parts of my previous comments in #40 are you perceiving to be "false claims"? Upstream _does_ mention supporting elogind in their release notes: https://github.com/storaged-project/udisks/blob/master/NEWS#L1227 Elogind _is_ ABI-compatible since 241.1. Citing from the release notes: “This is the first release that is fully ABI compatible to libsystemd, meaning that applications built against libsystemd can be used with libelogind as drop-in replacement.” - https://github.com/elogind/elogind/releases/tag/v241.1 (This is followed by a short list of stub-only interfaces, which are only provided to achieve ABI-compatibility. Afaict they don't affect udisks) Elogind _does_ document inhibitors working: Eg, here are Debian's manpages for the elogind-inhibit command: https://manpages.debian.org/testing/elogind/elogind-inhibit.1.en.html With all due respect, while it is ofc possible we were talking past each other or that I made an error in my comments, I'd prefer my mistakes to be pointed out directly and/or being asked for clarification instead of a silent close&archive followed by a later accusation of "false claims". > I doubt it is really fixable on a system where logind and > PID 1 don't actually communicate with each other (i.e. sysvinit). > Due to this unfixable nature of the problem, I closed it. The proper way to shutdown/reboot a system using elogind is asking elogind to do the shutdown respecting all inhibitors. See eg: https://wiki.gentoo.org/wiki/Elogind#Usage https://manpages.debian.org/testing/elogind/loginctl.1.en.html#System_Commands loginctl also doing shutdowns etc (unlike systemd's version) is mentioned in the README of elogind's Debian package. A _privileged_ user can still force a shutdown without respecting inhibitors by eg using other means of initiating a shutdown, but this is afaik also true for systemd. If you still feel there is some problem, with allowing users to choose elogind, could you please elaborate on what those problems are? I'm confident we can find a solution for this. Regards Nils _______________________________________________ Pkg-utopia-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
