From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver 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 Message-ID: <87lfzmuid1.fsf@netris.org> References: <87sgtu2tq7.fsf@gnu.org> <87pnoyuijc.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:55667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hN0PA-0006rs-U2 for bug-guix@gnu.org; Sat, 04 May 2019 15:33:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hN0P8-0005c4-4g for bug-guix@gnu.org; Sat, 04 May 2019 15:33:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:38799) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hN0P8-0005c0-1h for bug-guix@gnu.org; Sat, 04 May 2019 15:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hN0P7-0000UF-Ro for bug-guix@gnu.org; Sat, 04 May 2019 15:33:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87pnoyuijc.fsf@netris.org> (Mark H. Weaver's message of "Sat, 04 May 2019 15:27:08 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 35560@debbugs.gnu.org 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=3Dwayland exec dbus-run-session gnome-session" from a > text console. Perhaps that makes a difference? > >> The thing that=E2=80=99s really bad is that clicking on the eject icon o= f a >> removal storage device in Files leads to a gnome-shell crash that=E2=80= =99s >> unrecoverable (=E2=80=9Crespawning too quickly=E2=80=9D), followed by th= e 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