public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org, confabulate@kintzios.com
Subject: Re: [gentoo-user] Problems with commands "reboot" and "shutdown"
Date: Tue, 19 Nov 2024 17:32:23 +0100	[thread overview]
Message-ID: <673cbd99.5d0a0220.20ec5c.3405@mx.google.com> (raw)
In-Reply-To: (message from Dr Rainer Woitok on Fri, 15 Nov 2024 13:10:39 +0100)

Greetings,

On Fri, 15 Nov 2024 13:10:39 +0100 I myself wrote:

> > ...
> > I have no split-usr system here to compare notes, but did you try rebuilding 
> > the sys-auth/elogind package just in case?
> 
> Yes, I did.  With and without USE flag "cgroup-hybrid" which was enabled
> by default up to version 246.10-r4 including  but is disabled by default
> in version 252.9-r2.  Didn't change anything :-(

Well, it turned out my tests have been a bit too quick and dirty.  After
re-emerging package "sys-auth/elogind"  the old "elogind-daemon" service
programme is still executing  and thus clicking on  Xfce's "Restart" ac-
tion button only tests the old binary in its new environment which -- of
course -- isn't guaranteed to work :-(

So between re-emerging  and trying to reboot via Xfce's "Restart" action
button I need to reboot using "/sbin/reboot" to run the "elogind-daemon"
service programme I want to test.

Using this slightly more sophisticated test procedure  I found that both
stable "sys-auth/elogind" ebuilds work while BOTH BINARY PACKAGES DON'T.

As already described in a previous mail, after pressing Xfce's "Restart"
action button  the system stalls or loops indefinitely,  and syslog con-
tains

   2024-11-18T17:55:02+01:00 (5) kernel: elogind-daemon[1835]: System is rebooting.
   2024-11-18T17:55:02+01:00 (3) reboo[5780]: Failed to execute /usr/bin/reboot: No such file or directory

which somehow suggests that "elogind" expects "systemd" to be installed,
while I'm using "openrc".

Quoting a slightly outdated Gentoo webpage [1]:

   The available useflag settings and versions correspond to the
   stable packages of the amd64/17.1/nomultilib (i.e., openrc),
   amd64/17.1/desktop/plasma/systemd, and amd64/17.1/desktop/gnome/systemd
   profiles.

Apart from the outdated "17.1", I'm on neither of these profiles:

   $ eselect profile show
   Current /etc/portage/make.profile symlink:
     default/linux/amd64/23.0/split-usr/desktop
   $

Is THIS the problem?   But if -- as the above quote is suggesting -- the
binaries are coded to work with BOTH,  "openrc" AND "systemd",  then why
don't they work on my laptop?

Baffled,
 Rainer

[1]: https://www.gentoo.org/news/2023/12/29/Gentoo-binary.html


      parent reply	other threads:[~2024-11-19 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-09 17:07 [gentoo-user] Problems with commands "reboot" and "shutdown" Dr Rainer Woitok
2024-11-09 17:14 ` Michael
2024-11-09 18:05   ` Dr Rainer Woitok
2024-11-09 19:38     ` Dale
2024-11-09 23:55       ` Michael
2024-11-10  4:08         ` Dale
2024-11-09 17:58 ` ralfconn
2024-11-10 15:42   ` Steve Evans
2024-11-14 17:35     ` Dr Rainer Woitok
2024-11-14 19:15       ` Michael
2024-11-15 12:10         ` Dr Rainer Woitok
2024-11-15 12:28           ` Dale
2024-11-19 16:32         ` Dr Rainer Woitok [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=673cbd99.5d0a0220.20ec5c.3405@mx.google.com \
    --to=rainer.woitok@gmail.com \
    --cc=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox