Bug 485012 - Console crashes when external display connected
Summary: Console crashes when external display connected
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 23.08.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-04-04 07:07 UTC by Craig Edwards
Modified: 2024-06-07 00:52 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 Craig Edwards 2024-04-04 07:07:32 UTC
Application: konsole (23.08.1)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-26-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
connecting kde to two external hdmi via a dock reproducibly crashes konsole

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  0x00007e38f29fa48a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x00007e38f29faaa9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x00007e38f29fb3e9 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x00007e38f931850c in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007e38f9979557 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007e38f997b0e9 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007e38f997d278 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007e38f99c75e1 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007e38f99cb312 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007e38f996bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007e38f8ccc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007e38f91401c4 in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x00007e38f911762c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007e38f2a05f7e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007e38f6d13b2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007e38f6d6f46f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007e38f6d11d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007e38f8d27daa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007e38f8ccb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007e38f8cd3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00005a05713aa791 in ?? ()
#26 0x00007e38f8228150 in __libc_start_call_main (main=main@entry=0x5a05713a8d00, argc=argc@entry=1, argv=argv@entry=0x7ffdf7867528) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x00007e38f8228209 in __libc_start_main_impl (main=0x5a05713a8d00, argc=1, argv=0x7ffdf7867528, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdf7867518) at ../csu/libc-start.c:360
#28 0x00005a05713aafe5 in ?? ()
[Inferior 1 (process 1591410) detached]

The reporter indicates this bug may be a duplicate of or related to bug 484326.

Reported using DrKonqi
Comment 1 Christoph Cullmann 2024-06-06 22:13:55 UTC
Can not reproduce that with a more recent version, please try 24.02 or higher, thanks.

Qt 5.x had some bugs related to this, the Qt 6 version should be more robust.
Comment 2 Craig Edwards 2024-06-07 00:52:49 UTC
i updated to 24.04 when it came out, and havent seen this issue for a while. I dont know if it was updating to 24.04 or some other update that has either fixed it or made it much less frequent.