[network]: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()

[David Ramalho]

Happens on two different computers -I press the network icon, select Network Settings and the crash report comes up.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 30 10:37:39 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: gnome-control-center network
SegvAnalysis:
 Segfault happened at: 0x7fdcac1a9c0e <gtk_builder_get_object+30>: cmp %rax,(%rdx)
 PC (0x7fdcac1a9c0e) ok
 source "%rax" ok
 destination "(%rdx)" (0x6464612d7473696c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_builder_get_object () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
UpgradeStatus: Upgraded to oneiric on 2011-09-19 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.3.0-0ubuntu1

[Apport retracing service (apport)]

StacktraceTop:
 gtk_builder_get_object (builder=<optimized out>, name=0x7fdc8f49d9f3 "treeview_devices") at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkbuilder.c:1106
 refresh_ui_idle (data=0x7fdcae014000) at cc-network-panel.c:2130
 g_main_dispatch (context=0x7fdcadd94da0) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:2441
 g_main_context_dispatch (context=0x7fdcadd94da0) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3011
 g_main_context_iterate (context=0x7fdcadd94da0, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3089

[Sebastien Bacher (seb128)]

Thank you for your bug report. Is your system uptodate? Could you send your /usr/share/gnome-control-center/ui/network.ui to the bug? Did the issue start recently?

[David Ramalho (dramalho-gmail)]

Hi Sebastien :)

1) Yes, I update it some four times a day :)

2) sure, attached :)

2) Yes, it started (I think) this week, I might not have noticed immediately because I had a couple of days where no VPN was needed (so I didn't use the nm settings)

[Sebastien Bacher (seb128)]

is that specific to vpn configs? could you take a screen of the dialog with the button you click to get the bug?

[David Ramalho (dramalho-gmail)]

No, not vpn specific, it's the entire "Network Settings" applet / screen , I only noticed because I needed to check the VPN settings, that's all :) - none the less, here's a screenshot

[Sebastien Bacher (seb128)]

oh, you are using gnome-shell! Does it work if you open gnome-control-center and click on the network icon there?

[David Ramalho (dramalho-gmail)]

I can't reproduce it now because I'm actively using my VPN and .. here's the kicker :) .. in order to do that (I'll can't find the bug reference now - explaining this) I'm running nm-applet manually. This might explain why it's working now (it is btw), and not before, a simple reboot or simplly killing the nm-applet process will probably recreate the issue. I'll search for the bug that references running nm-applet as a solution, but I remember reading nm-applet isn't starting automatically due to another bug ...

I'm guessing this might explain, sincere apologies for not mentioning it sooner, it was something I did later in the process - I'll search for the bug

[Sebastien Bacher (seb128)]

nm-applet is not running under gnome-shell because the shell indicator is supposed to replace it, maybe they conflict in some way?

[Sebastien Bacher (seb128)]

settings to low, your issue seems a corner case due to un-usual tweaking

[David Ramalho (dramalho-gmail)]

All the computers at the office who are running 11.10 (a whooping 4 computers :) ) had the same issue - both with the crash and with needing nm-applet to start vpn connections (and having a working shell indicator.

Having the nm-applet workaround makes it less critical, but seems odd never the less :D

Anyway, thank you for your help Sebastien, cheers

[Sebastien Bacher (seb128)]

ok, thanks for the explanation, seems like you should open a bug for gnome-shell to do what you need without having to run nm-applet by hand or switch to Unity ;-)

[David Ramalho (dramalho-gmail)]

I'm undecided between gnome-shell and the network-manager itself , it's not just the dialog not showing, it's the whole vpn not connecting :)

Anyway, thanks mate ;)

[Launchpad Janitor (janitor)]

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

[Bayan Rafeh (bayan-rafeh92)]

I got the issue too when I activated the "use as hotspot" option in the network settings. I activated and then it crashed after I disabled wireless from gnome.

[Sebastien Bacher (seb128)]

Bayan, do you use gnome-shell as well?

[Sebastien Bacher (seb128)]

Similar to https://bugzilla.redhat.com/show_bug.cgi?id=768605

[Sebastien Bacher (seb128)]

the code has been rewritten since which means that bug isn't valid anymore