Bug 159015

Summary: plasma crashes at start, so there is no desktop, no menu, but I can still launch other apps via <Alt><F2>
Product: [Plasma] plasma4 Reporter: jean <jean.lienard>
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:

Description jean 2008-03-09 15:05:05 UTC
Version:           0.0.1 (using 4.0.2 (KDE 4.0.2), Kubuntu packages)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22-14-generic

I don't really remember what caused this bug - I think I was configuring some things concerning the graphical aspect of the desktop...
Anyway, after logging in with gdm, there is only this little window from the KDE crash handler saying that plasma crashed with signal 11 - no desktop, no workspace... But I can still launch any other application with Alt+F2.

There is also a very important point : this bug continue even AFTER removing every single package (with configuration) of KDE 4, and re-installing kde4-core... But damned! KDE worked just totally fine before this bug and with exactly the same version of KDE 4 !... 


I tried to launch xterm, kill plasma, and then tried to relaunch it from the command-line. I don't know if it is helpful, but here I go for what it said in the terminal before showing the same window from the KDE crash handler :

jean@the-butcher:~$ pkill plasma
jean@the-butcher:~$ plasma 
<unknown program name>(7190)/ checkComposite: Plasma has an argb visual 0x622950
 27262977
<unknown program name>(7190)/ checkComposite: Plasma is COMPOSITE-less on 0x61c5
60
X Error: BadMatch (invalid parameter attributes) 8
  Extension:    156 (RENDER)
  Minor opcode: 4 (RenderCreatePicture)
  Resource id:  0x13a
plasma(7191) PlasmaApp::PlasmaApp: Setting the pixmap cache size to 20624 kiloby
tes
plasma(7191) Plasma::Corona::addContainment: loading of containment "" failed.
findServiceByDesktopPath:  not found
Plasma crashed, attempting to automatically recover
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma path = <unknown> pid = 7191
sock_file=/home/jean/.kde4/socket-the-butcher/kdeinit4__0
plasma(7190): Communication problem with  "plasma" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not re
ceive a reply (timeout by message bus)" " 

jean@the-butcher:~$ <unknown program name>(7193)/ checkComposite: Plasma has an 
argb visual 0x622950 27262977
<unknown program name>(7193)/ checkComposite: Plasma is COMPOSITE-less on 0x61c5
60
X Error: BadMatch (invalid parameter attributes) 8
  Extension:    156 (RENDER)
  Minor opcode: 4 (RenderCreatePicture)
  Resource id:  0x13a
plasma(7196) PlasmaApp::PlasmaApp: Setting the pixmap cache size to 20624 kiloby
tes
plasma(7196) Plasma::Corona::addContainment: loading of containment "" failed.
findServiceByDesktopPath:  not found
plasma(7193): Communication problem with  "plasma" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not re
ceive a reply (timeout by message bus)" "
Comment 1 Alex Merry 2008-03-09 17:06:08 UTC
*** Bug 159022 has been marked as a duplicate of this bug. ***
Comment 2 Will Stephenson 2008-03-09 17:23:56 UTC
*** Bug 159025 has been marked as a duplicate of this bug. ***
Comment 3 Sebastian Sauer 2008-03-10 01:43:09 UTC
This should be fixed with r783242 committed on 2008-03-07 in the 4.0-branch what means it should be part of KDE 4.0.3
Comment 4 Sebastian Sauer 2008-03-10 01:46:17 UTC
*uarg* sorry, again the correct reply at the wrong report :-/

So, this is not fixed yet! To work around this, you can btw just remove the plasma-appletrc file.
Comment 5 Markus Grob 2008-04-08 19:00:02 UTC
Like descibed in another bug, try this first:
remove your ~/.kde/share/config/plasma-appletsrc and try again.
WFM in KDE 4.0.3
Comment 6 jean 2008-04-09 01:57:07 UTC
thanks Sebastian & Markus,

removing the plasma-appletsrc did the trick :)
Comment 7 Jason Stubbs 2008-06-01 07:25:27 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.