gnome-display-properties crashed with SIGSEGV in strcmp()

Bug #269595 reported by Traumflug on 2008-09-12
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

Happily clicking around after #258584 was fixed, I found the display properties panel vanishes in the short time between seeing the old resolution and seeing the new resolution. First, I thought this is intentional (and not-so-well designed), but then, Apport came up. Obviously, there's still an annoyance to fix :-)

$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10


P.S.: Hardware didn't change since reporting #258584 ( ) and software changed only by updates from Ubuntu, so the ls_pci logs there still apply.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-display-properties
Package: gnome-control-center 1:2.23.90-0ubuntu9
ProcAttrCurrent: unconfined
ProcCmdline: gnome-display-properties
Signal: 11
SourcePackage: gnome-control-center
 #0 0x00007f7a35ebb1a2 in strcmp () from /lib/
 #1 0x0000000000408016 in _start ()
 strcmp () from /lib/
 _start ()
 Thread 1 (process 13807):
 #0 0x00007f7a35ebb1a2 in strcmp () from /lib/
 #1 0x0000000000408016 in _start ()
Title: gnome-display-properties crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev vboxusers video

Traumflug (mah-jump-ing) wrote :

StacktraceTop:strcmp () from /lib/
on_screen_changed (scr=<value optimized out>, data=<value optimized out>)
screen_update (screen=0xdd3c10, force_callback=<value optimized out>) at gnome-rr.c:381
screen_on_event (xevent=<value optimized out>, event=<value optimized out>, data=0x1)
gdk_event_translate (display=0xbf9110, event=0x10b9400, xevent=0x7fff403ca8a0,

Changed in gnome-control-center:
importance: Undecided → Medium
James Westby (james-w) wrote :


Thanks for taking the time to report this bug. I have identified
the problem, and forwarded the bug upstream. I have also
a proposed patch to fix the issue.



Changed in gnome-control-center:
status: New → Triaged
assignee: nobody → desktop-bugs
James Westby (james-w) wrote :


There is a bzr branch attached to the bug report that could be
merged in to the next upload.


Attached is the patch that could be used instead, if that happens
the changelog will need some work.



Changed in gnome-control-center:
status: Unknown → New
Michael Vogt (mvo) wrote :

Thanks for your bugreport and thanks for the bzr branch.

I commited the branch into the main bzr tree and it will be part of the next upload.

Changed in gnome-control-center:
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-control-center - 1:2.23.90-0ubuntu11

gnome-control-center (1:2.23.90-0ubuntu11) intrepid; urgency=low

  [ James Westby ]
  * debian/patches/50_ubuntu_systemwide_prefs.patch:
    - fix typo (LP: #269328)
  * debian/patches/107_rr_NULL_output_name.patch
    - handle output->name being NULL in on_screen_changed
      in the xrandr capplet. (LP: #269595)

  [ Michael Vogt ]
  * debian/
    - add missing gconf2-common (>= 2.23.2-0ubuntu3) to ensure
      that the gconf system default stuff is working

 -- Michael Vogt <email address hidden> Sat, 20 Sep 2008 00:09:11 +0200

Changed in gnome-control-center:
status: Fix Committed → Fix Released
Traumflug (mah-jump-ing) wrote :

Thanks a lot for the fix, James & Michael.

When I just tried to confirm the fix, I finally ended up with :-/

Changed in gnome-control-center:
status: New → Invalid
Changed in gnome-control-center:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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