Version: (using KDE KDE 3.5.1) Installed from: Debian testing/unstable Packages It happens to me quite often that I start kopete, and then it runs, but displays no main window and no tray icon either. Instead, the tray contains an empty spot where kopete should have been. Killing kopete and starting it again usually gets it going.
can you run gdb and get a backtrace when it happen ? gdb kopete `pidof kopete`
did the backtrace: Reading symbols from /usr/lib/i686/cmov/libcrypto.so.0.9.8...(no debugging symbols found)...done. Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb641556e in __lll_mutex_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb64120c0 in _L_mutex_lock_29 () from /lib/tls/i686/cmov/libpthread.so.0 #3 0x08915f96 in ?? () #4 0x00d1606c in ?? () #5 0x00000000 in ?? () (gdb)
another one today: Loaded symbols for /usr/lib/i686/cmov/libssl.so.0.9.8 Reading symbols from /usr/lib/i686/cmov/libcrypto.so.0.9.8...(no debugging symbols found)...done. Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8 0xffffe410 in __kernel_vsyscall () (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb644856e in __lll_mutex_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb64450c0 in _L_mutex_lock_29 () from /lib/tls/i686/cmov/libpthread.so.0 #3 0x08915f96 in ?? () #4 0x00d4a50c in ?? () #5 0x00000000 in ?? () (gdb)
which version of kopete? do you have a webcam or other V4L compatible device connected to your system? if you wait for about 30 seconds or so, does kopete eventually show up?
Kopete 0.11.1 using KDE 3.5.1 No webcam or other V4L compatible device connected If I wait for about 30 seconds or so, kopete does not show up
> > ------- Additional Comments From ralf.hildebrandt charite de 2006-03-18 13:32 ------- > Kopete 0.11.1 using KDE 3.5.1 > No webcam or other V4L compatible device connected > If I wait for about 30 seconds or so, kopete does not show up what happens if you run it from a terminal? -- This insane ranting was brought to you by evyl bananas, and the number 3. www.chani3.com
waiting for a response for the terminal question. please reopen when you can provide an answer.
Closing bugs that were not fixed is really bad style.
But, alas, it seems that with KDE 3.5.2 the bug doesn't occur anymore.