Application: kwrite (4.4.2 (KDE 4.4.2)) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: It was started from bash within screen, first with a file to open ('.gitconfig'), then without any command-line options at all, and it crashed on open. It managed to write 'sock_file=/home/wendell/.kde/socket-wacky/kdeinit4__0' to the terminal first. This seems to me to be rather serious... kwrite won't even run normally without any options. The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Aborted [KCrash Handler] #6 0x0089f422 in __kernel_vsyscall () #7 0x003b4651 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x003b7a82 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x089c22dc in qt_message_output (msgType=QtFatalMsg, buf=0x99d6fc8 "kwrite(11171): Session bus not found \n") at global/qglobal.cpp:2250 #10 0x009923b5 in ~QDebug (this=0xbfc45710, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qdebug.h:85 #11 0x00a81b3c in KApplicationPrivate::init (this=0x99bba48, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:501 #12 0x00a83347 in KApplication (this=0xbfc45838, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:343 #13 0x00860377 in ?? () from /usr/lib/libkdeinit4_kwrite.so #14 0x0085b10e in kdemain () from /usr/lib/libkdeinit4_kwrite.so #15 0x080485fb in _start () This bug may be a duplicate of or related to bug 237928. Possible duplicates by query: bug 237928. Reported using DrKonqi
It looks like your dbus is not working properly (so that this isn't a kwrite problem). What does "started from bash within screen" mean exactly? Is it that you logged in to KDE, opened konsole/xterm/whatever, created a screen session therein and tried to run kwrite? This should work, try running echo $DBUS_SESSION_BUS_ADDRESS or qdbus within that bash to check your dbus (you can look for dbus-daemon processes running, too). OTOH if your situation is something like "started a screen from within KDE, then detached the screen session and logged out from KDE and now reattached to the screen session", then that can't work because the bash within that screen has stale DBUS_SESSION_BUS_ADDRESS pointing to a dbus-daemon that is not there anymore (went down with the first KDE session). You'll have to update it (just copy the information from a brand-new bash shell).
For sure no kwrite problem. Thanks for the explanation, hope it helped the user.