all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35560@debbugs.gnu.org
Subject: bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media
Date: Sat, 04 May 2019 15:30:55 -0400	[thread overview]
Message-ID: <87lfzmuid1.fsf@netris.org> (raw)
In-Reply-To: <87pnoyuijc.fsf@netris.org> (Mark H. Weaver's message of "Sat, 04 May 2019 15:27:08 -0400")

Earlier, I wrote:

> FWIW, I've found GNOME Shell to be quite solid on my X200, including
> since the 3.28 upgrade.  However, I run it under Wayland, by running
> "XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session" from a
> text console.  Perhaps that makes a difference?
>
>> The thing that’s really bad is that clicking on the eject icon of a
>> removal storage device in Files leads to a gnome-shell crash that’s
>> unrecoverable (“respawning too quickly”), followed by the laptop
>> entering suspend-to-RAM without prior notice (!):
>
> I just tried this, and it works fine for me.

I should also mention that unlike Timothy and Ricardo, I've *not* done
any cleaning of my GNOME-related configuration/state.  I also never
experienced the crashes that were apparently fixed by commit
c5db31d4141669d09c1cd8b37eb270c2fe23c7cf.

       Mark

  reply	other threads:[~2019-05-04 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 14:13 bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after ejecting removable media Ludovic Courtès
2019-05-04 14:43 ` Timothy Sample
2019-05-04 16:40   ` Ricardo Wurmus
2019-05-04 14:52 ` pelzflorian (Florian Pelz)
2019-05-04 19:27 ` Mark H Weaver
2019-05-04 19:30   ` Mark H Weaver [this message]
2019-05-04 19:54     ` Ricardo Wurmus
2021-12-14 16:51       ` Maxim Cournoyer
2021-12-14 16:48 ` Ludovic Courtès

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=87lfzmuid1.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=35560@debbugs.gnu.org \
    --cc=ludo@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.