Bug 396992 - Konsole crash while executing find and opening another tab
Summary: Konsole crash while executing find and opening another tab
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 17.04.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-07-30 20:08 UTC by Gary Lindquist
Modified: 2021-01-16 04:37 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 Gary Lindquist 2018-07-30 20:08:05 UTC
Application: konsole (17.04.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.140-62-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Had Konsole open and (as root) was executing 'find . -iname "*clamd*"'.  It was taking a long time so I clicked on File -> New Tab.  Before opening the new tab the application crashed.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f88745cf8c0 (LWP 31383))]

Thread 3 (Thread 0x7f885d304700 (LWP 31393)):
#0  0x00007f8873f1f30d in poll () at /lib64/libc.so.6
#1  0x00007f886b939314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f886b93942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f88705201ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f88704cdbfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f8870308f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f886e6cd295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007f887030da29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f886be56724 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8873f27e8d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f885f69e700 (LWP 31392)):
#0  0x00007f8873f1f30d in poll () at /lib64/libc.so.6
#1  0x00007f886c2793c2 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f886c27afaf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f8861bf90d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f887030da29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007f886be56724 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f8873f27e8d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f88745cf8c0 (LWP 31383)):
[KCrash Handler]
#6  0x00007f88704cfbd0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#7  0x00007f88704d19ca in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8870520b03 in  () at /usr/lib64/libQt5Core.so.5
#9  0x00007f886b939134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#10 0x00007f886b939388 in  () at /usr/lib64/libglib-2.0.so.0
#11 0x00007f886b93942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#12 0x00007f887052018c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#13 0x00007f88704cdbfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#14 0x00007f88704d5ae6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#15 0x00007f8874208fca in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#16 0x00007f8873e5b725 in __libc_start_main () at /lib64/libc.so.6
#17 0x0000000000400789 in _start ()

Reported using DrKonqi
Comment 1 Kurt Hindenburg 2018-08-03 14:16:23 UTC
We've seen a lot of these crashes with Qt5.6; best bet would be to upgrade to a newer Qt and KDE.
Comment 2 Justin Zobel 2020-12-17 05:38:39 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 3 Bug Janitor Service 2021-01-01 04:38:44 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 4 Bug Janitor Service 2021-01-16 04:37:30 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!