Bug 471023 - Konsole Crashes after long period of no activity
Summary: Konsole Crashes after long period of no activity
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 22.12.3
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
Keywords: drkonqi
Depends on:
Reported: 2023-06-14 14:02 UTC by Sandy
Modified: 2023-10-09 17:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Sandy 2023-06-14 14:02:33 UTC
Application: konsole (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-20-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Konsole crash window is displayed when again login to my system, though there were many time no activity / process were executed.
Specific to customization I've installed zsh with powerline theme.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault

[KCrash Handler]
#4  __memcpy_evex_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#5  0x00007f82cd4ef53a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x00007f82cd4efb59 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x00007f82cd4f04a9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007f82d3d0a0c2 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007f82d4379787 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007f82d437b339 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f82d437d4d8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f82d43c7a01 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f82d43cb7eb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f82d436bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f82d36bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f82d3b3e8f4 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x00007f82d3b164bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f82cd4fa54e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007f82d19d249d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f82d1a2d178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f82d19d11b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f82d3714e7a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f82d36b97cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f82d36c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00005624e719a7c1 in ?? ()
#26 0x00007f82d2c23a90 in __libc_start_call_main (main=main@entry=0x5624e7198ce0, argc=argc@entry=1, argv=argv@entry=0x7fff0b37b938) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x00007f82d2c23b49 in __libc_start_main_impl (main=0x5624e7198ce0, argc=1, argv=0x7fff0b37b938, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff0b37b928) at ../csu/libc-start.c:360
#28 0x00005624e719b055 in ?? ()
[Inferior 1 (process 869592) detached]

Reported using DrKonqi
Comment 1 Craig Edwards 2023-09-06 08:26:03 UTC
I would like to add a further bit of detail to this bug.

I went to log this bug and it was flagged as a duplicate, but i think this may be related to thunderbolt/usb3 docks, or change of display configuration from hot plugging a display.

This happens and is repeatable for me if i plug in my usb 3 dock to my laptop and let it detect the two displays that are plugged into it. The displays will do their usual rearrangement and appear, but often multiple programs crash as the display dimensions change.

Usual culprits are konsole (this bug) and discord.
Comment 2 Trent Whaley 2023-10-09 17:32:05 UTC
I experienced this or similar behaviour. I do not have a USB-C dock in use as I am on a desktop with single display, not being hotplugged (nor a KVM, which would do that), though the monitor may have been shut off by power management. I will disable monitor power management and see if issue recurs again today.

My system is a fresh install (yesterday) of Kubuntu 23.04 with all updates applied and user profile copied from old system (22.10, user Konsole profile settings did not transfer). My terminal font is Atkinson Hyperlegible.