Settings crashes when I click "Devices"(Enheter in norwegian) tap

[Lars Bahner]

Not much to say. It crashes every time, I cleick devices - and then continues to crash on every start up. Trying the command:

  gsettings reset org.gnome.ControlCenter last-panel

as a known workaround for a similar problem, will let me access gnome-control-center and use it, until I click Devices again.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.1-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jun 2 03:21:58 2019
InstallationDate: Installed on 2018-12-11 (172 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago)

[Gunnar Hjalmarsson (gunnarhj)]

Thanks for your report!

Can you please start it from terminal:

gnome-control-center

and check if any useful error message is printed when you click Devices.

[Lars Bahner (bahner)]

bahner@venus:~$ gnome-control-center

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218: no sunset data, using 16,00

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218: no sunrise data, using 8,00

(gnome-control-center:14031): GLib-GObject-CRITICAL **: 00:05:00.230: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Minnesegmentsfeil (kjerne lagret i fil)
bahner@venus:~$

That's a segfault. This happens, when I click Devices, and everytime I start gnome-control-center after that (without getting the time to do anything).

Cheers.

[Gunnar Hjalmarsson (gunnarhj)]

Thanks. I see now that you filed this bug from a Unity session, and I can reproduce the problem on Unity. The problem is that AFAIK gnome-control-center is not designed to work with Unity; unity-control-center is there for reasons.

Why are you using gnome-control-center on Unity?

[Sebastien Bacher (seb128)]

Can you use gdb to get details on the segfault?

[Gunnar Hjalmarsson (gunnarhj)]

On 2019-06-12 08:47, Sebastien Bacher wrote:
> Can you use gdb to get details on the segfault?

Please see attachment.

[Sebastien Bacher (seb128)]

Can you type "bt" in gdb after hitting the segfault?

[Gunnar Hjalmarsson (gunnarhj)]

On 2019-06-12 13:34, Sebastien Bacher wrote:
> Can you type "bt" in gdb after hitting the segfault?

New attachment.

[Gunnar Hjalmarsson (gunnarhj)]

The Ask Ubuntu question <https://askubuntu.com/q/1183917> indicates that this issue may show up also on standard Ubuntu with GNOME.

[Sebastien Bacher (seb128)]

Starting the setting on that section with a nb_NO.UTF−8 locale doesn't trigger a segfault.

Could you get another backtrace after installing libglib2.0-0-dbg and using 'bt full'?
Do you get the issue with a new user on the same machine??
What are your screens configuration?

[Sebastien Bacher (seb128)]

Sorry, reading again in was on Disco and with Unity, that's https://gitlab.gnome.org/GNOME/gnome-control-center/issues/604 then. Those settings can't be used outside of GNOME since they talk to gnome-shell, also the new version returns a proper error instead of segfaulting. Closing as fixed

[René Vangsgaard (rene-vangsgaard)]

I experience this on Ubuntu 19.10 using Gnome on Wayland.

❯ gnome-control-center --verbose
/sys/firmware/dmi/tables/smbios_entry_point: Permission denied
/dev/mem: Permission denied
fish: “gnome-control-center --verbose” terminated by signal SIGSEGV (Address boundary error)

[René Vangsgaard (rene-vangsgaard)]

Using the Pop!_OS PPA fixes this. https://launchpad.net/~system76/+archive/ubuntu/pop

[Sebastien Bacher (seb128)]

Don't use the PopOS ppa, it could result in your Ubuntu system to not upgrade properly in the futur