Bug 328964 - Konversation crashed when Ctrl+W was pressed
Summary: Konversation crashed when Ctrl+W was pressed
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-12-18 13:26 UTC by Syam
Modified: 2017-07-05 13:05 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 Syam 2013-12-18 13:26:32 UTC
Application: konversation (1.5-branch #4217)
KDE Platform Version: 4.11.3
Qt Version: 4.8.5
Operating System: Linux 3.11.10-200.fc19.x86_64 x86_64
Distribution: "Fedora release 19 (Schrödinger’s Cat)"

-- Information about the crash:
- What I was doing when the application crashed:
Straight after starting Konversation, it opened the set of default channels, I selected the first channel tab (perhaps #fedora), and pressed Ctrl+W to close it and Konversation crashed.

Couldn't reproduce afterwards.

The crash does not seem to be reproducible.

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

Thread 2 (Thread 0x7f2e532fc700 (LWP 2228)):
#0  0x000000380900e0bd in read () from /lib64/libpthread.so.0
#1  0x0000003c60e864f0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x0000003c60e47c0c in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x0000003c60e4807b in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0
#4  0x0000003c60e481ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#5  0x0000003c623a7166 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#6  0x0000003c62378ecf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#7  0x0000003c623791c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#8  0x0000003c6227866f in QThread::exec() () from /lib64/libQtCore.so.4
#9  0x0000003c6235a733 in QInotifyFileSystemWatcherEngine::run() () from /lib64/libQtCore.so.4
#10 0x0000003c6227ad0f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4
#11 0x0000003809007c53 in start_thread () from /lib64/libpthread.so.0
#12 0x00000038088f5dbd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f2e5ffac8c0 (LWP 2226)):
[KCrash Handler]
#5  0x0000003c63c3dfea in QApplication::x11ProcessEvent(_XEvent*) () from /lib64/libQtGui.so.4
#6  0x0000003c63c64e54 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtGui.so.4
#7  0x0000003c60e47df6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#8  0x0000003c60e48148 in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0
#9  0x0000003c60e481ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#10 0x0000003c623a7145 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#11 0x0000003c63c64fc6 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
#12 0x0000003c62378ecf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#13 0x0000003c623791c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#14 0x0000003c6237e45b in QCoreApplication::exec() () from /lib64/libQtCore.so.4
#15 0x000000000044ac70 in main ()

Possible duplicates by query: bug 328758, bug 328736, bug 328535, bug 328255, bug 328229.

Reported using DrKonqi
Comment 1 Syam 2017-07-05 13:05:38 UTC
This is an old report. I can no longer reproduce with the current version. So closing.