displayconfig-gtk crashed with AttributeError in _resyncResolution()

Bug #126048 reported by Jaap Haitsma
64
Affects Status Importance Assigned to Milestone
displayconfig-gtk (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: displayconfig-gtk

Startup displayconfig-gtk on a DELL Latitude D410 and it crashes immediately

ProblemType: Crash
Architecture: i386
Date: Sat Jul 14 23:09:54 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/displayconfig-gtk
InterpreterPath: /usr/bin/python2.5
Package: displayconfig-gtk 0.2+20070605ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-gtk
ProcCwd: /home/haitsma/Programming/gnome2/gnome-applets
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/haitsma/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
PythonArgs: ['/usr/bin/displayconfig-gtk']
SourcePackage: displayconfig-gtk
Title: displayconfig-gtk crashed with AttributeError in _resyncResolution()
Uname: Linux guzzi 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
Jaap Haitsma (jaap) wrote :
Changed in displayconfig-gtk:
importance: Undecided → Medium
Revision history for this message
Siegfried Gevatter (rainct) wrote :

Thanks for your bug report! Does this problem still occur with the current version of displayconfig-gtk?

If yes, please run «gksudo displayconfig-gtk > ~/output.displayconfig-gtk.log 2>&1» in a terminal and upload the file «output.displayconfig-gtk.log» that will be created on your home directory here.

Changed in displayconfig-gtk:
assignee: nobody → rainct
status: New → Invalid
Changed in displayconfig-gtk:
status: Invalid → Incomplete
Revision history for this message
hakáishi (naurun-deactivatedaccount) wrote :

Hi, I got the very same problem....
Here the output.displayconfig-gtk.log

Changed in displayconfig-gtk:
assignee: rainct → nobody
status: Incomplete → Confirmed
Revision history for this message
Siegfried Gevatter (rainct) wrote :

Do you have this problem with Gutsy or Hardy? And how many screens do you have?

Revision history for this message
hakáishi (naurun-deactivatedaccount) wrote :

On Hardy, and I have just one screen, a widescreen

Revision history for this message
hakáishi (naurun-deactivatedaccount) wrote :

To me it seems as if the problem consists of a bundle of bugs

Revision history for this message
robertocravero (roberto-cravero) wrote :

same problem on Acer travelmate 3040, one screen, running hardy alpha 5

Revision history for this message
hakáishi (naurun-deactivatedaccount) wrote :

I solved this problem by reinstalling Ubuntu from the new Daily-Live - CD. It works fine now (at least for me). ^^

Revision history for this message
Bryce Harrington (bryce) wrote :

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk

Changed in displayconfig-gtk:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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