https://bugs.kde.org/show_bug.cgi?id=491751
--- Comment #23 from xei...@proton.me ---
(In reply to Peter Leconte from comment #22)
> Could anyone confirm if setting your computer to sleep causes a freeze?
> I currently have worked around the issue by disabling anything that would
> cause my PC to go into sleep mode.
> This issue now also doesn't seem to occur anymore.
> However, if I manually set my PC to sleep it will immediately freeze. This
> might be a completely unrelated issue however.
Testing sleep mode on my end, I haven't been able to reproduce the freeze with
it. In my case, when the system is put to sleep manually with a single monitor,
it does so without issue, and resumes normally without freezing. When the
second monitor (graphics tablet) is connected, putting to PC to sleep appears
to work fine, but then on resume the second monitor does not receive input
signal and is not detected by the system. I suspect this is more to with with
how the tablet is connected though, as I have to use the Wacom Link adaptor for
it that splits and converts the combined output signal from a USB-C port into
HDMI and microUSB instead. Unfortunately I dont have any means of connecting it
directly from USB-C to USB-C as none of our machines support such connections,
though that is probably irrelevant given how niche such a setup would be in
regards to troubleshooting this bug. I have also tried only connecting it with
HDMI to have it treated as just a second display without input, however this
results in the same freezing unless input is connected separately first,
interestingly enough. Again, not as useful for those affected with standard
monitors.
As for sleep settings, I have setup the following setup manually:
- Using `nvidia-dkms`
- Enabled `nvidia-suspend.service`, `nvidia-hibernate.service`, and
`nvidia-resume.service` explicitly via `systemctl`
- Created `/etc/modprobe.d/nvidia-suspend-fix.conf` with settings
- `options nvidia NVreg_PreserveVideoMemoryAllocations=1`
Previously I avoided sleep mode entirely because it would often lead to issues
with my Nvidia card, however after looking up things on the ArchWiki, it
appears setting that kernel module option to preserve video memory now allows
it to work normally (at least, ignoring the problem with the tablet display not
resuming, but again I suspect that to be a more unique issue with how its
physically connected).
Notably though we're both on different GPUs, as your previous comment mentions
running on AMD in the specs. Would be interested in knowing if the freeze is
caused by sleep mode specifically on one or another, though in either case I
feel like that is probably a different issue that's just resulting int he same
graphics failure. If you wait a while while the screen is frozen (1-2 minutes),
and then try to move the mouse around, does the screen unfreeze for you at all?
I'm able to consistently recover from the freeze in my cases now by simply
waiting, though as mentioned the amount of time to wait is inconsistent.
Finally, a few other things I've tried, but to no avail:
- Changing to 200% scaling instead of previously 175% fractional scaling in
system settings
- Downgrading to `kwin 6.2.3`
Given 6.2.3 did not make any difference though and that package release was
roughly 3 weeks back, I don't imagine downgrading further will make a
difference, especially given others have been having this issue for much
longer. Will perhaps see about getting a journal from my Garuda install later
today though to see if anything is different in how its handling the extra
monitor being reconnected, or if suddenly the issue is reproducible there.
--
You are receiving this mail because:
You are watching all bug changes.
