unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 33592@debbugs.gnu.org
Subject: bug#33592: "herd restart term-tty2" caused *all* processes to be killed
Date: Mon, 03 Dec 2018 09:44:15 +0100	[thread overview]
Message-ID: <87k1kratk0.fsf@gnu.org> (raw)
In-Reply-To: <87tvjvmmt3.fsf@netris.org> (Mark H. Weaver's message of "Sun, 02 Dec 2018 20:16:29 -0500")

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Hello,

Mark H Weaver <mhw@netris.org> skribis:

> After killing a Wayland 'gnome-session' that I had launched from the
> command-line on tty2, the login prompt did not return as it normally
> does.
>
> I decided to try "herd restart term-tty2" to see if that would help.
> That turned out to be a serious mistake.  It caused TERM to be sent to
> all processes, most filesystems to be unmounted, and many (all?) core
> services to be stopped.  This left my system in a unusuable state,
> besides being able to switch between otherwise unresponsive text virtual
> terminals and issue SysRq commands.

Per ‘guix system shepherd-graph desktop.tmpl’, the only dependent of
‘term-tty2’ is ‘console-font-tty2’.

I just tried in a desktop.tmpl VM and only ‘console-font-tty2’ is
restarted (screenshot attached.)  Same on my laptop, which uses Xorg but
not GNOME.

Could it be something with the Wayland-related services?  Could you
check ‘guix system shepherd-graph’ on your config?

Thanks,
Ludo’.


[-- Attachment #2: the screenshot --]
[-- Type: image/png, Size: 57396 bytes --]

  reply	other threads:[~2018-12-03  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  1:16 bug#33592: "herd restart term-tty2" caused *all* processes to be killed Mark H Weaver
2018-12-03  8:44 ` Ludovic Courtès [this message]
2018-12-04  2:10   ` Mark H Weaver

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87k1kratk0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33592@debbugs.gnu.org \
    --cc=mhw@netris.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).