Solved gnome-control-center segfault

[VentGrey]

Trying to set the red-light night thingy from gnome-control-center -> screens/monitor causes the app to segfault and be unable to be re-launched from the menu.

I was able to make it run again by typing gsettings set org.gnome.ControlCenter last-panel '', however repeating the "screens" step makes the system crash again. I don't know if this might be related but here is the console output:

(gnome-control-center:77432): Gtk-CRITICAL **: 21:39:52.609: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
Segmentation Fault

Any Ideas on why is this happening or how can I debug to a deeper level the settings app?

 

[derpOmattic]

Using this is making Settings crash?

 

[VentGrey]

Clicking on this option makes it crash

(sorry it's in spanish)

 

[derpOmattic]

Not sure I'm following where that is exactly. I'm looking at 20.04 and 20.10. Can you provide a larger context, a bigger screen capture to show where you're seeing that?

 

[VentGrey]

Well, this seemed trange to me, as I've only updated, but yesterday my night light stopped working and I was like . So I decided to go in here:

However when I click the "Screen" option ("Pantallas") the control center just closes. Trying to run in from a terminal just results in the code I pasted up there. I tried installing `coredumpctl` but I've got no useful information apart from it trying to access restricted memory spaces.

 

[derpOmattic]

Oh, from that left menu. You don't even get into the "Screen Display" window. I have no trouble with the default, so I'm wondering if that is input specific. I'll poke around and see if it is a known issue. In the meantime, you could have a terminal open running journalctl -f, which will show you what's happening while you're clicking on it.
If the output is too much, you can limit it with --level or -p for priority.

journalctl -k -p 3 -f

The -k flag adds kernel messages, like dmesg output. The priority of 3 is "errors", and -f is following the output. If you know the PID or service name, we can modify the log parameters.

 

[VentGrey]

Managed to fix it it was trying to call hdpi-daemon which I had "restricted" 'cause it was eating my precious resources. Sorry for the trouble caused!

 

[derpOmattic]

We're all learning from each other, and Planet can document it for others.