You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2024-03-14 09:10:04
- 0BADC0DE
- Member
- From: Regnum Utriusque Siciliae
- Registered: 2018-02-21
- Posts: 342
Weird coredumps killing GTK-based apps
Hi all.
I am getting this weird behavior: sometimes I get my dual-screen system (1 HDMI and 1 USB) killing any GTK-base application (Vivaldi and VScode in my case) and turning off and on both screens.
This is what I can see in the logs but I am not sure is it related (though I have never got a core dump from konsole in 10 years).
I would like to help fixing/troubleshooting this.
Any hint?
mar 14 10:02:05 Feynman kernel: konsole[5494]: segfault at 6ffffffff ip 000072ae2bd8d813 sp 00007ffd73182410 error 4 in libQt6WaylandClient.so.6.6.2[72ae2bd7c000+57000] likely on CPU 3 (core 3, socket 0)
mar 14 10:02:05 Feynman kernel: Code: 48 89 c7 48 8d 40 f0 48 85 ff 48 0f 45 f8 e8 b4 07 02 00 48 89 c6 48 85 c0 0f 84 1a ff ff ff 48 89 df e8 90 98 ff ff 48 89 c7 <48> 8b 00 ff 50 28 48 8d 7b 18 48 89 ee e8 3b c5 ff ff e9 f8 fe ff
mar 14 10:02:05 Feynman systemd[1]: Started Process Core Dump (PID 11856/UID 0).
mar 14 10:02:07 Feynman systemd-coredump[11857]: [?] Process 5494 (konsole) of user 1000 dumped core.
Stack trace of thread 5494:
#0 0x000072ae2bd8d813 n/a (libQt6WaylandClient.so.6 + 0x6e813)
#1 0x000072ae2e578f9a _ZN22QGuiApplicationPrivate20_q_updateFocusObjectEP7QObject (libQt6Gui.so.6 + 0x178f9a)
#2 0x000072ae2df90fab n/a (libQt6Core.so.6 + 0x190fab)
#3 0x000072ae2e5ce497 _ZN7QWindow18focusObjectChangedEP7QObject (libQt6Gui.so.6 + 0x1ce497)
#4 0x000072ae2ef4b5b1 n/a (libQt6Widgets.so.6 + 0x14b5b1)
#5 0x000072ae2eef59b8 _ZN19QApplicationPrivate15setActiveWindowEP7QWidget (libQt6Widgets.so.6 + 0xf59b8)
#6 0x000072ae2eef5cb1 _ZN19QApplicationPrivate24notifyActiveWindowChangeEP7QWindow (libQt6Widgets.so.6 + 0xf5cb1)
#7 0x000072ae2e571db5 _ZN22QGuiApplicationPrivate21processActivatedEventEPN29QWindowSystemInterfacePrivate20ActivatedWindowEventE (libQt6Gui.so.6 + 0x171db5)
#8 0x000072ae2e5da85c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x1da85c)
#9 0x000072ae2e9b26c4 n/a (libQt6Gui.so.6 + 0x5b26c4)
#10 0x000072ae2c84df69 n/a (libglib-2.0.so.0 + 0x59f69)
#11 0x000072ae2c8ac3a7 n/a (libglib-2.0.so.0 + 0xb83a7)
#12 0x000072ae2c84c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#13 0x000072ae2e1739c4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3739c4)
#14 0x000072ae2df43d6e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x143d6e)
#15 0x000072ae2df3c2b8 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x13c2b8)
#16 0x000057ff20565695 n/a (konsole + 0x6695)
#17 0x000072ae2d843cd0 n/a (libc.so.6 + 0x25cd0)
#18 0x000072ae2d843d8a __libc_start_main (libc.so.6 + 0x25d8a)
#19 0x000057ff20565fd5 n/a (konsole + 0x6fd5)
Stack trace of thread 10149:
#0 0x000072ae2d9190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x000072ae2bd83b18 n/a (libQt6WaylandClient.so.6 + 0x64b18)
#2 0x000072ae2e0a0bd3 n/a (libQt6Core.so.6 + 0x2a0bd3)
#3 0x000072ae2d8a955a n/a (libc.so.6 + 0x8b55a)
#4 0x000072ae2d926a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 10150:
#0 0x000072ae2d9190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x000072ae2bd83b18 n/a (libQt6WaylandClient.so.6 + 0x64b18)
#2 0x000072ae2e0a0bd3 n/a (libQt6Core.so.6 + 0x2a0bd3)
#3 0x000072ae2d8a955a n/a (libc.so.6 + 0x8b55a)
#4 0x000072ae2d926a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 5495:
#0 0x000072ae2d9190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x000072ae2c8ac2f6 n/a (libglib-2.0.so.0 + 0xb82f6)
#2 0x000072ae2c84c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x000072ae2e1739c4 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3739c4)
#4 0x000072ae2df43d6e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x143d6e)
#5 0x000072ae2e02106f _ZN7QThread4execEv (libQt6Core.so.6 + 0x22106f)
#6 0x000072ae2cc769df n/a (libQt6DBus.so.6 + 0x299df)
#7 0x000072ae2e0a0bd3 n/a (libQt6Core.so.6 + 0x2a0bd3)
#8 0x000072ae2d8a955a n/a (libc.so.6 + 0x8b55a)
#9 0x000072ae2d926a3c n/a (libc.so.6 + 0x108a3c)
ELF object binary architecture: AMD x86-64
mar 14 10:02:07 Feynman systemd[1]: systemd-coredump@1-11856-0.service: Deactivated successfully.
mar 14 10:02:07 Feynman systemd[1]: systemd-coredump@1-11856-0.service: Consumed 1.291s CPU time.Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.
Offline
#2 2024-03-14 09:47:04
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 76,016
Re: Weird coredumps killing GTK-based apps
turning off and on both screens
I'd rather look at that - are there any (other) error messages around the crash?
Offline
#3 2024-03-14 10:08:31
- 0BADC0DE
- Member
- From: Regnum Utriusque Siciliae
- Registered: 2018-02-21
- Posts: 342
Re: Weird coredumps killing GTK-based apps
turning off and on both screens
I'd rather look at that - are there any (other) error messages around the crash?
This is what I see "around" that event.
I am not sure I fully get how to use debuginfod once I have got the "debuginfo" file.
Do I need to use that for file a bug?
Maybe Computers Will Never Become As Intelligent
As Humans. Surely They Won't Ever Become So Stupid.
Offline
#4 2024-03-14 15:33:18
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 76,016
Re: Weird coredumps killing GTK-based apps
It'll probably be helpful - if you've the crash in https://wiki.archlinux.org/title/Core_d … _core_dump installing debuginfod should™ allow you to see it w/ full symbols.
A somewhat similar backtrace shows up in https://bugs.kde.org/show_bug.cgi?id=341798 which was about IMs, do you use one (fcitx, ibus, etcetc.)?
Offline
Pages: 1