gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate() (no RANDR)

Bug #864137 reported by Huben Stoev
156
This bug affects 28 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Fault after fault.Impossible to work normally

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Oct 1 18:42:23 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: gnome-control-center background
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4da94ec2c7 <gtk_widget_size_allocate+23>: mov 0x18(%rdi),%rbp
 PC (0x7f4da94ec2c7) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_widget_size_allocate () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgnome-control-center.so.1
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1546): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1546): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
usr_lib_gnome-control-center:
 deja-dup 20.0-0ubuntu3
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.3.0-0ubuntu1

Revision history for this message
Huben Stoev (hubenss) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_widget_size_allocate (widget=0x0, allocation=0x7fff32f6f7f0) at /build/buildd/gtk+3.0-3.2.0/./gtk/gtkwidget.c:4766
 cc_panel_size_allocate (widget=0x7f4daa8bd000, allocation=0x7fff32f6fca0) at cc-panel.c:180
 g_closure_invoke (closure=0x7f4daa519500, return_value=0x0, n_param_values=2, param_values=0x7f4daaa9ab30, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x7f4daa8bd000, emission_return=0x0, instance_and_params=0x7f4daaa9ab30) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3202
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3003

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Expired
Changed in gnome-control-center (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Gendeau (gendeau) wrote :

I am running via nx (nomachine v3.?), I have reported other (related?) issue 971482 / 970723

Revision history for this message
Kiall Mac Innes (kiall) wrote :

This seems to be affecting 12.04 beta2 now as well...

Revision history for this message
Nathaniel W. Turner (nturner) wrote :

To reproduce: System Settings... > Displays. I get dialog indicating "Could not get screen information" "RANDR extension is not present". Choose Close button. Crash.

My setup is an Nvidia Quadro NVS 450 with 3 monitors (and thus Xinerama), so the RANDR extension is not expected to be present. I don't, however, expect the configuration app to crash.

tags: added: precise
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, that's an useful information ... is that already the case for others who get that issue? What video driver,screen setup do you use?

summary: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate()
+ (no RANDR)
Revision history for this message
Paul Meredith (paul-venture-its) wrote :

I am also running Nvidia Quadro NVS450 with Xinerama and Mosaic enabled. Then RANDR extention is not running as expected. I am using the latest Nvidia Drivers (295.40) and Ubuntu 12.04 Beta2. 1 am using 4 Screens (1680x1050) in a 2 x 2 configuration.

Revision history for this message
Mario Jäckel (mario-jaeckel) wrote :

I am running Ubuntu 12.04 LTS -Release amd64(20120425) with a Nvidia Quadro NVS 295 graphic card. Xinerama is enabled with two identical monitors. RANDR extension is missing on system.
I am using the 295.49 printed out from nvidia x server settings. X says I'm using 295.33 driver as printed out in /etc/X11/xorg.conf

Revision history for this message
Goekce (leuko) wrote :

I can also confirm it with an Nvidia Quadro NVS 450 with 304.22 beta drivers regardless of using Xinerama or not. Also using Ubuntu 12.04.

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.