[SOLVED] Gnome Settings crashing after opening

doofy_doofus · 2023-10-29 17:18:47

I recently installed Gnome on my Arch laptop (dual booting with Windows) and as soon as i booted into the Desktop, I observed that I couldn't open the Settings panel, which keeps on closing right after opening, hitting a segmentation fault.

Visual Demonstration

Last edited by doofy_doofus (2023-11-05 17:48:25)

seth · 2023-10-29 21:40:39

hitting a segmentation fault.
Visual Demonstration

https://wiki.archlinux.org/title/Core_d … _core_dump

Edit:

dual booting with Windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Last edited by seth (2023-10-29 21:41:19)

doofy_doofus · 2023-10-30 06:43:38

Thanks a lot for the quick reply Seth.
The core dump article is extremely valuable and was definitely worth the read.

But interestingly, gnome-control-center hasn't crashed once after disabling fast startup in Windows registry.

My hypothesis is that since Windows isn't actually turned off and is just hibernating, it must have some reserved memory slots, which gnome-control-center was trying to access? I don't know if that is logical by any means, but that's what I think happened.

seth · 2023-10-30 07:41:37

The contentious part isusually some HW, typically wifi, b/c the hibernated system still "occupies" them and leaves them in an undefined state.
The old coredumps should still be there and might hint at the problem (at least the library that caused the crash)

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

doofy_doofus · 2023-10-30 18:51:58

Thanks for the input Seth.

Unfortunately it turns out that it was a false alarm. The issue still persists, and I first observed it after rebooting later that day.
It triggered right after I tried changing the wallpaper (the same thing I tried in the demo vod).

Error Message:

00:13:48.6823                  Gtk[ 2255]: WARNING: Unknown key gtk-modules in /home/mitch/.config/gtk-4.0/settings.ini
00:13:48.7463              Adwaita[ 2255]: WARNING: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
00:13:48.8068        cc-wwan-panel[ 2255]: WARNING: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
[1]    2255 segmentation fault (core dumped)  gnome-control-center background

coredumptctl shows:

Signal: 11 (SEGV)
Timestamp: Tue 2023-10-31 00:12:12 (7min ago)
Command Line: /usr/bin/gnome-control-center background
Executable: /usr/bin/gnome-control-center

and:

Stack trace of thread 2005:
#0  0x00007fbf237ab842 n/a (libc.so.6 + 0x16a842)
#1  0x00007fbf25378dac n/a (libglib-2.0.so.0 + 0x6cdac)
#2  0x00007fbf2537f5ba g_sequence_insert_sorted_iter (libglib-2.0.so.0 + 0x735ba)
#3  0x00007fbf2537f6ac g_sequence_insert_sorted (libglib-2.0.so.0 + 0x736ac)
#4  0x00007fbf2557d34f g_list_store_insert_sorted (libgio-2.0.so.0 + 0xc334f)
#5  0x0000562850a8d32b n/a (gnome-control-center + 0x7c32b)
#6  0x00007fbf2546c6c0 g_closure_invoke (libgobject-2.0.so.0 + 0x146c0)
#7  0x00007fbf2549aa36 n/a (libgobject-2.0.so.0 + 0x42a36)
#8  0x00007fbf2548ba42 n/a (libgobject-2.0.so.0 + 0x33a42)

I really wanted to figure out from the coredump logs myself, but I was really short on time.
Thank you so much for reading.

Last edited by doofy_doofus (2023-10-30 18:55:31)

seth · 2023-10-30 19:30:14

That's not about time - the backtrace unfortunately is as generic as it gets.
But from the context and w/

00:13:48.7463              Adwaita[ 2255]: WARNING: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

I'd clean up that first; post /home/mitch/.config/gtk-4.0/settings.ini

doofy_doofus · 2023-10-30 20:37:13

Here:

[Settings]
gtk-application-prefer-dark-theme=true
gtk-cursor-theme-name=Windows-10-Dark
gtk-cursor-theme-size=32
gtk-decoration-layout=:minimize,maximize,close
gtk-enable-animations=true
gtk-font-name=Noto Sans,  10
gtk-icon-theme-name=Windows-Eleven
gtk-modules=colorreload-gtk-module
gtk-primary-button-warps-slider=false
gtk-theme-name=WhiteSur-Dark-solid
gtk-xft-dpi=98304

Last edited by doofy_doofus (2023-10-30 20:37:36)

seth · 2023-10-30 20:52:13

Remove "gtk-application-prefer-dark-theme=true" and "gtk-modules=colorreload-gtk-module" and see what happens (leaving aside that two of the warnings should disappear)
Ultimately, you might want to try to completely move the file away.

doofy_doofus · 2023-10-31 07:01:49

Yep, the two warnings have disappeared, but the segfault is still there:

12:30:17.9599        cc-wwan-panel[ 3974]: WARNING: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
[1]    3974 segmentation fault (core dumped)  gnome-control-center

seth · 2023-10-31 07:09:26

https://wiki.archlinux.org/title/Debugg … g_packages

Before that

strace -f -o /tmp/gnome-cc.strace gnome-control-center background
cat /tmp/gnome-cc.strace | curl -F 'file=@-' 0x0.st

The cause is, most likely, some custom theme.

doofy_doofus · 2023-10-31 07:33:04

Thanks a lot, Seth.

Curl reports this address:

http://0x0.st/HyyQ.txt

seth · 2023-10-31 07:40:23

6114  +++ exited with 0 +++
6112  +++ exited with 0 +++
6110  +++ exited with 0 +++
6111  +++ exited with 0 +++
6109  +++ exited with 0 +++

That process didn't crash?

doofy_doofus · 2023-10-31 07:58:47

As you might've seen in the vod, the settings window keeps on closing on its own, so i felt "crash" here is an appropriate term.
That too, after a few seconds of opening (because it hits a segfault a couple moments later)

Should I record again?

Last edited by doofy_doofus (2023-10-31 07:59:24)

seth · 2023-10-31 08:02:54

I don't care about the video; the previous posts suggested a segmentation fault that's not reflected in that strace - did it still happen?

doofy_doofus · 2023-10-31 08:06:44

Here's the output, I'll run it again.

13:35:45.6462        cc-wwan-panel[15882]: WARNING: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
[1]    15882 segmentation fault (core dumped)  gnome-control-center background

I find it weird that it says "exited with code 0", when the terminal output clearly shows a segfault right after the window terminates.

Last edited by doofy_doofus (2023-10-31 08:08:56)

seth · 2023-10-31 08:20:34

crash-on-exit?
Can you any of

gnome-control-center -l
gnome-control-center datetime
gnome-control-center -v background # this one will likely crash, but maybe post something interesting

Also, just a hunch

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

doofy_doofus · 2023-10-31 08:34:48

The first command just shows a list of panels, nothing else to see there.
datetime seems to open fine, no crashes there. I checked with keyboard too, and that doesn't close either. Maybe it's something specific to background?

The third command yields this:

14:00:12.4339        cc-wwan-panel[17288]: WARNING: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: Unit dbus-org.freedesktop.ModemManager1.service not found.
[1]    17288 segmentation fault (core dumped)  gnome-control-center --verbose background

loginctl:

5 - mitch (1000)
         Leader: 2470 (lightdm)
         Seat: seat0; vc7
         Display: :0
         Service: lightdm; type x11; class user
         Desktop: gnome
           State: active
            Idle: no
            Unit: session-5.scope
                  ├─2470 lightdm --session-child 12 20
                  └─2482 /usr/lib/gnome-session-binary

Oct 31 12:29:07 Arch systemd[1]: Started Session 5 of User mitch.

$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

seth · 2023-10-31 12:31:20

The session is ok - mut maybe it does try to talk to GDM?

dbus-monitor --session
dbus-monitor --system # you'll have to run those in twoother terminals
gnome-control-center background # check what's going on on the session and system bus

Another stumbling stone could be some invalid wallpaper in the wallpaper path?
(Though the process itself doesn't open anything in your $HOME)

doofy_doofus · 2023-11-01 17:34:11

Thank you for the input again, Seth.

--system had no anomalies, there wasn't much to look at.
I'm bit confused looking at the output of --session. There was definitely lots going on as soon as I launched gnome-control-center.

Frankly, I'm not able to make heads or tails of it.

http://0x0.st/HyIG.txt

seth · 2023-11-01 20:52:56

This is weird

method call time=1698766911.648642 sender=:1.95 -> destination=org.freedesktop.DBus serial=35 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.gnome.Shell',interface='org.gnome.Shell',path='/org/gnome/Shell'"
method return time=1698766911.648662 sender=org.freedesktop.DBus -> destination=:1.95 serial=27 reply_serial=35
method call time=1698766911.648673 sender=:1.95 -> destination=org.freedesktop.DBus serial=36 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',path='/org/freedesktop/DBus',arg0='org.gnome.Shell'"
method return time=1698766911.648691 sender=org.freedesktop.DBus -> destination=:1.95 serial=28 reply_serial=36
method call time=1698766911.648701 sender=:1.95 -> destination=org.freedesktop.DBus serial=37 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.gnome.Shell"
   uint32 0
error time=1698766911.648730 sender=org.freedesktop.DBus -> destination=:1.95 error_name=org.freedesktop.DBus.Error.ServiceUnknown reply_serial=37
   string "The name org.gnome.Shell was not provided by any .service files"
method call time=1698766911.649915 sender=:1.95 -> destination=org.freedesktop.DBus serial=38 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetNameOwner
   string "org.gnome.Shell"
method return time=1698766911.649964 sender=org.freedesktop.DBus -> destination=:1.95 serial=30 reply_serial=38
   string ":1.24"
method call time=1698766912.139577 sender=:1.95 -> destination=:1.24 serial=39 path=/org/gnome/Shell; interface=org.freedesktop.DBus.Properties; member=GetAll
   string "org.gnome.Shell"
method return time=1698766912.140344 sender=:1.24 -> destination=:1.95 serial=587 reply_serial=39
   array [
      dict entry(
         string "Mode"
         variant             string "user"
      )
      dict entry(
         string "OverviewActive"
         variant             boolean false
      )
      dict entry(
         string "ShellVersion"
         variant             string "45.0"
      )
   ]
signal time=1698766912.912343 sender=org.freedesktop.DBus -> destination=:1.95 serial=31 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string "org.gnome.Settings"

Also your loginctl session-status lists only two processes? (lightdm --session-child and gnome-session-binary)

Is this a regular gnome session or did you customize it?
Because it's gnome: are you willing to try to substitute lightdm w/ gdm for a test?

doofy_doofus · 2023-11-01 21:18:19

Nope. I just installed the gnome group using pacman and logged into it (the login entry that reads "GNOME" only)

Yep, I would like to try GDM. Could using a non-native DM be the reason why legacy apps open a bit slow? (I had this problem in cinnammon too)
sorry I'm a bit new to this.

Last edited by doofy_doofus (2023-11-01 21:23:46)

seth · 2023-11-01 21:46:50

The DM should™ not have any impact on the DE, but just the other day there was a thread where it turned out that gnome's screen locking doesn't work if you're not using GDM…

doofy_doofus · 2023-11-01 22:06:41

So I went through some articles, and what's the right way to switch to GDM as the main graphical login prompt + DM?
I'm confused between using .xprofile and creating a graphical.target symlink to GDM. Puzzling stuff as a beginner

Last edited by doofy_doofus (2023-11-01 22:11:10)

seth · 2023-11-01 22:15:29

https://wiki.archlinux.org/title/GDM#Starting
You can also explcitily disable lightdm first, but that should™ not be necessary, https://wiki.archlinux.org/title/Displa … ay_manager

xprofile has nothing to do with that - it's sourced by some DMs or sessions *after* you login.

doofy_doofus · 2023-11-01 22:29:40

Yes. I just enabled gdm.service.

Unfortunately, stuff has gone haywire. Gnome settings is still crashing after rebooting, albeit the DM has changed.
I initially used xrandr to stretch to a 4x3 resolution but now xrandr just refuses to work:

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  11 (RRQueryOutputProperty)
  Serial number of failed request:  22
  Current serial number in output stream:  22

loginctl:

             TTY: tty2
         Service: gdm-password; type wayland; class user
           State: active
            Idle: no
            Unit: session-3.scope
                  ├─1002 "gdm-session-worker [pam/gdm-password]"
                  ├─1076 /usr/lib/gdm-wayland-session /usr/bin/gnome-session
                  └─1088 /usr/lib/gnome-session-binary

[1]    4168 segmentation fault (core dumped)  gnome-control-center background

$ coredumpctl info 4168 | grep "Signal"
        Signal: 11 (SEGV)

Arch Linux

#1 2023-10-29 17:18:47

[SOLVED] Gnome Settings crashing after opening

#2 2023-10-29 21:40:39

Re: [SOLVED] Gnome Settings crashing after opening

#3 2023-10-30 06:43:38

Re: [SOLVED] Gnome Settings crashing after opening

#4 2023-10-30 07:41:37

Re: [SOLVED] Gnome Settings crashing after opening

#5 2023-10-30 18:51:58

Re: [SOLVED] Gnome Settings crashing after opening

#6 2023-10-30 19:30:14

Re: [SOLVED] Gnome Settings crashing after opening

#7 2023-10-30 20:37:13

Re: [SOLVED] Gnome Settings crashing after opening

#8 2023-10-30 20:52:13

Re: [SOLVED] Gnome Settings crashing after opening

#9 2023-10-31 07:01:49

Re: [SOLVED] Gnome Settings crashing after opening

#10 2023-10-31 07:09:26

Re: [SOLVED] Gnome Settings crashing after opening

#11 2023-10-31 07:33:04

Re: [SOLVED] Gnome Settings crashing after opening

#12 2023-10-31 07:40:23

Re: [SOLVED] Gnome Settings crashing after opening

#13 2023-10-31 07:58:47

Re: [SOLVED] Gnome Settings crashing after opening

#14 2023-10-31 08:02:54

Re: [SOLVED] Gnome Settings crashing after opening

#15 2023-10-31 08:06:44

Re: [SOLVED] Gnome Settings crashing after opening

#16 2023-10-31 08:20:34

Re: [SOLVED] Gnome Settings crashing after opening

#17 2023-10-31 08:34:48

Re: [SOLVED] Gnome Settings crashing after opening

#18 2023-10-31 12:31:20

Re: [SOLVED] Gnome Settings crashing after opening

#19 2023-11-01 17:34:11

Re: [SOLVED] Gnome Settings crashing after opening

#20 2023-11-01 20:52:56

Re: [SOLVED] Gnome Settings crashing after opening

#21 2023-11-01 21:18:19

Re: [SOLVED] Gnome Settings crashing after opening

#22 2023-11-01 21:46:50

Re: [SOLVED] Gnome Settings crashing after opening

#23 2023-11-01 22:06:41

Re: [SOLVED] Gnome Settings crashing after opening

#24 2023-11-01 22:15:29

Re: [SOLVED] Gnome Settings crashing after opening

#25 2023-11-01 22:29:40

Re: [SOLVED] Gnome Settings crashing after opening

Board footer