Arch Linux

linerman

Member

Registered: 2021-02-16

Posts: 88

How to disable faulty config (gnome-extensions?)

Hi,

After my weekly update, my gnome desktop went wild. Almost nothing works, no way to get to the journal.
My suspicious went to gnome-extensions. They look disabled but still there is something....
Anyway, I downgraded system, created new gnome user then I upgraded system again. After that, new user with clear gnome works flawlessly, old one has the same problem as earlier.

So, is there any way to not to configure the new user from the scratch but rather delete/disable old user faulty config? 

Regards,
L.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,612

Re: How to disable faulty config (gnome-extensions?)

Empty out .local/share/gnome-shell/extensions
Note that will clear extensions, but will not be a start from 'scratch'

If that does not work, do the same  to .local/share/gnome-shell/

Last edited by ewaller (2023-08-05 22:47:04)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

linerman

Member

Registered: 2021-02-16

Posts: 88

Re: How to disable faulty config (gnome-extensions?)

After two days of digging inside my system...it turned out that this one: https://bbs.archlinux.org/viewtopic.php?id=287224 is connected.
The problem was actually Xscreensaver and SystemD service.

When I removed from ~/systemd/user/xscreensaver.service (I found that one on wiki but it doesn't exist anymore)

 
[Unit]
Description=XScreenSaver
[Service]
ExecStart=/usr/bin/xscreensaver --no-splash
[Install]
WantedBy=default.target

the problem immediately was gone (means extensions were not disabled and there were no white screen with info: something went wrong, please log off) plus the journal showed no errors anymore.
Anyway, noticed that every 3 times when screensaver was running, after returning to session, the error occurred again.
Needed to remove Xcreensaver from running to solve the problem completely. So the problem is gone but I stayed with no screensaver at all...

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,307

Re: How to disable faulty config (gnome-extensions?)

"ExecStartPre=/usr/bin/sleep 5"?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

linerman

Member

Registered: 2021-02-16

Posts: 88

Re: How to disable faulty config (gnome-extensions?)

I put that

[Unit]
Description=XScreenSaver
[Service]
ExecStartPre=/usr/bin/sleep 5
ExecStart=/usr/bin/xscreensaver --no-splash
[Install]
WantedBy=default.target 

without adding Xscreensaver to Gnome autostart for a test.
After manually launching the daemon, I wait for screensaver to run. Immediately after screensaver starts, gnome-shell crashed.
So I guess it is the Xcreensaver-arch-no logo package, is it?

Last edited by linerman (2023-08-22 06:24:11)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,307

Re: How to disable faulty config (gnome-extensions?)

If gnome crashes running some X11/xwayland client that's more like a gnome issue, but I'd try the behavior of https://archlinux.org/packages/?name=xscreensaver first and if that doesn't cause this, make sure you've rebuilt the AUR package after recent updates.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc