| Summary: | Graphical corruption while playing games | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | skrubprime <skrubprime> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | duha.bugs, nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Crazy artifacting
More artifacting |
||
|
Description
skrubprime@gmail.com
2025-03-31 02:41:51 UTC
Created attachment 179879 [details]
More artifacting
Ok so this is something new. I restarted after posting that report and now my desktop environment will go completely black for a half second, then reload, do it again, and then stay completely black the third time it goes away and doesn't come back. I was able to do some things before I lose the DE, but then I just restart the computer and this cycle repeats. On one of these restarts I was able to do another journalctl: journalctl -f | grep --line-buffered kde Journal file /var/log/journal/36f9b26c1893423586550454d07d0005/user-1000@000630468afb6240-7e3da53e8f462bee.journal~ is truncated, ignoring file. Mar 30 22:57:19 dino-nobara systemd[1]: dbus-:1.3-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully. Mar 30 22:57:19 dino-nobara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=dbus-:1.3-org.kde.powerdevil.discretegpuhelper@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 30 22:57:19 dino-nobara systemd[1]: dbus-:1.3-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully. Mar 30 22:57:19 dino-nobara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=dbus-:1.3-org.kde.powerdevil.chargethresholdhelper@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 30 22:57:19 dino-nobara systemd[1]: dbus-:1.3-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully. Mar 30 22:57:19 dino-nobara audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=dbus-:1.3-org.kde.powerdevil.backlighthelper@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Module libtimerplugin.so from rpm kdeplasma-addons-6.3.3-1.fc41.x86_64 Module libdictplugin.so from rpm kdeplasma-addons-6.3.3-1.fc41.x86_64 Module libKF6CalendarEvents.so.6 from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module libkdeconnectcore.so.24 from rpm kde-connect-24.12.3-1.fc41.x86_64 Module libkdeconnectdeclarativeplugin.so from rpm kde-connect-24.12.3-1.fc41.x86_64 Module liborg_kde_desktop_private.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module liborg_kde_desktop.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module libdraganddropplugin.so from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module libkquickcontrolsaddonsplugin.so from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module org.kde.desktop.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module liborg_kde_plasmacomponents3.so from rpm libplasma-6.3.3-1.fc41.x86_64 Module org.kde.plasma.vault.so from rpm plasma-vault-6.3.3-1.fc41.x86_64 Module org.kde.plasma.notifications.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.kscreen.so from rpm kscreen-6.3.3-1.fc41.x86_64 Module org.kde.plasma.private.systemtray.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.plasma.systemtray.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.contextmenu.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Mar 30 22:57:21 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth": file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9 Mar 30 22:57:21 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth": file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9 Mar 30 22:57:22 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/nobara-app-menu-icon Mar 30 22:57:22 dino-nobara plasmashell[6038]: kf.coreaddons: "Could not find plugin plasma5support/dataengine/plasma_engine_org.kde.plasma.clipboard" Mar 30 22:57:22 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:310:13: QML Image: Cannot open: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/nobara-app-menu-icon Mar 30 22:57:22 dino-nobara plasmashell[6038]: org.kde.plasma.taskmanager: Failed to find service for Unity Launcher "application://discord.desktop" Mar 30 22:57:22 dino-nobara plasmashell[6038]: org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement" Mar 30 22:57:22 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.plasma.timer/contents/ui/CompactRepresentation.qml:224:17: Unable to assign [undefined] to QString Mar 30 22:57:22 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.plasma.timer/contents/ui/CompactRepresentation.qml:223:17: Unable to assign [undefined] to QString Mar 30 22:57:24 dino-nobara plasmashell[6038]: file:///usr/share/plasma/plasmoids/org.kde.plasma.timer/contents/ui/TimerView.qml:18: TypeError: Cannot read property 'width' of undefined Mar 30 22:57:25 dino-nobara kded6[3057]: org.kde.colorcorrectlocationupdater: Geolocator stopped Module libtimerplugin.so from rpm kdeplasma-addons-6.3.3-1.fc41.x86_64 Module libdictplugin.so from rpm kdeplasma-addons-6.3.3-1.fc41.x86_64 Module libKF6CalendarEvents.so.6 from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module libkdeconnectcore.so.24 from rpm kde-connect-24.12.3-1.fc41.x86_64 Module libkdeconnectdeclarativeplugin.so from rpm kde-connect-24.12.3-1.fc41.x86_64 Module liborg_kde_desktop_private.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module liborg_kde_desktop.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module libdraganddropplugin.so from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module libkquickcontrolsaddonsplugin.so from rpm kf6-kdeclarative-6.12.0-1.fc41.x86_64 Module org.kde.desktop.so from rpm kf6-qqc2-desktop-style-6.12.0-1.fc41.x86_64 Module liborg_kde_plasmacomponents3.so from rpm libplasma-6.3.3-1.fc41.x86_64 Module org.kde.plasma.vault.so from rpm plasma-vault-6.3.3-1.fc41.x86_64 Module org.kde.plasma.notifications.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.kscreen.so from rpm kscreen-6.3.3-1.fc41.x86_64 Module org.kde.plasma.private.systemtray.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.plasma.systemtray.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Module org.kde.contextmenu.so from rpm plasma-workspace-6.3.3-1.fc41.x86_64 Mar 30 22:58:14 dino-nobara plasma_waitforname[5364]: org.kde.plasma.waitforname: WaitForName: Service was not registered within timeout Mar 30 22:58:14 dino-nobara systemd[2517]: dbus-:1.2-org.kde.KSplash@1.service: Main process exited, code=exited, status=1/FAILURE Mar 30 22:58:14 dino-nobara systemd[2517]: dbus-:1.2-org.kde.KSplash@1.service: Failed with result 'exit-code'. Not really sure what to do anymore. Didn't expect this to happen after restarting. Maybe my desktop environment is corrupt or something. Guess I gotta reinstall the OS This sounds like graphical corruption, not actual crashing. Crashing is when an app unexpectedly stops running. Moving to KWin where hopefully someone can help debug it. What kind of GPU hardware are you using? That sequence of events sound a lot like a GPU reset, and the image and "X connection to :0 broken (explicit kill or server shutdown)" matches too.
You can check with
> sudo dmesg
after it happens (or journalctl -k --boot -1 a reboot afterwards) to make sure, amdgpu prints about starting and completing the reset. If you can see artifacts afterwards, it probably doesn't reset successfully though.
If you're using shaders in Minecraft, try disabling them... they don't always use the most well behaved OpenGL code (to put it very nicely).
(In reply to Nate Graham from comment #3) > This sounds like graphical corruption, not actual crashing. Crashing is when > an app unexpectedly stops running. Moving to KWin where hopefully someone > can help debug it. > > What kind of GPU hardware are you using? Sorry for the late reply guys, I had a lot going on. The issue was happening on both my 6700 XT and 6600, but it seems that I might have fixed the issue. I think it might have been my CoreCtrl profile that was creating instability and making plasmashell crash. I still don't understand the part where the entire desktop environment goes black and becomes really hard to use after it crashed a few more times, even after turning off the profile and disabling the overdrive in grub. It was completely broken. But if not overclocking the vram to stop it from crashing is what fixes that, then that's what it is But I'm gonna wait a few more days and see if I still have issues to see if this is what really fixed it. Will report back later. So far though, seems to be fine now. Just need to see if I spoke too soon 😭 😭 (In reply to Zamundaaa from comment #4) > That sequence of events sound a lot like a GPU reset, and the image and "X > connection to :0 broken (explicit kill or server shutdown)" matches too. > > You can check with > > sudo dmesg > after it happens (or journalctl -k --boot -1 a reboot afterwards) to make > sure, amdgpu prints about starting and completing the reset. If you can see > artifacts afterwards, it probably doesn't reset successfully though. > > If you're using shaders in Minecraft, try disabling them... they don't > always use the most well behaved OpenGL code (to put it very nicely). Yeah seems that shaders can cause problems. I was using complementary on CachyOS with kde and it was just not working out. Then I switched to bsl and had no issues until over time I had the same timeouts, and then I realized that the vram oc I had was creating instability. Now I am back on nobara without that dreaded overclock and have no issues for now. But I really do think this is more so the vram because it was also resetting the same way on other games. The reason I thought that it was minecraft at first was because it was the only game causing these timeouts, but I think I didn't give it enough time on other games to make the best conclusion. I realized I was being stubborn because on Windows I was able to push my vram to the highest amd adrenalin would let me set it (+150mhz) and have no problems, so I genuinely thought that the more conservative overclock I had on linux was fine. But I guess the behavior is different on here and I just thought I could have the same clocks and be fine. What I did now was change my power profile + reset vram clocks and that is somehow giving the same performance, even though the vram clock is at stock speeds. So far I have no issues but I am gonna give it more time to confirm this To elaborate on this black screen thing, seems like other people have this issue too but it is pretty uncommon, where kde will go completely black until rebooting: https://discuss.kde.org/t/black-screen-when-turning-on-a-second-monitor/26948 Not sure what triggered it for these other guys with a second monitor, but this strange behavior happens to me after a gpu reset. The gpu reset is on me. I guess maybe the gpu driver is not as stable for undervolting compared to windows or something, because even a less aggressive setting would still be unstable. I increased the offset even more now so that shouldn't be an issue anymore But I found a fix for this black screen behavior. You can just use one monitor which would suck, or do a fresh reinstall which I do not recommend, but the one that fixes it without a bunch of hassle is just deleting the two files in .config found on this solution here: https://discuss.kde.org/t/reset-all-plasma-settings-at-once-and-start-tiling-feature-on-command-line/9503 This resets plasma settings and after doing this I have no issues. Another thing is apparently setting the monitor color to prefer accuracy instead of efficiency could create the grounds for this to form. Some people fixed their issue by changing that but it didn't work for me. But I don't notice a difference between the two settings anyway so I will just use the default efficiency setting. I also deleted kwinoutputconfig.json in .config just to be sure, since that has the monitor information. Hopefully I do not encounter this again 💀💀 (In reply to skrubprime@gmail.com from comment #7) > Hopefully I do not encounter this again 💀💀 I didn't get the black desktop environment again. I found the root cause, which is setting the monitor color accuracy in the display settings to prefer accuracy over efficiency, which is not the default setting. The default setting is to prefer efficiency and that fixes this weird issue. I also don't notice a difference between the two settings anyway. I'm gonna mark this resolved |