/etc/init.d/display-manager fails here as: /usr/bin/startDM: line 17: /lib/rc/sh/functions.sh: No such file or directory Reminder: equery f openrc|grep functions.sh /etc/init.d/functions.sh /usr/libexec/rc/sh/functions.sh /usr/libexec/rc/sh/rc-functions.sh May be missing something here, though.
.. so >=0.56? Which version is bad for you? I suspect something more may be happening, as it would imply no ~arch users using display-manager-init would have noticed since.. commit ea4c2ea555a490aee397a7c5a1d0d2881f7d9f41 Author: William Hubbs <williamh@gentoo.org> Date: Tue Dec 31 12:11:40 2024 -0600 sys-apps/openrc: add 0.56 Signed-off-by: William Hubbs <williamh@gentoo.org> but I'm one of them, and it works OK for me.
bug with display-manager-init's startDM script, which basically seems to entirely bypass openrc but still start a service under it from sysvinit (we seriously shouldn't do this) thus moving an internal file (from /lib/rc to /usr/libexec/rc) broke it. > I suspect something more may be happening, as it would imply no ~arch users using display-manager-init would have noticed since.. the actual init script only calls startDM if the configured vt is already in use by something by what i understood of this. basically forgoing openrc to use sysvinit as the actual trigger with telinit, nasty for now though we should just correct the path, tho doing so for =>openrc-0.56 breaks <=openrc-0.55.1, since 56 is stabilized, non-issue? or we can check both places before sourcing
(In reply to Anna from comment #2) > bug with display-manager-init's startDM script, which basically seems to > entirely bypass openrc but still start a service under it from sysvinit (we > seriously shouldn't do this) > > thus moving an internal file (from /lib/rc to /usr/libexec/rc) broke it. > > > I suspect something more may be happening, as it would imply no ~arch users using display-manager-init would have noticed since.. > > the actual init script only calls startDM if the configured vt is already in > use by something by what i understood of this. basically forgoing openrc to > use sysvinit as the actual trigger with telinit, nasty !!! > > for now though we should just correct the path, tho doing so for > =>openrc-0.56 breaks <=openrc-0.55.1, since 56 is stabilized, non-issue? or > we can check both places before sourcing I'd say check both places to be safe in case people are only partially upgrading or something.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bfc8e3f218e86ee62242d5e0802596cf8efc36c commit 7bfc8e3f218e86ee62242d5e0802596cf8efc36c Author: Anna (navi) Figueiredo Gomes <navi@vlhl.dev> AuthorDate: 2025-03-03 18:29:29 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-03-03 18:37:05 +0000 gui-libs/display-manager-init: Load functions.sh from libexec. Closes: https://bugs.gentoo.org/950508 Signed-off-by: Anna (navi) Figueiredo Gomes <navi@vlhl.dev> Closes: https://github.com/gentoo/gentoo/pull/40875 Signed-off-by: Sam James <sam@gentoo.org> ...init-1.1.2.ebuild => display-manager-init-1.1.2-r1.ebuild} | 2 +- gui-libs/display-manager-init/files/startDM-r1 | 11 ++++++++++- 2 files changed, 11 insertions(+), 2 deletions(-)
Thks 4 quickness.
