Bug 308837 - Konversation crashed after issuing /part command
Summary: Konversation crashed after issuing /part command
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-22 21:56 UTC by K Garton
Modified: 2012-10-23 18:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description K Garton 2012-10-22 21:56:16 UTC
Application: konversation (1.4)
KDE Platform Version: 4.9.2
Qt Version: 4.8.2
Operating System: Linux 3.3.4-5.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I had been logged into Konversation across some 7 or so channels on 4 different servers and was /join ing some channels to see if they were already registered and then /part ing from them. After one such /part, Konversation crashed.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a611d0880 (LWP 9744))]

Thread 2 (Thread 0x7f5a53e04700 (LWP 9745)):
#0  0x000000335e80aa74 in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0
#1  0x0000003360083731 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#2  0x000000336004715d in g_main_context_prepare () from /lib64/libglib-2.0.so.0
#3  0x000000336004788b in ?? () from /lib64/libglib-2.0.so.0
#4  0x0000003360047a84 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#5  0x0000003bff7a44e6 in QEventDispatcherGlib::processEvents (this=0x7f5a4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x0000003bff77510f in QEventLoop::processEvents (this=this@entry=0x7f5a53e03cf0, flags=...) at kernel/qeventloop.cpp:149
#7  0x0000003bff775398 in QEventLoop::exec (this=0x7f5a53e03cf0, flags=...) at kernel/qeventloop.cpp:204
#8  0x0000003bff678650 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x0000003bff755b2f in QInotifyFileSystemWatcherEngine::run (this=0x15efa20) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x0000003bff67b5eb in QThreadPrivate::start (arg=0x15efa20) at thread/qthread_unix.cpp:307
#11 0x000000335e807d14 in start_thread () from /lib64/libpthread.so.0
#12 0x000000335e4f197d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5a611d0880 (LWP 9744)):
[KCrash Handler]
#6  0x0000003c01043c7a in QApplication::x11ProcessEvent (this=0x7fffbe3515e0, event=0x7fffbe3510b0) at kernel/qapplication_x11.cpp:3426
#7  0x0000003c0106a4cc in x11EventSourceDispatch (s=0x142a500, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#8  0x0000003360047695 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#9  0x00000033600479c8 in ?? () from /lib64/libglib-2.0.so.0
#10 0x0000003360047a84 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#11 0x0000003bff7a44e6 in QEventDispatcherGlib::processEvents (this=0x13c9350, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x0000003c0106a1ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#13 0x0000003bff77510f in QEventLoop::processEvents (this=this@entry=0x7fffbe351480, flags=...) at kernel/qeventloop.cpp:149
#14 0x0000003bff775398 in QEventLoop::exec (this=0x7fffbe351480, flags=...) at kernel/qeventloop.cpp:204
#15 0x0000003bff77a188 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#16 0x0000000000445c13 in main (argc=5, argv=0x7fffbe3517b8) at /usr/src/debug/konversation-1.4/src/main.cpp:120

Possible duplicates by query: bug 308481, bug 307631, bug 307507, bug 307023, bug 306575.

Reported using DrKonqi
Comment 1 Eike Hein 2012-10-23 18:32:03 UTC
Thank you for your report, but unfortunately this backtrace doesn't provide enough information to pinpoint a reason for your problem (no Konversation code shows up in those hops). Please reopen if you can provide any additional information that might enable us to reproduce this on our end.