[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KDE 4.6.2



I have a little more information to add to this mystery.

The story so far: I upgraded my workstation and my laptop to kde 4.6.2 from the experimental snapshot on Friday. Prior to doing so, I did an aptitude full-upgrade on both systems before and after installing.

Now, however, the desktop works fine. On the laptop, whenever trying to start a KDE application (either from KDE or Gnome), X crashes and tosses me back to KDM. There is some manner of backtrace in /var/log/Xorg.0.log and /var/log/kdm.log as well as error messages in .xsession errors. (I will include short segments of each file covering one such crash.

I decided to go ahead and "nuke and pave" the laptop, going through a complete reinstall, installing squeeze, then using only the sid sources. As soon as I installed the nvidia driver, I started seeing the same issues again. The other thing I noticed was that in order to get the nvidia working, I had to install nvidia-glx, which required I downgrade the xserver-xorg package from 1.10.x to 1.9.5. On the laptop, this deinstalled most of the xorg display drivers -- including nouveau and nv. I have been hesitant to risk further breakage by trying to deinstall and reinstall the drivers. However, prior to getting nvidia working, nv was installed and did not display this behavior.

Okay, so now, I am trying to isolate it. I have all compositing turned off (both withing kde and compiz -- and compiz runs fine in Gnome), so I figure that the items that are left that could be the problem are

* nvidia driver
* KDE
* QT
* nvidia
* hardware

In an attempt to check the memory, I clicked menu from the kdm login screen, then Shutdown.The turn off computer or restart buttons showed up, and regardless of which I pressed, I got the same traceback and it started kdm again.

I'm running a memtest, but does anyone have _any_ ideas why my laptop appears posessed?

Thanks,
--b
[   176.828] 3: /usr/bin/X (ProcessWorkQueue+0x30) [0x80980e0]
[   176.828] 4: /usr/bin/X (WaitForSomething+0x56) [0x80a7e26]
[   176.828] 5: /usr/bin/X (0x8048000+0x3ae0e) [0x8082e0e]
[   176.828] 6: /usr/bin/X (0x8048000+0x1e695) [0x8066695]
[   176.828] 7: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xf7416c76]
[   176.829] 8: /usr/bin/X (0x8048000+0x1e271) [0x8066271]
[   176.829] Segmentation fault at address (nil)
[   176.829] 
Fatal server error:
[   176.829] Caught signal 11 (Segmentation fault). Server aborting
[   176.829] 
[   176.829] 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org


Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80edefb]
1: /usr/bin/X (0x8048000+0x58915) [0x80a0915]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xf77c1410]
3: /usr/bin/X (ProcessWorkQueue+0x30) [0x80980e0]
4: /usr/bin/X (WaitForSomething+0x56) [0x80a7e26]
5: /usr/bin/X (0x8048000+0x3ae0e) [0x8082e0e]
6: /usr/bin/X (0x8048000+0x1e695) [0x8066695]
7: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xf74c3c76]
8: /usr/bin/X (0x8048000+0x1e271) [0x8066271]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting


Please consult the The X.Org Foundation support 
             at http://wiki.x.org
for help. 

Attachment: xsession-errors
Description: Binary data


Reply to: