Bug 414727 - Konversation crashes without any user input
Summary: Konversation crashes without any user input
Status: RESOLVED DUPLICATE of bug 437595
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.7.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-01 19:45 UTC by William
Modified: 2021-12-19 15:24 UTC (History)
2 users (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 William 2019-12-01 19:45:11 UTC
SUMMARY
I started Konversation, connected to a server, joined a couple of channels and minimized the window. While I was using another app (firefox, the last time), Konversation crashed.
This has happened both on Windows 10 (1909) and openSUSE Leap 15.1, both times running the 1.7.5 version. The Windows version was downloaded from https://binary-factory.kde.org/.

STEPS TO REPRODUCE
1. Open Konversation;
2. Connect to a server and join a channel;
3. Minimize Konversation;
4. Wait a few minutes (about 20 to 40 minutes(?) - it's not constant) until it crashes.

OBSERVED RESULT
Konversation crashes silently. The last time (in openSUSE), I ran it from the console to check if I got an error to display there, and it actually brought up the KDE crash reporter; The generated report is pasted under "Additional Information".

EXPECTED RESULT
Keep Konversation running.

SOFTWARE/OS VERSIONS
Windows: Windows 10 (1909, 64-bit)
Linux/KDE Plasma: openSUSE Leap 15.1, KDE Plasma 5.12.8
(openSUSE)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.55.0
Qt Version: 5.9.7
(Windows 10 - information taken from "About Konversation")
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2 (built against 5.13.2)

ADDITIONAL INFORMATION
KDE generated crash report:

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

Thread 6 (Thread 0x7f8131ce6700 (LWP 2525)):
#0  0x00007f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x00007f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x00007f815b08d569 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f815d6099ef in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8132628700 (LWP 2524)):
#0  0x00007f815b0938ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f813739c83b in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x00007f813739c547 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x00007f815b08d569 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f815d6099ef in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8146be7700 (LWP 2523)):
#0  0x00007f815d5ff19b in poll () from /lib64/libc.so.6
#1  0x00007f81578551a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f81578552bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f815e27c96b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007f815e22190a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x00007f815b08d569 in start_thread () from /lib64/libpthread.so.0
#8  0x00007f815d6099ef in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f8147fff700 (LWP 2522)):
#0  0x00007f8157854640 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f81578550db in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f81578552bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f815e27c96b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4  0x00007f815e22190a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5  0x00007f815e03fdaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x00007f815e6fc9e5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x00007f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x00007f815b08d569 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f815d6099ef in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f814f56c700 (LWP 2521)):
#0  0x00007f815d5ff19b in poll () from /lib64/libc.so.6
#1  0x00007f8159416307 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f8159417f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f8152324939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f815e044ced in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007f815b08d569 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f815d6099ef in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8164a58900 (LWP 2520)):
[KCrash Handler]
#6  0x00007f815e0bf6e3 in operator==(QString const&, QString const&) () from /usr/lib64/libQt5Core.so.5
#7  0x0000562f782d32d9 in ?? ()
#8  0x0000562f782e035c in ?? ()
#9  0x0000562f782e96fd in ?? ()
#10 0x0000562f78297b9b in ?? ()
#11 0x0000562f783f937f in ?? ()
#12 0x00007f815e252535 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#13 0x00007f815e25f087 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5
#14 0x00007f815e25f3e8 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5
#15 0x00007f815e25305b in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#16 0x00007f815f6f33dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#17 0x00007f815f6faca4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#18 0x00007f815e2238d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#19 0x00007f815e27bdee in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#20 0x00007f815e27c5b1 in ?? () from /usr/lib64/libQt5Core.so.5
#21 0x00007f8157854e87 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f8157855230 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f81578552bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f815e27c94f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#25 0x00007f815e22190a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#26 0x00007f815e22a9b4 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#27 0x0000562f7822be80 in ?? ()
#28 0x00007f815d531f8a in __libc_start_main () from /lib64/libc.so.6
#29 0x0000562f7823ab1a in _start ()
[Inferior 1 (process 2520) detached]
Comment 1 Sam Wilson 2021-06-12 08:30:38 UTC
I've noticed this happening usually a few minutes (or less) after waking the system from sleep. Konversation looks fine, but as soon as I interact with it it crashes with:

Connection broken with state 5 and error: "The remote host closed the connection"
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konversation path = /usr/bin pid = 197606
KCrash: Arguments: /usr/bin/konversation 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
[1]+  Stopped                 konversation
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
Comment 2 Friedrich W. H. Kossebau 2021-12-19 15:24:07 UTC
Thanks for the report. While the backtrace sadly lacks the needed info for the chain of calls ending up in the crashing operator== call, the present calls and the crash description hint this is the same cause as for the fixed bug 437595, so closing as duplicate.

Please reopen if still seeing with versions >= 1.8.21080.

*** This bug has been marked as a duplicate of bug 437595 ***