https://bugs.kde.org/show_bug.cgi?id=495435
--- Comment #4 from Alex Bikadorov <alex.bikado...@kdemail.net> ---
Thanks. Relevant stack trace:
Stack trace of thread 3089961:
#0 0x00007766830f15d8 n/a (libQt6Widgets.so.6 + 0xf15d8)
#1 0x000077668316a7cc n/a (libQt6Widgets.so.6 + 0x16a7cc)
#2 0x00007766830fe31a
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 +
0xfe31a)
#3 0x00007766821585a8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 +
0x1585a8)
#4 0x0000776682785d4b
_ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE
(libQt6Gui.so.6 + 0x185d4b)
#5 0x0000776682801284
_ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt6Gui.so.6 + 0x201284)
#6 0x0000776682c4da14 n/a (libQt6Gui.so.6 + 0x64da14)
#7 0x000077667fb88559 n/a (libglib-2.0.so.0 + 0x5d559)
#8 0x000077667fbeb157 n/a (libglib-2.0.so.0 + 0xc0157)
#9 0x000077667fb87a55 g_main_context_iteration
(libglib-2.0.so.0 + 0x5ca55)
#10 0x00007766823bf71d
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt6Core.so.6 + 0x3bf71d)
#11 0x0000776682164566
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 +
0x164566)
#12 0x0000776682159a2f _ZN16QCoreApplication4execEv
(libQt6Core.so.6 + 0x159a2f)
#13 0x000061f1e0d5420f n/a (krusader + 0x9b20f)
#14 0x0000776681a34e08 n/a (libc.so.6 + 0x25e08)
#15 0x0000776681a34ecc __libc_start_main (libc.so.6 + 0x25ecc)
#16 0x000061f1e0d56465 n/a (krusader + 0x9d465)
It seems to be deep in Qt6 base libraries. Also, I don't get why glib2 is used
in between.
What is your exact Krusader version (git hash)?
What is your desktop environment? Plasma?
You are sure that your Arch packages, specially qt6-base and glib2 are up to
date?
>ADDITIONAL INFORMATION
>NOTE: if Alt-Enter is used instead, the GUI seemingly disappears and then
>reappears, with the Properties dialog open. Any subsequent invocation of
>Properties, via context menu or shortcut, appears OK.
That indicates maybe a bug with signal/slot code. Also fits to the stack trace
doing event processing.
I have the exact same software versions on Arch and still cannot reproduce it
:/ A stack trace with debug symbols would be good.
--
You are receiving this mail because:
You are watching all bug changes.
