Ubuntu
restricted-manager package

[apport] restricted-manager crashed with ParseException in readConfig()

Bug #102052 reported by Lotacus
2
Affects Status Importance Assigned to Milestone
restricted-manager (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

Binary package hint: restricted-manager

Feisty 7.04 AMD64

ran in terminal
sudo restricted-manager

ProblemType: Crash
Architecture: amd64
Date: Mon Apr 2 17:31:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/restricted-manager
InterpreterPath: /usr/bin/python2.5
Package: restricted-manager 0.17
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/restricted-manager
ProcCwd: /home/lotacus
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_CA.UTF-8
PythonArgs: ['/usr/bin/restricted-manager']
SourcePackage: restricted-manager
Uname: Linux lotacus-desktop 2.6.17-10-generic #2 SMP Tue Dec 5 21:16:35 UTC 2006 x86_64 GNU/Linux

Revision history for this message
Lotacus (mikewatters) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Hmm, can you please attach your /etc/X11/xorg.conf so that I can replicate this crash? I will change r-m to display an error dialog about a broken xorg.conf, but it might actually be a bug in the parser and a valid file. Thank you!

Changed in restricted-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Lotacus (mikewatters) wrote :

Hmm. That could be a problem. I've since then replaced feisty with edgy. If it helps any, I was trying to use beryl with feisty and trying to get the ATI drivers to work correctly. The xorg.conf file didn't look any different than it did with Edgy. I was following many guides with no success until I came across a forum post about a new restricted-manager application that can be used to manage the drivers. When I used apt-get and aftwards ran it, that is when the crash appeared. Since the xorg.conf file is no different than what I always use, and it's something I pay close attention to, I will post the one that I have, if your only looking to have a duplicate of the xorg.conf for reproduction.

I will tell you however, that the display resolutions in the xorg file where all 1024x768, 800x600 @ 24bit

and the entry
 Option "VideoOverlay" "on"
 Option "OpenGLOverlay" "off"
 BusID "PCI:1:0:0"
EndSection

was not present.

I will install feisty again on a separate partition since I only have one computer to test on. I know I know, not something that is recommended, but the computer isn't something I depend on.

Revision history for this message
Martin Pitt (pitti) wrote :

r-m works fine for me with the attached xorg.conf. So I'll produce a really broken one for myself and display an error message.

Changed in restricted-manager:
assignee: nobody → pitti
status: Needs Info → In Progress
Martin Pitt (pitti)
Changed in restricted-manager:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

 restricted-manager (0.18) feisty; urgency=low
 .
   * RestrictedManager/xorg_driver.py: Intercept ParseException and
     AttributeError when parsing xorg.conf, and display an error dilaog instead
     of crashing. (LP: #102052)
   * restricted-manager: Set gettext domain for the glade file to get a
     translated window title. (LP: #99357)
   * RestrictedManager/restricted22.png: Replace with a non-blurry version,
     thanks to Jef! (LP: #102641)
   * RestrictedManager/core.py, save_restricted_list(): If we encounter an
     exception during writing the cache file (e. g. out of space), unlink it,
     so that we ensure to never have broken cache files. (LP: #101883)

Changed in restricted-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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