From: Thomas Danckaert <post@thomasdanckaert.be>
To: help-guix@gnu.org
Subject: gnome shell crashes after ~1m
Date: Wed, 13 Jul 2022 11:28:29 +0200 (CEST) [thread overview]
Message-ID: <20220713.112829.1147910227408114415.post@thomasdanckaert.be> (raw)
Dear mailing list,
after 5 months without updating my system (I know!), I just ran guix
pull and reconfigured my system with the latest gnome desktop.
Unfortunately, when I start this latest system generation, gnome
shell crashes after about 1 minute (I get the “oops, something went
wrong” grey screen of death).
Looking in the logs (/var/log/messages and ~/.cache/gdm/session.log),
I find the messages involving
org.gnome.SettingsDaemon.UsbProtection.desktop that coincide with the
moment of the crash. Here are the messages from session.log:
** (gsd-usb-protection:1051): WARNING **: 11:15:06.587: Failed to
connect to the screen saver: Error calling StartServiceByName for
org.gnome.ScreenSaver: Timeout was reached
gnome-session-binary[842]: WARNING: Application
'org.gnome.SettingsDaemon.UsbProtection.desktop' killed by signal 11
** (gsd-power:1063): WARNING **: 11:15:06.855: Failed to connect to
the screen saver: Error calling StartServiceByName for
org.gnome.ScreenSaver: Timeout was reached
(gsd-power:1063): GLib-GObject-WARNING **: 11:15:06.855: invalid
(NULL) pointer instance
(gsd-power:1063): GLib-GObject-CRITICAL **: 11:15:06.855:
g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)'
failed
** (gsd-usb-protection:1443): WARNING **: 11:15:31.652: Failed to
connect to the screen saver: Error calling StartServiceByName for
org.gnome.ScreenSaver: Timeout was reached
gnome-session-binary[842]: WARNING: Application
'org.gnome.SettingsDaemon.UsbProtection.desktop' killed by signal 11
gnome-session-binary[842]: WARNING: App
'org.gnome.SettingsDaemon.UsbProtection.desktop' respawning too
quickly
Any suggestions for solutions or workarounds? Has anybody else
experienced this behaviour? Due to the long time between updates
(previous generation was from February), it might not be obvious to
track the change that causes this error (likely a new gnome desktop
version I suppose...).
sincerely,
Thomas
next reply other threads:[~2022-07-13 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:28 Thomas Danckaert [this message]
2022-07-13 10:29 ` gnome shell crashes after ~1m paren--- via
2022-07-13 12:41 ` Thomas Danckaert
2022-07-13 12:48 ` Luis Felipe
2022-07-14 9:28 ` Daniel Meißner
2022-07-14 11:30 ` Thomas Danckaert
2022-07-17 18:49 ` Reza Housseini
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=20220713.112829.1147910227408114415.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--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.
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).