Bug 212050

Summary: Kwrite crashes when trying to launch it in a terminal as root
Product: [Frameworks and Libraries] kdelibs Reporter: David Todd <contact>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED DUPLICATE    
Severity: crash CC: cullmann, robertknight, valerio.marinelli
Priority: NOR    
Version: 0.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description David Todd 2009-10-27 13:16:52 UTC 
Version:           2.3.2 (using 4.3.2 (KDE 4.3.2), Mandriva Linux release 2010.0 (Cooker) for i586)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-desktop-1mnb

When trying to launch Kwrite in Konsole as root it crashes (OK as normal user)!  doesn't matter if it is just the application or trying to open a specific file. e.g.

[root@ASUS900 david]# kwrite
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
KCrash: Application 'kwrite' crashing...
sock_file=/root/.kde4/socket-ASUS900/kdeinit4__0
Warning: connect() failed: : Connection refused
KCrash cannot reach kdeinit, launching directly.

[1]+  Stopped                 kwrite
[root@ASUS900 david]#

[root@ASUS900 lists]# kwrite bannedextensionlists
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
KCrash: Application 'kwrite' crashing...
sock_file=/root/.kde4/socket-ASUS900/kdeinit4__0
Warning: connect() failed: : Connection refused
KCrash cannot reach kdeinit, launching directly.

[1]+  Stopped                 kwrite bannedextensionlists
[root@ASUS900 lists]#
Comment 1 Christoph Cullmann 2010-02-16 21:46:06 UTC 
If it is a real bug, then it should be a generic problem. I personally wouldn't start kwrite or any other kde app as root, but better use fish io slave.
Comment 2 Valerio 2010-07-15 01:02:25 UTC 
Just reported my crash as BUG 226868.

Thanks.
Comment 3 Christoph Feck 2010-08-08 14:02:04 UTC 

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