MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()

Bug #91545 reported by Alpha_Cluster on 2007-03-12
658
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
High
Kubuntu Bugs

Bug Description

Binary package hint: kde-guidance

I get this after attempting to use dual monitors with the radeon driver. The main monitor was a laptop LCD. After unplugging the monitor I got this error.

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 11 22:12:08 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py
InterpreterPath: /usr/bin/python2.5
Package: kde-guidance 0.7.1~svn20070205-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/bin/python /usr/bin/displayconfig-restore
ProcCwd: /home/nikkun
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: kde-guidance
StacktraceTop:
 ?? () from /usr/lib/libXrandr.so.2
 XRRGetScreenInfo () from /usr/lib/libXrandr.so.2
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalFrameEx ()
Uname: Linux Aoi 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Alpha_Cluster (alphacluster) wrote :

StacktraceTop:XRRGetScreenInfo (dpy=0x8ceb30, window=69) at ../../src/XrrConfig.c:351
?? ()
?? ()
?? ()

Changed in kde-guidance:
assignee: nobody → kubuntu-team
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Changed in kde-guidance:
importance: Medium → High
Simon Edwards (simon-simonzone) wrote :

Looking at all of these crash reports I'm getting the feeling that the problem has to do with guidance not handling things when the xrandr X extension is not available. In the past, calling XRRGetScreenInfo() would just return null if the extensions was not available, maybe this behaviour has been changed. Maybe an explicit check for the presence of of xrandr is required.

Filofel (filofel) wrote :

I reported a similar error, that was marked as a duplicate of this one.
But I didn't mention in my original report that I was running a dual screen configuration.
Mine uses a dual-head Matrox G400 PCI board.

Simon Edwards (simon-simonzone) wrote :

I just committed a fix in KDE's SVN for this. (rev 660160, on trunk/extragear/utils/guidance)

Changed in kde-guidance:
status: Confirmed → Fix Committed
jajaX (jajaplanet) wrote :

Hi !

sorry for my bad english.

I can't open displayconfig too and I have this error message when KDE start :

message d'erreur au démarrage de kde => "l'application power management (guidance-power-manager.py) s'est terminé anormalement et a provoqué un signal 11...."
(error message for kde starting => the application power management (guidance-power-manager.py) was terminated anormaly and had made a sgnal 11...")

details :

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209804592 (LWP 27775)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7cb7454 in ?? () from /usr/lib/libXrandr.so.2
#7 0x00018881 in ?? ()
#8 0x08598780 in ?? ()
#9 0x00000048 in ?? ()
#10 0xb6c10b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()

I can find a package called "libpthread" but not "libthread"

Luka Renko (lure) wrote :

I have prepared test packages (i386 only) with above fix from KDE SVN. You can install and test them:

http://muse.19inch.net/~lure/feisty/kde-guidance_0.8.0-0ubuntu6~lure1_i386.deb
http://muse.19inch.net/~lure/feisty/kde-guidance-powermanager_0.8.0-0ubuntu6~lure1_i386.deb

Please report back if it fixes or not your problem. If we get good feedback, this fix will be considered for https://wiki.ubuntu.com/StableReleaseUpdates

David McNeill (davemc) wrote :

I can only test on a dual head rig with AMD64. Will test that when one is available.

All is good on my 2 machines. Thanks for your efforts.

On 5/3/07, Luka Renko <email address hidden> wrote:
>
> I have prepared test packages (i386 only) with above fix from KDE SVN.
> You can install and test them:
>
>
> http://muse.19inch.net/~lure/feisty/kde-guidance_0.8.0-0ubuntu6~lure1_i386.deb
>
> http://muse.19inch.net/~lure/feisty/kde-guidance-powermanager_0.8.0-0ubuntu6~lure1_i386.deb
>
> Please report back if it fixes or not your problem. If we get good
> feedback, this fix will be considered for
> https://wiki.ubuntu.com/StableReleaseUpdates
>
> --
> MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
> XRRGetScreenInfo()
> https://bugs.launchpad.net/bugs/91545
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Mantan (poul-public) wrote :

I tried the kde-guidance packasge.... it doesn't crash, but it won't load the display module.

Luka Renko (lure) wrote :

Mantan: can you run "kcmshell displayconfig" from command line and attach output? Did it work before? I suspect this is different bug as it runs properly here.

Rich S.: thanks for testing! Can you try Display module in system settings to see if you have same problem as Mantan with new package?

Rich S. (rws265) wrote :

Display module will not open from system settings or from "kcmshell
displayconfig " on the command line.

Rich

On 5/4/07, Luka Renko <email address hidden> wrote:
>
> Mantan: can you run "kcmshell displayconfig" from command line and
> attach output? Did it work before? I suspect this is different bug as it
> runs properly here.
>
> Rich S.: thanks for testing! Can you try Display module in system
> settings to see if you have same problem as Mantan with new package?
>
> --
> MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
> XRRGetScreenInfo()
> https://bugs.launchpad.net/bugs/91545
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Rich S. (rws265) wrote :
Download full text (3.6 KiB)

Attached file is the output from running kcmshell displayconfig at the
command prompt.

On 5/4/07, Luka Renko <email address hidden> wrote:
>
> Mantan: can you run "kcmshell displayconfig" from command line and
> attach output? Did it work before? I suspect this is different bug as it
> runs properly here.
>
> Rich S.: thanks for testing! Can you try Display module in system
> settings to see if you have same problem as Mantan with new package?
>
> --
> MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
> XRRGetScreenInfo()
> https://bugs.launchpad.net/bugs/91545
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

rich@asus:~$ kcmshell displayconfig
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

Pythonize constructor -- pid = 6580
Python interpreter initialized!

Pythonize constructor -- pid = 6580
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 392, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1103, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1553, in _finalizeInit
    if self.x_live_screen is not None and self.x_live_screen.resolutionSupportAvailable():
  File "/var/lib/python-support/python2.5/xf86misc.py", line 54, in resolutionSupportAvailable
    return self.screenconfig is not None
AttributeError: 'XF86Screen' object has no attribute 'screenconfig'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 44, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 392, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python...

Read more...

Sanchola (sanchola) wrote :

I applied the patches and no longer have the power manager crash. However, I can no longer change the display settings in kcmshell Here is the output:

Pythonize constructor -- pid = 9796
Python interpreter initialized!

Pythonize constructor -- pid = 9796
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 392, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1103, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1553, in _finalizeInit
    if self.x_live_screen is not None and self.x_live_screen.resolutionSupportAvailable():
  File "/var/lib/python-support/python2.5/xf86misc.py", line 54, in resolutionSupportAvailable
    return self.screenconfig is not None
AttributeError: 'XF86Screen' object has no attribute 'screenconfig'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 44, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "<string>", line 8, in kcontrol_bridge_create_displayconfig
  File "/var/lib/python-support/python2.5/displayconfig.py", line 1698, in create_displayconfig
    return DisplayApp(parent, name)
  File "/var/lib/python-support/python2.5/displayconfig.py", line 441, in __init__
    self.xsetup = XSetup(self.xconfigpath)
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 387, in __init__
    self._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 392, in _finalizeInit
    gfxcard._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1103, in _finalizeInit
    screen._finalizeInit()
  File "/var/lib/python-support/python2.5/displayconfigabstraction.py", line 1553, in _finalizeInit
    if self.x_live_screen is not None and self.x_live_screen.resolutionSupportAvailable():
  File "/var/lib/python-support/python2.5/xf86misc.py", line 54, in resolutionSupportAvailable
    return self.screenconfig is not None
AttributeError: 'XF86Screen' object has no attribute 'screenconfig'
error: *** runFunction failure
;

I just committed a fix for that AttributeError about "screenconfig". (KDE SVN revision 661336)

Federico "Lox" (federico.lox) wrote :

Can we have packages for 64bit systems please?

I also got a segfault in ixf86misc.XRRGetScreenInfo in a xinerama setup without the randr extension.

After installing the http://muse.19inch.net/~lure/feisty/kde-guidance_0.8.0-0ubuntu6~lure1_i386.deb and http://muse.19inch.net/~lure/feisty/kde-guidance-powermanager_0.8.0-0ubuntu6~lure1_i386.deb packages, I got the same AttributeError as for example Rich S..

I didn't know how to access the SVN, but after trivially fixing the problem (setting self.screenconfig to None in the constructor), displayconfig-restore does not crash anymore. I can also open the "Monitor & Display - System Settings" now. It is not useful thought and does not provide the correct information. This is probably hardly surprising and much better than before...

Thanks!

Patrick Salami (pat-entitycom) wrote :

I have the same problem as in the original bug report, and I also can't launch kcmshell displayconfig because it segfaults when I try to launch it. The stack trace is attached.
Are the patched packages available for amd64 yet or are they available in source form?
Thanks!

Laur Mõtus (vprints) wrote :

Why is it marked fix committed when the duplicates are coming in all the time ? This ain't fixed!

Laur Mõtus (vprints) wrote :

I appologise for my earlier comment.

TuxFan (make) wrote :

This happens to me too. Using the latest and greatest Gutsy at the moment (don't know if this happened in Feisty for me since it's X was too unstable for some weird reason so I quickly changed to Gutsy).

I'm using xinerama too with my Radeon 7500. On konsole the "kcmshell displayconfig" crashes with "KCrash: Application 'kcmshell' crashing..." The screen settings (systemsettings) crashes with signal 11 SIGSEGV.

What also happens is that if I logout, I don't get the KDM's login screen. In stead I see the last booting messages. Logging in a virtual console and doing '/etc/init.d/kdm reload' makes the login screen to show up again.

Petr Škoda (skodak) (skodak) wrote :

hello,
the packages above fixed the problem for me in Feisty. (the problem appeared originally when I started using 2 screen configuration - each different size/nvidia).
the problem is still present in Gutsy though. I managed to force downgrade to these packages above and it sort of works again.

skodak

Thanks for all you help.

xD.

2007/7/20, Petr Škoda (skodak) <email address hidden>:
>
> hello,
> the packages above fixed the problem for me in Feisty. (the problem
> appeared originally when I started using 2 screen configuration - each
> different size/nvidia).
> the problem is still present in Gutsy though. I managed to force downgrade
> to these packages above and it sort of works again.
>
> skodak
>
> --
> MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
> XRRGetScreenInfo()
> https://bugs.launchpad.net/bugs/91545
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--

-----Angel Berlanas Vicente----
--<email address hidden>--

Laur Mõtus (vprints) wrote :

So, when the fix will be released ?

Luka Renko (lure) wrote :

I have just checked the current package and both fixes are included in current version: 0.8.0svn20070928-0ubuntu5

Marking as Fix released. Please open new bug if you still experience similar problem with up-to-date gutsy.

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

Other bug subscribers