Bug 159129

Summary: workspace is not visible
Product: [Unmaintained] plasma4 Reporter: Stefan Lorenz <stefan.lorenz>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED INTENTIONAL    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Stefan Lorenz 2008-03-11 11:28:24 UTC
Version:           0.0.1 (using 4.0.2 (KDE 4.0.2), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-11-generic

while loggin in into KDE4 plasma crashes with sigsev
the workspace remains black
no bars, background etc visible but kde4 is running
able to start apps with alt+F2
Comment 1 Stefan Lorenz 2008-03-11 11:30:19 UTC
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb582b740 (LWP 26519)]
[KCrash handler]
#6  0x08082383 in ?? ()
#7  0xbff4007b in ?? ()
#8  0x08065230 in ?? ()
#9  0x08120748 in ?? ()
#10 0xbff4a388 in ?? ()
#11 0x00000001 in ?? ()
#12 0xb7cf9c7c in ?? () from /usr/lib/kde4/lib/libplasma.so.1
#13 0xbff4a398 in ?? ()
#14 0xb7d417e0 in ?? () from /usr/lib/kde4/lib/libplasma.so.1
#15 0x0811fd48 in ?? ()
#16 0x00000001 in ?? ()
#17 0xb7cf3734 in ?? () from /usr/lib/kde4/lib/libplasma.so.1
#18 0xb7e134e8 in ?? () from /usr/lib/kde4/lib/libplasma.so.1
#19 0x0000000c in ?? ()
#20 0x0000000c in ?? ()
#21 0x00000000 in ?? ()
#0  0xb7f97410 in __kernel_vsyscall ()
Comment 2 Markus Grob 2008-04-08 00:41:41 UTC
Seems to be, that Kubuntu users have problems with KDE 4.0.2. Could you try it again with KDE 4.0.3? It works fine for me, but I have OpenSuse 10.3 installed. For testing move ./kde4 to ./kde4_old and ./kde also.
Comment 3 Hans Chen 2008-04-08 00:44:23 UTC
Or try to move/delete ~/.kde/share/config/plasmarc.
Comment 4 Jason Stubbs 2008-06-01 07:33:18 UTC
With 4.1 just around the corner, it's time to close off 4.0 bugs. If you get similar crashes with 4.1 please open a new bug with a full backtrace.