From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#35560: GNOME Shell 3.28 crashes and suspends to RAM (!) after
	ejecting removable media
Date: Sat, 04 May 2019 21:54:16 +0200
Message-ID: <874l6aknbr.fsf@elephly.net>
References: <87sgtu2tq7.fsf@gnu.org> <87pnoyuijc.fsf@netris.org>
	<87lfzmuid1.fsf@netris.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:58897)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hN0lP-0003ab-Cq
	for bug-guix@gnu.org; Sat, 04 May 2019 15:56:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hN0lO-0002KM-4Q
	for bug-guix@gnu.org; Sat, 04 May 2019 15:56:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:38826)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1hN0lO-0002KI-0j
	for bug-guix@gnu.org; Sat, 04 May 2019 15:56:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hN0lN-00017D-Tp
	for bug-guix@gnu.org; Sat, 04 May 2019 15:56:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.35560.B.15569997034198@debbugs.gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:58669)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1hN0kG-0003Rf-EE
	for bug-guix@gnu.org; Sat, 04 May 2019 15:54:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1hN0kD-0001lp-Ns
	for bug-guix@gnu.org; Sat, 04 May 2019 15:54:52 -0400
Received: from sender4-of-o53.zoho.com ([136.143.188.53]:21360)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <rekado@elephly.net>) id 1hN0kD-0001l2-6b
	for bug-guix@gnu.org; Sat, 04 May 2019 15:54:49 -0400
In-reply-to: <87lfzmuid1.fsf@netris.org>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: 35560@debbugs.gnu.org


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

> 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 =
of 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 t=
he 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.

The crashes would only happen if stale notifications were loaded up by
the new GNOME.

--=20
Ricardo