Version: (using KDE KDE 3.1.3) Installed from: SuSE RPMs OS: Linux After upgrading to KDE 3.1.3 the following problem exists. If I make a krfb (remote desktop) connection, all works perfectly, but if I close the viewer/connection, I cannot reconnect unless I SSH in, then kill the following process: drkonqi -display :0.0 --appname krfb --signal 11 --pid 3416 After that, I can connect again until disconnecting... I verified this on two systems, one using the RPMs direct from SuSE, one using the RPMs from kde.org Thanks, Dave
That process running means that krfb crashed. Can you please do the following: (where PID is the PID in the command line) gdb /proc/PID/exe PID When gdb loads, type bt and paste the contents of the backtrace here.
I'm not sure if I was supposed to do the PID of the drkonqi process or the PID listed in that process string, here's both. drkonqi -display :0.0 --appname krfb --signal 11 --pid 3833: (gdb) bt #0 0x41143342 in select () from /lib/libc.so.6 #1 0x40ddbc98 in typeinfo for QMotifStyle () from /usr/lib/libqt-mt.so.3 #2 0x40971333 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #3 0x4095cf3f in QApplication::enter_loop() () from /usr/lib/libqt-mt.so.3 #4 0x40b33265 in QDialog::exec() () from /usr/lib/libqt-mt.so.3 #5 0x0804ef53 in main () #6 0x4107d8ae in __libc_start_main () from /lib/libc.so.6 krfb --kinetd 459: (gdb) bt #0 0x40c69d2a in ?? () #1 0x40369ad9 in ?? () #2 0x40c68895 in ?? () #3 <signal handler called> #4 0x00000001 in ?? () #5 0x40694662 in ?? () #6 0x402f9c09 in ?? () #7 0x0805b92e in ?? () #8 0x40dcc8ae in ?? ()
The one listed in drkonqi's command-line. Either way, none of your backtraces contain much information...
I don't know what to say... I am not sure how I can best assist in fixing this bug aside from complying with requests made, which I have done. If there are other means you'd like me to take, I'd be happy to.
Thanks, but the bug has already been reported (and fixed). The title of the other report is quite misleading, unfortunately - I should have changed it. *** This bug has been marked as a duplicate of 61904 ***
Ahh, I do see now. Thanks a ton. I'll look there for how to fix. Thanks! Dave