all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Martin Castillo <castilma@uni-bremen.de>
Cc: help-guix@gnu.org
Subject: Re: getting loginctl to work
Date: Thu, 23 Mar 2023 20:09:04 +0100	[thread overview]
Message-ID: <87ttybcmhd.fsf@riseup.net> (raw)
In-Reply-To: <bcac7d5a-ffb1-1baa-8b66-2041616a8d7b@uni-bremen.de>


Martin Castillo <castilma@uni-bremen.de> writes:

> Hi,
>
> I have guix system installed and want `loginctl poweroff` to work. I'm
> logged in via ssh. The vm is started using
> qemu-system-x86_64   -drive media=disk,file=geex-unenc.img,format=raw
> -bios /usr/share/ovmf/x64/OVMF.fd  -m 2G   -smp 3 -nic
> user,model=virtio-net-pci,hostfwd=tcp::2223-:22 -enable-kvm
>
>
> Currently loginctl does not work:
> $ strace -o loginctl.str loginctl poweroff
> returns 1 and prints no errors.
> loginctl.str shows some partial error message. I don't know how to get
> loginctl or dbus to be more verbose and show me the error.
> /var/log/secure does not show anything regarding that error.
>
> $ loginctl list
> SESSION UID USER SEAT  TTY
>      c1 983 gdm  seat0 tty7
>
> 1 sessions listed.
>
>
> First I tried configuring %base-services plus elogind-service-type,
> but it didn't work, so I tried %desktop-services, and it still doesn't
> work, but I'm sure it should. My (approximate) configuration.scm is
> attached.
>
>
> Martin
>
> [2. text/x-scheme; configuration.scm]...
>
> [3. application/vnd.pg.format; loginctl.str]...

Could it be that something is holding an inhibit lock on shutdown?  I
think ssh can do that.  It might even be automatic??
Try running elogind-inhibit with no arguments.


  reply	other threads:[~2023-03-23 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 21:20 getting loginctl to work Martin Castillo
2023-03-23 19:09 ` Csepp [this message]
2023-03-24 16:04   ` Martin Castillo
2023-03-27 10:21 ` SeerLite
2023-03-27 13:18   ` Martin Castillo

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=87ttybcmhd.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=castilma@uni-bremen.de \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.