gnome-display-properties assert failure: display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code should not be reached

Bug #431953 reported by toobuntu
316
This bug affects 52 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Fix Released
Critical
gnome-control-center (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs
Karmic
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

Start gnome-display-properties on i915 chipset with a VGA external monitor connected to the machine, click the mirror check box and it will crash.

ProblemType: Crash
Architecture: i386
AssertionMessage: display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code should not be reached
CheckboxSubmission: 828a5c329e78d7d842afb06bc29466b6
CheckboxSystem: b4511570833504a308af03903c18ec08
Date: Thu Sep 17 11:46:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-display-properties
Package: gnome-control-center 1:2.27.91-0ubuntu3
ProcCmdline: gnome-display-properties
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 g_assertion_message () from /usr/lib/libglib-2.0.so.0
 _start ()
Title: gnome-display-properties assert failure: display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code should not be reached
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
toobuntu (toobuntu) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
IA__g_assertion_message (
rebuild_gui (app=0x8adde20) at xrandr-capplet.c:643

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Felix Geyer (debfx) wrote :

gnome-display-properties also crashes when resizing the VirtualBox window (changing display resolution) while gnome-display-properties is running on the guest machine.

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

With nouveau driver on startup
$ gnome-display-properties

(gnome-display-properties:2317): Gtk-WARNING **: Ignoring the separator setting

(gnome-display-properties:2317): Gtk-WARNING **: No object called:
**
display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code should not be reached
Aborted (core dumped)

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :
Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Not sure if mine really is the same problem but i'll describe it and a sort of workaround
My default resolution is 1280x1024 but when desktop starts its in 1280x960 and and xrandr shows seemingly wrong resolution list without 1280x1024 on it. if it ret to start gnome-display-properties now i get the crash described above.
if i now manually set
$xrandr --output VGA2 --mode 1280x1024
i get the correct resolution, and runing xrand shows the 'correct' set of resolutions. now if i start gnome-display-properties it runs fine. the problem will be reset on next log in.

Revision history for this message
Niall Creech (sevenmachines-deactivatedaccount) wrote :

Correction to above, i need to set xrand to one of the original available resolutions before xrandr will show the 'correct' set of resolutions and i can set it to 1280x1024. note, i do not get this with the nvidia binaryt driver, only nouveau. the set of commands in terminal on new login is attached

$ apt-show-versions gnome-control-center libdrm2 libdrm-nouveau1 xserver-xorg-video-nouveau nouveau-kernel-source

gnome-control-center/karmic uptodate 1:2.28.0-0ubuntu2
libdrm-nouveau1/karmic uptodate 2.4.13-1ubuntu1
libdrm2/karmic uptodate 2.4.13-1ubuntu1
nouveau-kernel-source/karmic uptodate 0.0.15+git20090823-0ubuntu1
xserver-xorg-video-nouveau/karmic uptodate 1:0.0.10~git+20090823+569a17a-0ubuntu1

Changed in gnome-control-center (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Medium → High
milestone: none → ubuntu-9.10
Revision history for this message
Chris Coulson (chrisccoulson) wrote :
Changed in gnome-control-center (Ubuntu Karmic):
status: Confirmed → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

there is a patch upstream now

Changed in gnome-control-center (Ubuntu Karmic):
status: Triaged → Fix Committed
Revision history for this message
Chris (chris-yourdreamnet) wrote :

This bug still affects me even though I am running the latest version of karmic.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-control-center - 1:2.28.0-0ubuntu4

---------------
gnome-control-center (1:2.28.0-0ubuntu4) karmic; urgency=low

  * debian/patches/81_upstream_change_fix_xrand_capplet_crash.patch:
    - bugzilla change to fix a crasher in the xrandr capplet
      (lp: #431953)
  * debian/patches/82_upstream_change_fix_aboutme_crash.patch:
    - bugzilla change to fix the aboutme capplet crashing on closing
      (lp: #414538)

 -- Sebastien Bacher <email address hidden> Tue, 06 Oct 2009 19:20:49 +0200

Changed in gnome-control-center (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Yves (yavady) wrote :

The fix worked for me. The app no longer crashes. I reported a duplicate bug on this earlier.

Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → Fix Released
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.