[konsole] [Bug 441217] New: Konsole crached after pressing Ctrl+D in one of its splits
Vitaliy Perekhovy
bugzilla_noreply at kde.org
Fri Aug 20 09:31:12 BST 2021
https://bugs.kde.org/show_bug.cgi?id=441217
Bug ID: 441217
Summary: Konsole crached after pressing Ctrl+D in one of its
splits
Product: konsole
Version: 21.08.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: konsole-devel at kde.org
Reporter: feriman at gmail.com
Target Milestone: ---
Application: konsole (21.08.0)
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.13.12-gentoo-x86_64 x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: Gentoo/Linux
-- Information about the crash:
Steps to reproduce:
1. Start Konsole with ONE tab opened.
2. Split Konsole window.
3. Start some interactive program (like top or mc) in one of the created
splits.
4. Select another split and press Ctrl+D.
Note: Without step 3, Konsole is not crached but closed.
The crash can be reproduced every time.
-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
[KCrash Handler]
#4 0x00007f0afc37526e in QObject::startTimer(int, Qt::TimerType) () from
/usr/lib64/libQt5Core.so.5
#5 0x00007f0afc37e6dc in QTimer::start() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f0afc37a871 in ?? () from /usr/lib64/libQt5Core.so.5
#7 0x00007f0afd503532 in Konsole::TerminalDisplay::compositeFocusChanged(bool)
() from /usr/lib64/libkonsoleprivate.so.21
#8 0x00007f0afc37a871 in ?? () from /usr/lib64/libQt5Core.so.5
#9 0x00007f0afd5035ef in ?? () from /usr/lib64/libkonsoleprivate.so.21
#10 0x00007f0afd56d9b8 in ?? () from /usr/lib64/libkonsoleprivate.so.21
#11 0x00007f0afc34c075 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQt5Core.so.5
#12 0x00007f0afcde7d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#13 0x00007f0afcdf0950 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#14 0x00007f0afc34c2b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#15 0x00007f0afcdee239 in QApplicationPrivate::setFocusWidget(QWidget*,
Qt::FocusReason) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007f0afce23b7f in QWidget::setFocus(Qt::FocusReason) () from
/usr/lib64/libQt5Widgets.so.5
#17 0x00007f0afcdee722 in QApplication::setActiveWindow(QWidget*) () from
/usr/lib64/libQt5Widgets.so.5
#18 0x00007f0afcdee79b in
QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from
/usr/lib64/libQt5Widgets.so.5
#19 0x00007f0afc7de8d5 in
QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*)
() from /usr/lib64/libQt5Gui.so.5
#20 0x00007f0afc7e35ac in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib64/libQt5Gui.so.5
#21 0x00007f0afc7be25b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib64/libQt5Gui.so.5
#22 0x00007f0af689286a in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#23 0x00007f0afa6a149b in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#24 0x00007f0afa6a1748 in ?? () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f0afa6a17ff in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#26 0x00007f0afc397140 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQt5Core.so.5
#27 0x00007f0afc34ad63 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQt5Core.so.5
#28 0x00007f0afc352700 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#29 0x00005644e8498b71 in ?? ()
#30 0x00007f0afbd8d7fd in __libc_start_main () from /lib64/libc.so.6
#31 0x00005644e8498efa in ?? ()
[Inferior 1 (process 26131) detached]
Possible duplicates by query: bug 440619, bug 429884, bug 297152, bug 286386,
bug 281349.
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the konsole-devel
mailing list