Bug 169147

Summary:	KWin crashes on login, signal 11
Product:	[Plasma] kwin	Reporter:	Greg Hypta <mortici>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	cooltd825, sven.burmeister
Priority:	NOR
Version:	3.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Greg Hypta 2008-08-15 01:45:34 UTC

Version:           3.0 (using KDE 4.1.0)
Installed from:    Ubuntu Packages
OS:                Linux

Running KDE 4.1.0 for no apperent reason after reboot my KWin now crashes on login with a signal 11, my whole screen at login gets completely messed up and then KWin restarts and everything is ok

Here is the crash handler output:

...
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5753960 (LWP 6755)]
[KCrash handler]
#6  0xb5d28b78 in ?? () from /usr/lib/libGLcore.so.1
#0  0xb7ef9410 in __kernel_vsyscall ()

and here is .xsession-errors |grep kwin:

kwin(6755) KDecorationPlugins::loadPlugin: kwin : path  "/usr/lib/kde4/lib/kde4/kwin3_ozone.so"  for  "kwin3_ozone"
kwin(6755): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed"
kwin(6755): Couldn't start knotify from knotify4.desktop:  "KDEInit could not launch '/usr/lib/kde4/bin/knotify4'."
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x120003f)
KCrash: Application Name = kwin path = <unknown> pid = 6755
kwin(6794) KDecorationPlugins::loadPlugin: kwin : path  "/usr/lib/kde4/lib/kde4/kwin3_ozone.so"  for  "kwin3_ozone"
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x120004d)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x120017d)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1200555)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x12007d2)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1200b20)
kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1200dfc)

Any assistance would be great, thanks!

Desktop Effects are enabled. No plasmids or widgets are enabled. Startup items include: kmix,ktorrent,amarok(all kde4 versions) and knetworkmanager (kde3 edition)

Nvidia 7950GT (Latest Driver), 2GB Ram, 320GB RAID0, DVD-RW, Core 2 Duo E6400 @ 3.2GHz, ASUS P5B Deluxe on Ubuntu Hardy 8.04

Comment 1 Lubos Lunak 2008-08-15 16:16:35 UTC

The backtrace is unfortunately useless, please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports .

Comment 2 S. Burmeister 2008-08-17 12:30:03 UTC

I cannot get a decent backtrace either, although the build is debug-enabled. Yet it happens with the latest kde4:factory packages for 10.3 too.

What I get is:
 
[New Thread 0xb57ee6f0 (LWP 8356)]
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
kwin(8356) KWin::Extensions::init: Extensions: shape: 0x "11"  composite: 0x "4"  render: 0x "a"  fixes: 0x "40"
kwin(8356) KWin::CompositingPrefs::detect: glx version is  1 . 3

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb57ee6f0 (LWP 8356)]
0xb6d4a92d in ?? () from /usr/X11R6/lib/libGL.so.1
(gdb) bt
#0  0xb6d4a92d in ?? () from /usr/X11R6/lib/libGL.so.1
#1  0xb6d59f69 in ?? () from /usr/X11R6/lib/libGL.so.1
#2  0x00990001 in ?? ()
#3  0x00990001 in ?? ()
#4  0x5a4f49d2 in ?? ()
#5  0x081ff5e4 in ?? ()
#6  0xbfb88090 in ?? ()
#7  0x0806a108 in ?? ()
#8  0x00000000 in ?? ()

Comment 3 S. Burmeister 2008-08-17 13:11:14 UTC

I got it working again. It's the nvidia binary driver. While 173.14.12 breaks it, 177.13 (beta) works. Before I installed the 177 some days ago I ran the version before 173.14.12 without problems, I think it was 173.14.09.

So either it is a nvidia bug, or there were changes on both sides that lead to the crash.

Reverting kwin to revision 836665 does not solve the issue.

Comment 4 S. Burmeister 2008-08-17 13:27:53 UTC

It seems I had some left-overs from the 177 manual install when updating the kernel driver packages. After running the uninstall for the binary driver again and refreshing the packages from nvidia, it all works now.

Have you installed the drivers manually before?

Comment 5 cooltd825 2008-09-04 23:51:52 UTC

confirmed

beta drivers eliminate the crash on startup, although system stability is compromised.

Comment 6 Lubos Lunak 2008-09-05 07:17:52 UTC

Driver problem then.