[Bug 1043754] New: kopete crashes whenever I enter anything
http://bugzilla.suse.com/show_bug.cgi?id=1043754 Bug ID: 1043754 Summary: kopete crashes whenever I enter anything Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since the last update (for at least six days now) whenever I enter anything in a chat window or the search box for contacts, kopete crashes. This reproduces 100%, which implies that kopete is completely unusable for me right now. Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe808deb900 (LWP 17259))] Thread 5 (Thread 0x7fe7dae1f700 (LWP 17290)): #0 0x00007fe80505b08d in poll () at /lib64/libc.so.6 #1 0x00007fe8000a2ce9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fe8000a3082 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fe7f6f223b6 in () at /usr/lib64/libgio-2.0.so.0 #4 0x00007fe8000c9bb5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fe80223b4e7 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fe805064a2f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe7e89c8700 (LWP 17289)): #0 0x00007fe805056dfd in read () at /lib64/libc.so.6 #1 0x00007fe8000e67e0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fe8000a27cb in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fe8000a2c90 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fe8000a2dfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fe8000a2e41 in () at /usr/lib64/libglib-2.0.so.0 #6 0x00007fe8000c9bb5 in () at /usr/lib64/libglib-2.0.so.0 #7 0x00007fe80223b4e7 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fe805064a2f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fe7e91c9700 (LWP 17263)): #0 0x00007fe805056dfd in read () at /lib64/libc.so.6 #1 0x00007fe8000e67e0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fe8000a27cb in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fe8000a2c90 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fe8000a2dfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fe8067e6f0e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #6 0x00007fe8067b53f4 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #7 0x00007fe8067b575e in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #8 0x00007fe7e9d48833 in QCA::SyncThread::run() () at /usr/lib64/libqca.so.2 #9 0x00007fe8066aa514 in () at /usr/lib64/libQtCore.so.4 #10 0x00007fe80223b4e7 in start_thread () at /lib64/libpthread.so.0 #11 0x00007fe805064a2f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fe7ec62e700 (LWP 17260)): #0 0x00007fe80505b08d in poll () at /lib64/libc.so.6 #1 0x00007fe8000a2ce9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fe8000a2dfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fe8067e6f0e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #4 0x00007fe8067b53f4 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #5 0x00007fe8067b575e in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #6 0x00007fe8066a7c56 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x00007fe806795943 in () at /usr/lib64/libQtCore.so.4 #8 0x00007fe8066aa514 in () at /usr/lib64/libQtCore.so.4 #9 0x00007fe80223b4e7 in start_thread () at /lib64/libpthread.so.0 #10 0x00007fe805064a2f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe808deb900 (LWP 17259)): [KCrash Handler] #6 0x00007fe8058fe2de in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1043754
http://bugzilla.suse.com/show_bug.cgi?id=1043754#c1
Wolfgang Bauer
http://bugzilla.suse.com/show_bug.cgi?id=1043754
http://bugzilla.suse.com/show_bug.cgi?id=1043754#c2
Gerald Pfeifer
http://bugzilla.suse.com/show_bug.cgi?id=1043754
http://bugzilla.suse.com/show_bug.cgi?id=1043754#c3
Wolfgang Bauer
the crash no longer occurs -- even if
2284 tty2 Sl 0:00 ibus-daemon --xim --panel disable 2289 tty2 Sl 0:00 /usr/lib64/ibus/ibus-dconf 2291 tty2 Sl 0:05 /usr/lib64/ibus/ibus-x11 --kill-daemon 2558 tty2 Sl 0:00 /usr/lib64/ibus/ibus-engine-simple
are still running.
I suppose that's because ibus-qt is not installed any more, so Qt4 applications don't use it. Maybe the crash is actually a bug in ibus-qt, the applications mentioned in bug#1043734 (and kopete) all use Qt4.
Thanks for the great hint! Is there anything we can do for users in general?
Yes, fix bug#1043734. ;-) Or not install ibus (or ibus-qt). A default KDE installation doesn't do that anyway, but I think GNOME pulls it in. *** This bug has been marked as a duplicate of bug 1043734 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com