Bug 292677

Summary: kde crash at start up, kded KO, after a release update to kubuntu 11.10
Product: [I don't know] kde Reporter: COQUELLE Xavier <xavier>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: lamarque, xavier
Priority: NOR    
Version: 4.7   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: generated by the crash assistant

Description COQUELLE Xavier 2012-01-28 11:16:18 UTC
Created attachment 68265 [details]
generated by the crash assistant

Version:           4.7 (using KDE 4.7.4) 
OS:                Linux

kde crash at start up
kded is stopped, trying to give it the signal CONTINUE seemed to work in survey apps but is considered as not running by bug report assistant 


Reproducible: Always

Steps to Reproduce:
seems to happen every time ... 2 or 3 tries. 
while starting the computer, after log in kdm

Actual Results:  
erratic behavior of  the kde environnement with impact on the personnal datas (see below)

Expected Results:  
- respect the choices of kde configuration parameters : good application menus, new session at start (doesn't do it !)
- respect the true personnal ressources (mail, calendar, contacts, notes)
... what else ?

context.
I have just install kubuntu 11.10 without formating /home I used with kubuntu 10.4
I noticed several problems also :
- the plasma application launcher does not refresh the menu entries automatically and claims it can't find khotkeys, but if i ask it to save, it's ok after.
- akonadi ressources have been automatically created in a strange way. After correction to point my files (calendar, contat, notes, mail), it creates another unexpected ressource
- kmail migration to kmail2 crashed at the first try

I wonder if the new kde do a good update or  migration of the ancien kde parameters and configuration files
Comment 1 Lamarque V. Souza 2012-01-29 12:17:07 UTC
This bug was fixed more than five months ago. Please update Plasma NM to a newer version.

*** This bug has been marked as a duplicate of bug 280494 ***