Bug 340746 - Konversation crashed after closing a query tab with Strg+W
Summary: Konversation crashed after closing a query tab with Strg+W
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-07 23:29 UTC by Bruno Kiste
Modified: 2018-11-30 04:02 UTC (History)
0 users

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 Bruno Kiste 2014-11-07 23:29:32 UTC
I had Konversation running for about one hour. I was connected to exacly one server. I had two channels and one Query open. When I wanted to close the Query, using Strg+W Konversation crashed.
I tried to reproduce the error 5 times. I does not seem to be reproducible.

The crash does not seem to be reproducible.


Reproducible: Couldn't Reproduce




-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb447d740 (LWP 4852))]

Thread 2 (Thread 0xb1564b40 (LWP 4872)):
#0  0xb505e13a in __pthread_mutex_unlock_usercnt (mutex=0xb0c00558, decr=<optimized out>) at pthread_mutex_unlock.c:93
#1  0xb555f8f4 in pthread_mutex_unlock (mutex=0xb0c00558) at forward.c:194
#2  0xb4dfe120 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4db92cf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb4db9528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb641f95f in QEventDispatcherGlib::processEvents (this=0xb0c00468, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0xb63ee823 in QEventLoop::processEvents (this=this@entry=0xb1564258, flags=...) at kernel/qeventloop.cpp:149
#7  0xb63eeb49 in QEventLoop::exec (this=this@entry=0xb1564258, flags=...) at kernel/qeventloop.cpp:204
#8  0xb62db23d in QThread::exec (this=this@entry=0x9d46e30) at thread/qthread.cpp:537
#9  0xb63cec44 in QInotifyFileSystemWatcherEngine::run (this=0x9d46e30) at io/qfilesystemwatcher_inotify.cpp:265
#10 0xb62ddb6f in QThreadPrivate::start (arg=0x9d46e30) at thread/qthread_unix.cpp:349
#11 0xb505af70 in start_thread (arg=0xb1564b40) at pthread_create.c:312
#12 0xb55524ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xb447d740 (LWP 4852)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0xb59069ad in QApplication::x11ProcessEvent (this=0xbf9a52e0, event=event@entry=0xbf9a4f6c) at kernel/qapplication_x11.cpp:3529
#9  0xb5933524 in x11EventSourceDispatch (s=0x9bcd140, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#10 0xb4db91e3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb4db9468 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 0xb4db9528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 0xb641f95f in QEventDispatcherGlib::processEvents (this=this@entry=0x97aeeb8, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#14 0xb59335de in QGuiEventDispatcherGlib::processEvents (this=0x97aeeb8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#15 0xb63ee823 in QEventLoop::processEvents (this=this@entry=0xbf9a5228, flags=...) at kernel/qeventloop.cpp:149
#16 0xb63eeb49 in QEventLoop::exec (this=this@entry=0xbf9a5228, flags=...) at kernel/qeventloop.cpp:204
#17 0xb63f48fe in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#18 0xb587ca24 in QApplication::exec () at kernel/qapplication.cpp:3828
#19 0x08082f8c in ?? ()
#20 0xb547fa83 in __libc_start_main (main=0x8080eb0, argc=3, argv=0xbf9a5414, init=0x823fcc0 <__libc_csu_init>, fini=0x823fd30 <__libc_csu_fini>, rtld_fini=0xb778b180 <_dl_fini>, stack_end=0xbf9a540c) at libc-start.c:287
#21 0x08098f88 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 328964.

Possible duplicates by query: bug 339285, bug 339046, bug 336966, bug 336796, bug 336756.
Comment 1 Andrew Crouthamel 2018-10-31 03:57:03 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-15 10:49:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-30 04:02:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!