https://bugs.kde.org/show_bug.cgi?id=491751
xei...@proton.me changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xei...@proton.me
--- Comment #21 from xei...@proton.me ---
Created attachment 176309
--> https://bugs.kde.org/attachment.cgi?id=176309&action=edit
`journalctl -b` ouput after freeze, plus info after unfreezing
I think I've also been experiencing this same issue. As mxr576 mentions above,
this does seem to also be related to monitor setup changes. In my case, I'm
connecting my Wacom graphics tablet to my desktop to draw with, but
occasionally I'll run into bug 493027 after periods of inactivity. While the
workaround that was merged avoids the segfault for that issue, I still have to
reconnect my tablet in order to restore proper input functionality for it.
This was working fine on a Garuda Linux install, but recently I migrated my
system to a new Arch Linux setup instead. Since then, reconnecting my tablet to
try and restore input instead causes this full graphics freeze. Interestingly,
it appears that the system is able to recover and unfreeze after an some amount
of time if the graphics tablet is disconnected again (sometimes it does so
quickly, sometimes it takes a minute or so). However, I just now found that if
I first connect the tablet for input only (USB), and then after for display
(HDMI), then this can avoid the freeze and allow it to reconnect normally
again, however this still causes other apps such as Dolphin file explorer,
kwallet, Telegram, and so on to crash. Obviously this is not so helpful of a
workaround for most users, but it feels worth noting.
Additionally, I have had this issue occur on Arch regardless of using `linux`
or `linux-zen` kernels, and `nvidia` or `nvidia-dkms` respectively. Still
trying to troubleshoot things to see if there's any more information that can
be gained, as I'm especially curious why I haven't seen this happen under my
Garuda install, but does under Arch (unless there was some update to kwin
within the last week or so that potentially introduced the bug that I just
wasn't aware of due to migrating). I moved my system over just a couple days
ago, but still have the previous one setup on a separate SSD, so I could try
testing things further and see if that produces anything noteworthy in the
journal for comparison.
Also possibly related: bug 486460
However in my case HDR is disabled, and I'm not encountering any black screens.
In the meantime, I've added my journal of the issue occurring on Arch to the
attachments as well.
Journal summary:
- The wall of "GL_FRAMEBUFFER" errors occurs from line 6088 to 17024, at which
point the system recovered from the freeze.
- Then again in troubleshooting once more, another wall of errors from 17875 to
28773, where it recovers again.
- After that point, I then attempt the workaround of connecting the tablet as
input first, then display, which causes the multiple application crashes that
are caught by the system.
- The end state is graphics remaining unfrozen and system functioning normally
(as far as I can tell).
I can also provide coredumps from the affected applications if that would help
at all, though I feel those are mainly side effects of the actual issue.
---
Operating System: Arch Linux
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.12.1-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2
--
You are receiving this mail because:
You are watching all bug changes.
