From: Reza Housseini <reza.housseini@gmail.com>
To: help-guix@gnu.org
Subject: GNOME issues with gsd-usb-protect
Date: Fri, 06 Sep 2024 21:14:41 +0200 [thread overview]
Message-ID: <87mskky4pq.fsf@housseini.me> (raw)
Hi Guix
Since a while now when I start gnome desktop I get a "Oops something
went wrong" error. Looking at /var/log/messages there is a segfault
involving gsd-usb-protection from
org.gnome.desktop.SettingsDaemon.UsbProtection. Searching the web there
where problems with this but they all seem to be resolved. When trying
to disable this daemon through dconf-editor (gsettings seems not
available) I notice there is no org.gnome.desktop.SettingsDaemon entry
only org.gnome.desktop.settings-daemon.plugins without a UsbProtection
entry. In the bug reports mentioned they claim that the segfault is
caused by org.gnome.desktop.SettingsDaemon.ScreesaverProxy but this
entry is also nowhere present. I am a little confused. Can somebody with
more experience shed some light on this issue, why are they two
incompatible settings daemon names and why is dconf-editor available but
gsettings not (and why is dconf and dconf-editor containing different
entries)?
Thanks and greetings,
Reza Housseini
reply other threads:[~2024-09-06 19:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mskky4pq.fsf@housseini.me \
--to=reza.housseini@gmail.com \
--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).