Bug 394617 - Konsole crash when exiting nvim
Summary: Konsole crash when exiting nvim
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 18.04.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-23 14:28 UTC by Flav
Modified: 2021-01-01 04:39 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 Flav 2018-05-23 14:28:46 UTC
Application: konsole (18.04.1)

Qt Version: 5.11.0
Frameworks Version: 5.46.0
Operating System: Linux 4.16.11-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Just execute the following command :

konsole -e 'nvim'

type `:q` and konsole crashes.

- Custom settings of the application:
If I replace nvim with vim, there is no crash, so it maybe be also related to nvim. However, I filed the bug here since it's konsole that crashes, and there is not this problem on xterm.

It doesn't crash if I first launch konsole (with a shell running), and then execute nvim and exit it back to the shell.

The crash can be reproduced every time.

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

Thread 4 (Thread 0x7f1629ba0700 (LWP 7871)):
#0  0x00007f1645436ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1  0x00007f162a83b094 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x00007f162a83ad88 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x00007f1645431075 in start_thread () from /usr/lib/libpthread.so.0
#4  0x00007f164dc3153f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1631870700 (LWP 7870)):
#0  0x00007f164dc26ea9 in poll () from /usr/lib/libc.so.6
#1  0x00007f1643446523 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f164344663e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f1649f56e64 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007f1649f0285c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007f1649d4bac9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007f1647e23976 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007f1649d55b95 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007f1645431075 in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007f164dc3153f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f16394d5700 (LWP 7869)):
#0  0x00007f164dc26ea9 in poll () from /usr/lib/libc.so.6
#1  0x00007f1645857180 in ?? () from /usr/lib/libxcb.so.1
#2  0x00007f1645858e4b in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x00007f163c072f1a in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x00007f1649d55b95 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x00007f1645431075 in start_thread () from /usr/lib/libpthread.so.0
#6  0x00007f164dc3153f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f164e2f0800 (LWP 7868)):
[KCrash Handler]
#6  0x00007f164d85afa0 in ?? () from /usr/lib/libkonsoleprivate.so.18
#7  0x00007f164d8ad0b3 in Konsole::SessionManager::sessionProfileCommandReceived(QString const&) () from /usr/lib/libkonsoleprivate.so.18
#8  0x00007f1649f2db60 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#9  0x00007f164d8e16a6 in Konsole::Session::profileChangeCommandReceived(QString const&) () from /usr/lib/libkonsoleprivate.so.18
#10 0x00007f164d8920dc in Konsole::Session::setUserTitle(int, QString const&) () from /usr/lib/libkonsoleprivate.so.18
#11 0x00007f1649f2db60 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#12 0x00007f164d8e07b7 in Konsole::Emulation::titleChanged(int, QString const&) () from /usr/lib/libkonsoleprivate.so.18
#13 0x00007f164d8db90a in ?? () from /usr/lib/libkonsoleprivate.so.18
#14 0x00007f1649f2db60 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#15 0x00007f1649f39b38 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5
#16 0x00007f1649f2e29b in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#17 0x00007f164af0a984 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#18 0x00007f164af1225b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#19 0x00007f1649f03bc9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#20 0x00007f1649f5621a in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#21 0x00007f1649f56aa2 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x00007f1643446368 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007f16434465b1 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f164344663e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007f1649f56e49 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#26 0x00007f163c107b32 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#27 0x00007f1649f0285c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#28 0x00007f1649f0ab56 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#29 0x00007f164df1bbc7 in kdemain () from /usr/lib/libkdeinit5_konsole.so
#30 0x00007f164db5c06b in __libc_start_main () from /usr/lib/libc.so.6
#31 0x000056468b2a475a in _start ()

Rapporter à https://bugs.kde.org/
Comment 1 Kurt Hindenburg 2018-05-23 17:33:47 UTC
I can't reproduce here; I'll try to do some more tests
Comment 2 Justin Zobel 2020-12-02 00:43:40 UTC
Thanks for the report.

As it's 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've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 Bug Janitor Service 2020-12-17 04:34:15 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-01 04:39:37 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!