https://bugs.kde.org/show_bug.cgi?id=528089
Bug ID: 528089
Summary: Icons-and-text task manager glitches out after waking
display
Classification: Plasma
Product: plasmashell
Version First 6.7.5
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Task Manager and Icons-Only Task Manager widgets
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: 1.0
This was *going* to be A Dr Konqi report, but it refuses to submit because
"gathering crash information failed for unknown reasons".
I have a displayport monitor that interacts poorly with my Haswell iGPU. I had
to disable drm kms polling to stop the backlight from turning on ever 30s.
Whenever the monitor wakes up, there is an error in dmesg, and Plasma's panels
glitch out and (usually) recover. Google's free model has a theory about why,
which may be a hallucination.
See https://share.gemini.google/unMHtawQ9Zat
I haven't yet (fully) tried its suggestion of deleting
`~/.local/share/kscreen/`. I couldn't find a way to get it regenerated without
a reboot.
The (not attached) crash dump is the one from the 2nd-to-last turn of that
chat, when I manually restarted plasmashell with `systemctl restart`.
Relevant message from me:
Disabling drm kms polling made it stop waking up every 30 s when idle, *but* I
still see the same i915 error in the logs when I wake up the display
intentionally. And when I unlock the screen, KDE Plasma's taskbar glitches out
for 2-10 seconds (invisible; then window list all piled to one end and jittery,
etc.) before finally reasserting itself.
Log shows a bunch of repeated
> plasmashell[3256]: Final member StackingOrder is overridden in class
> QQmlDMAbstractItemModelData. The override won't be used.
and then a bunch of repeated
> plasmashell[3256]:
> qrc:/qt/qml/plasma/applet/org/kde/plasma/taskmanager/main.qml:430:13: QML
> TaskList: Binding loop detected for property "stripeCount":
>qrc:/qt/qml/plasma/applet/org/kde/plasma/taskmanager/TaskList.qml:33:5
> plasmashell[3256]:
> qrc:/qt/qml/plasma/applet/org/kde/plasma/taskmanager/main.qml:430:13: QML
> TaskList: Binding loop detected for property "heightOccupation":
>qrc:/qt/qml/plasma/applet/org/kde/plasma/taskmanager/main.qml:442:
DR KONQUI ERROR:
Traceback (most recent call last):
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 667, in
print_preamble
print_preamble_internal()
~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 658, in
print_preamble_internal
print_sentry_payload(thread)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 530, in
print_sentry_payload
payload = SentryEvent().make(program, thread)
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 443, in
make
stacktrace = SentryTrace(crash_thread, True).to_dict()
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 286, in
to_dict
SentryTrace.load_solib(self.thread, cramped_memory)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 248, in
load_solib
raise UnexpectedMappingException(f"No solib and no image found for frame
#{i} on thread {thread}! You could try with debug symbols downloading
enabled.")
UnexpectedMappingException: No solib and no image found for frame #28 on thread
<gdb.InferiorThread id=1.1 target-id="Thread 0x7f218b38d340 (LWP 3152)">! You
could try with debug symbols downloading enabled.
No solib and no image found for frame #28 on thread <gdb.InferiorThread id=1.1
target-id="Thread 0x7f218b38d340 (LWP 3152)">! You could try with debug symbols
downloading enabled.
Sentry is attempting to send 2 pending events
Waiting up to 30 seconds
Press Ctrl-C to quit
Debugging ended with exit code '1' and exit status 'NormalExit'
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2
Kernel Version: 7.2.11-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4670K CPU @ 3.40GHz
Memory: 24 GiB of RAM (23.0 GiB usable)
Graphics Processor: Intel® HD Graphics 4600
--
You are receiving this mail because:
You are watching all bug changes.
