Bug 144514 - guidance-power-manager.py crashes at startup after upgrade to kubuntu feisty
Summary: guidance-power-manager.py crashes at startup after upgrade to kubuntu feisty
Status: RESOLVED FIXED
Alias: None
Product: guidance
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
: 150188 150538 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-04-22 11:51 UTC by Florian M.
Modified: 2010-01-30 02:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian M. 2007-04-22 11:51:55 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

traceback:

(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 -1209993008 (LWP 5547)]
(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  0xb690b454 in ?? () from /usr/lib/libXrandr.so.2
#7  0x00019981 in ?? ()
#8  0x085a0680 in ?? ()
#9  0x00000048 in ?? ()
#10 0xb6be2b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()
Comment 1 Sebastian Kügler 2007-04-22 19:06:57 UTC
Can you start powermanager from a shell and post the output here?
Comment 2 Florian M. 2007-04-22 22:55:26 UTC
flo@flo-acer-kub:~$ guidance-power-manager
flo@flo-acer-kub:~$ X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
KCrash: Application 'guidance-power-manager.py' crashing...

And KDE-Crashmanager comes up with the traceback above.
Comment 3 Maiko Herajin 2007-04-24 18:29:49 UTC
I get the exact same thing happening, although mine was a new install, not an upgrade. It happens on every single boot.

Out of curiosity, are you running xinerama? I seemed to have narrowed it down to that. Switching the video card to twinview alleviates the problem, and also fixes some (I assume) related problems such as the monitor applet in kcontrol crashing.
Comment 4 Florian M. 2007-04-25 00:42:56 UTC
It's true. I use Xinerama, and when I turn it off guidance works fine. that's on an ATI Radeon Mobility 9700 adapter with the fglrx driver.
Comment 5 Marc Salvatori 2007-04-27 05:10:39 UTC
My freshly installed Fiesty experience is similar.  It only crashes when logging in remotely using XDMCP:  
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47407511766768 (LWP 10549)]
(no debugging symbols found)
   <snip repeats>
(no debugging symbols found)
[KCrash handler]
#5  0x00002b1df09c6a45 in ?? () from /usr/lib/libXrandr.so.2
#6  0x00002b1df09c6b68 in XRRGetScreenInfo () from /usr/lib/libXrandr.so.2
#7  0x00002b1df5bdab4f in ?? ()
   from /var/lib/python-support/python2.5/ixf86misc.so
#8  0x000000000048875d in PyEval_EvalFrameEx ()
#9  0x0000000000488ab1 in PyEval_EvalFrameEx ()
#10 0x000000000048973a in PyEval_EvalCodeEx ()
#11 0x00000000004d3cf8 in ?? ()
#12 0x0000000000417be3 in PyObject_Call ()
. . . 
Comment 6 Gregoire Vincke 2007-05-06 22:07:26 UTC
I have the same bug, with exactly same traceback. Arround 1 to 5 minutes after loading desktop, i have a window wich say that guidance-power-manager.py has terminated abnormaly and has generated a " signal 11 (SIGSEGV)".
I upgraded from kubuntu 6.10 to 7.04 with the automatic tool, but it has stopped at 49% of configuration of all downloaded packages. I finished the upgrage using Terminal with a "dpkg --configure -a" followed by a "apt-get update" and "apt-get upgrade".
I have a AMD processor, on a dual screen computer with Xinerama on a nvidia 256 MB GeForce FX 5600XT video card.
Comment 7 morgajel 2007-07-26 15:22:14 UTC
I'm seeing the same behavior with almost identical backtrace- IBM thinkpad T42 with docking station- one dvi output, one standard. Intel Proc and an ati chipset with Radeon drivers, using xinerama.

jmorgan@twiggo ~ $ guidance-power-manager
jmorgan@twiggo ~ $ KCrash: Application 'guidance-power-manager.py' crashing...
jmorgan@twiggo ~ $

could it be that powermanager is getting confused by the fact that there are two things to put into sleep mode?

Section "Device"
        Identifier      "ATI1"
        Driver          "radeon"
        BusID           "PCI:1:0:0"
        Option          "XAANoOffscreenPixmaps" "true"
        Option          "DRI" "true"
        Option          "RenderAccel" "true"
        Option          "VideoOverlay" "on"
        Option          "AddARGBGXVisuals" "True"
        Option          "DisableGLXRootClipping" "True"
        Option "ColorTiling" "on"
        Option "EnablePageFlip" "true"
        Option "AccelMethod" "XAA"
        Option "XAANoOffscreenPixmaps"
        Option "AGPMode" "4"
        Option "AGPFastWrite" "on"
        Option      "MergedFB" "false"
        screen 0
EndSection

Section "Device"
        Identifier      "ATI2"
        Driver          "radeon"
        BusID           "PCI:1:0:0"
        Option          "XAANoOffscreenPixmaps" "true"
        Option          "DRI" "true"
        Option          "RenderAccel" "true"
        Option          "VideoOverlay" "on"
        Option          "AddARGBGXVisuals" "True"
        Option          "DisableGLXRootClipping" "True"
        Option "ColorTiling" "on"
        Option "EnablePageFlip" "true"
        Option "AccelMethod" "XAA"
        Option "XAANoOffscreenPixmaps"
        Option "AGPMode" "4"
        Option "AGPFastWrite" "on"
        Option      "MergedFB" "false"
        screen 1
EndSection
Comment 8 Sebastian Kügler 2007-07-26 15:55:22 UTC
On Thursday 26 July 2007 15:22:15 morgajel wrote:
> could it be that powermanager is getting confused by the fact that there
> are two things to put into sleep mode?


I don't think so, that's HAL's job. If you can get me a python backtrace, I'll 
see what I can do.
Comment 9 morgajel 2007-08-01 22:06:55 UTC
As the original poster posted, this is all that comes up as far backtraces go- Let me know if there's better information I can relay.


(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 -1210079024 (LWP 12852)]
(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  0xb68ee454 in ?? () from /usr/lib/libXrandr.so.2
#7  0x0000e251 in ?? ()
#8  0x08598db0 in ?? ()
#9  0x00000048 in ?? ()
#10 0xb6bcdb2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()
Comment 10 Stefan Zimmermann 2007-08-03 09:24:49 UTC
*** This bug has been confirmed by popular vote. ***
Comment 11 Philip Schlesinger 2007-09-27 00:28:57 UTC
I myself am having this same problem with a new install of Feisty Kubuntu.  Backtrace: 

(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 -1210398512 (LWP 5596)]
(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  0xb7c26454 in ?? () from /usr/lib/libXrandr.so.2
#7  0x00020cc9 in ?? ()
#8  0x0850c338 in ?? ()
#9  0x00000048 in ?? ()
#10 0xb6b7fb2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()
Comment 12 Toni Rantanen 2007-09-27 13:21:05 UTC
I've noticed that the problem starts occurring when i install the nVidia restricted driver and configure my display system. I just re-installed my system, and it happened again. My configuration (if anybody gets anything out of it):

2,66 Ghz Core 2 Duo
Asus P5N32-Deluxe MB
2Gt Kingston 800 HyperX
2x nVidia GeForce 7600 GTX xxx edition @ Sli
3x lcd-display & 32" lcd-tv configured with Xinerama
Comment 13 Robert Auch 2007-10-05 17:03:51 UTC
I have 2 xorg.conf files - one with Xinerama enabled when I'm at my desk, and one for just the laptop monitor.  I only get this when Xinerama is enabled.  My backtrace (below) is more detailed.

Power software running:
acpid (apm disabled by me)
cpufreqd (for CPUs)
laptop-mode (for disk spindown)
kpowersave (for video)
Dell D620 - NVidia--glx-new drivers

Backtrace when booting (on AC): 
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47520717752048 (LWP 6370)]
(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]
#5  0x00002b384c377a45 in ?? () from /usr/lib/libXrandr.so.2
#6  0x00002b384c377b68 in XRRGetScreenInfo () from /usr/lib/libXrandr.so.2
#7  0x00002b38515a0b4f in ?? ()
   from /var/lib/python-support/python2.5/ixf86misc.so
#8  0x00000000004885fd in PyEval_EvalFrameEx ()
#9  0x0000000000488951 in PyEval_EvalFrameEx ()
#10 0x00000000004895da in PyEval_EvalCodeEx ()
#11 0x00000000004d3ba8 in ?? ()
#12 0x0000000000417be3 in PyObject_Call ()
#13 0x000000000041e37d in ?? ()
#14 0x0000000000417be3 in PyObject_Call ()
#15 0x000000000045a018 in ?? ()
#16 0x000000000045cf12 in ?? ()
#17 0x0000000000417be3 in PyObject_Call ()
#18 0x0000000000484360 in PyEval_EvalFrameEx ()
#19 0x00000000004895da in PyEval_EvalCodeEx ()
#20 0x00000000004d3ba8 in ?? ()
#21 0x0000000000417be3 in PyObject_Call ()
#22 0x000000000041e37d in ?? ()
#23 0x0000000000417be3 in PyObject_Call ()
#24 0x000000000045a018 in ?? ()
#25 0x000000000045cf12 in ?? ()
#26 0x0000000000417be3 in PyObject_Call ()
#27 0x0000000000484360 in PyEval_EvalFrameEx ()
#28 0x00000000004895da in PyEval_EvalCodeEx ()
#29 0x00000000004d3ba8 in ?? ()
#30 0x0000000000417be3 in PyObject_Call ()
#31 0x000000000041e37d in ?? ()
#32 0x0000000000417be3 in PyObject_Call ()
#33 0x0000000000481052 in PyEval_CallObjectWithKeywords ()
#34 0x0000000000421e06 in PyInstance_New ()
#35 0x0000000000417be3 in PyObject_Call ()
#36 0x0000000000484360 in PyEval_EvalFrameEx ()
#37 0x00000000004895da in PyEval_EvalCodeEx ()
#38 0x00000000004d3ba8 in ?? ()
#39 0x0000000000417be3 in PyObject_Call ()
#40 0x000000000041e37d in ?? ()
#41 0x0000000000417be3 in PyObject_Call ()
#42 0x000000000045a018 in ?? ()
#43 0x000000000045cf12 in ?? ()
#44 0x0000000000417be3 in PyObject_Call ()
#45 0x0000000000484360 in PyEval_EvalFrameEx ()
#46 0x00000000004895da in PyEval_EvalCodeEx ()
#47 0x00000000004d3ba8 in ?? ()
#48 0x0000000000417be3 in PyObject_Call ()
#49 0x000000000041e37d in ?? ()
#50 0x0000000000417be3 in PyObject_Call ()
#51 0x000000000045a018 in ?? ()
#52 0x000000000045cf12 in ?? ()
#53 0x0000000000417be3 in PyObject_Call ()
#54 0x0000000000484360 in PyEval_EvalFrameEx ()
#55 0x00000000004895da in PyEval_EvalCodeEx ()
#56 0x0000000000489622 in PyEval_EvalCode ()
#57 0x00000000004aad1e in PyRun_FileExFlags ()
#58 0x00000000004aafb0 in PyRun_SimpleFileExFlags ()
#59 0x00000000004146b5 in Py_Main ()
#60 0x00002b38474d08e4 in __libc_start_main () from /lib/libc.so.6
#61 0x0000000000413bf9 in _start ()

Backtrace on battery when launched manually:
rauch@lt00-bofh:~$ guidance-power-manager
rauch@lt00-bofh:~$ KCrash: Application 'guidance-power-manager.py' crashing...

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47285490505456 (LWP 13151)]
(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]
#5  0x00002b0187948a45 in ?? () from /usr/lib/libXrandr.so.2
#6  0x00002b0187948b68 in XRRGetScreenInfo () from /usr/lib/libXrandr.so.2
#7  0x00002b018cb71b4f in ?? ()
   from /var/lib/python-support/python2.5/ixf86misc.so
#8  0x00000000004885fd in PyEval_EvalFrameEx ()
#9  0x0000000000488951 in PyEval_EvalFrameEx ()
#10 0x00000000004895da in PyEval_EvalCodeEx ()
#11 0x00000000004d3ba8 in ?? ()
#12 0x0000000000417be3 in PyObject_Call ()
#13 0x000000000041e37d in ?? ()
#14 0x0000000000417be3 in PyObject_Call ()
#15 0x000000000045a018 in ?? ()
#16 0x000000000045cf12 in ?? ()
#17 0x0000000000417be3 in PyObject_Call ()
#18 0x0000000000484360 in PyEval_EvalFrameEx ()
#19 0x00000000004895da in PyEval_EvalCodeEx ()
#20 0x00000000004d3ba8 in ?? ()
#21 0x0000000000417be3 in PyObject_Call ()
#22 0x000000000041e37d in ?? ()
#23 0x0000000000417be3 in PyObject_Call ()
#24 0x000000000045a018 in ?? ()
#25 0x000000000045cf12 in ?? ()
#26 0x0000000000417be3 in PyObject_Call ()
#27 0x0000000000484360 in PyEval_EvalFrameEx ()
#28 0x00000000004895da in PyEval_EvalCodeEx ()
#29 0x00000000004d3ba8 in ?? ()
#30 0x0000000000417be3 in PyObject_Call ()
#31 0x000000000041e37d in ?? ()
#32 0x0000000000417be3 in PyObject_Call ()
#33 0x0000000000481052 in PyEval_CallObjectWithKeywords ()
#34 0x0000000000421e06 in PyInstance_New ()
#35 0x0000000000417be3 in PyObject_Call ()
#36 0x0000000000484360 in PyEval_EvalFrameEx ()
#37 0x00000000004895da in PyEval_EvalCodeEx ()
#38 0x00000000004d3ba8 in ?? ()
#39 0x0000000000417be3 in PyObject_Call ()
#40 0x000000000041e37d in ?? ()
#41 0x0000000000417be3 in PyObject_Call ()
#42 0x000000000045a018 in ?? ()
#43 0x000000000045cf12 in ?? ()
#44 0x0000000000417be3 in PyObject_Call ()
#45 0x0000000000484360 in PyEval_EvalFrameEx ()
#46 0x00000000004895da in PyEval_EvalCodeEx ()
#47 0x00000000004d3ba8 in ?? ()
#48 0x0000000000417be3 in PyObject_Call ()
#49 0x000000000041e37d in ?? ()
#50 0x0000000000417be3 in PyObject_Call ()
#51 0x000000000045a018 in ?? ()
#52 0x000000000045cf12 in ?? ()
#53 0x0000000000417be3 in PyObject_Call ()
#54 0x0000000000484360 in PyEval_EvalFrameEx ()
#55 0x00000000004895da in PyEval_EvalCodeEx ()
#56 0x0000000000489622 in PyEval_EvalCode ()
#57 0x00000000004aad1e in PyRun_FileExFlags ()
#58 0x00000000004aafb0 in PyRun_SimpleFileExFlags ()
#59 0x00000000004146b5 in Py_Main ()
#60 0x00002b0182aa18e4 in __libc_start_main () from /lib/libc.so.6
#61 0x0000000000413bf9 in _start ()
Comment 14 Pino Toscano 2007-10-06 14:01:40 UTC
*** Bug 150538 has been marked as a duplicate of this bug. ***
Comment 15 Pino Toscano 2007-10-06 14:01:53 UTC
*** Bug 150188 has been marked as a duplicate of this bug. ***
Comment 16 Paul Davison 2007-10-06 19:22:03 UTC
I get the same error when I log in via a VNC viewer, I have resumable sessions set up.

(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 -1210321216 (LWP 8224)]
(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)
(no debugging symbols found)
[KCrash handler]
#6  0xb68bb454 in ?? () from /usr/lib/libXrandr.so.2
#7  0x00002681 in ?? ()
#8  0x0857e980 in ?? ()
#9  0x00000048 in ?? ()
#10 0xb6b92b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()

Can anyone suggest anything to stop this from happening?
Cheers
Comment 17 Sebastian Kügler 2010-01-30 02:28:32 UTC
Closing this bug since it seems to be a one-time problem (and probably upstream, as the crasher seems to happen in xrandr).