[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #16 from Francisco González --- (In reply to Zamundaaa from comment #15) > Do the DPMS issues still happen with released Plasma 6? They seem gone! Although some versions ago, when the screen went off by timeout, some garbage was displayed, but moving the mouse was enough to "clean" that. I'mma keep you updated if it happens again, but for now seems fixed. Thank you for your work <3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #13 from Francisco González --- Oh, by the way I'm testing KDE 6 from source, built with kdesrc-build from branch master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Francisco González --- Hi. I've noticed that this issue is partially solved, because the commit only fixes TTY switching, but not when the computer is powered on after sleep, or when the screen powers off due to the energy management timeout. It's not the same kind of corruption though, since the glitches involve one of my screens not turning on, and the other one refreshing at a very low rate (like 2-5 fps). I'm not sure if this is the same bug, but in case it isn't, please close this report and tell me if you need me to file it as another bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473575] New: Avoid sleep while flushing cache to removable drive
https://bugs.kde.org/show_bug.cgi?id=473575 Bug ID: 473575 Summary: Avoid sleep while flushing cache to removable drive Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fgonzalez.n...@gmail.com Target Milestone: --- Today I was copying an ISO image to a Ventoy-enabled USB drive (exfat). It seems that the file transfer was cached by default, so the file transfer dialog was closed after the file was cached. After clicking the secure-remove button, Plasma showed me the message to not unplug the device until the flush was done. After 10 minutes (by setting) my computer went to sleep, and after resuming the flush message was still showing. It would mean that the flush might not finish prior to sleep. It would be nice to have a feature to disable sleep while a cached file transfer is still being done since file corruption might happen. STEPS TO REPRODUCE 1. Transfer a file to a device with write cache enabled. 2. Wait for the computer to sleep (make sure to set an appropriate time threshold so the sleep can occur while the flush is still going). 3. Resume the computer and check the flush dialog and/or file corruption. OBSERVED RESULT The computer goes to sleep but after resuming, the cache flush is still ongoing. EXPECTED RESULT The computer goes to sleep only after the cache flush has ended. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, 6.4.11-arch2-1 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Running on Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #9 from Francisco González --- Also, running sudo journalctl -b 0 --grep drm sometimes shows a flooded journal with a "Page flip failed" error that said that there was no space left on device (IIRC). Can't remember in which case did it happen, but it seems it was when I was using the "radeon" module rather than "amdgpu". If it happens again, I'll post that output here. BTW, the screen corruption shows up with any of those modules. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #8 from Francisco González --- Some observations: - About the screen mode changes on TTY switch, the screen frequency regression to 60 Hz is noticeable but is not informed by KScreen, which shows 75 Hz. - Even though I'm not an expert on this, it seems that the lack of DRM_CLIENT_CAP_ATOMIC support on my graphics card and some problem with KWin handling that, might be the cause of the screen corruption. - In the duplicated bug referenced before, the user has a Radeon HD 6310, which seems to be pre-GCN (one gen before my GPU). That could mean that this bug might be replicable with HD 7000 series GPUs or older. - Running drm_info on my laptop (Intel UHD Graphics 620) shows support for DRM_CLIENT_CAP_ATOMIC, and there are no artifacts at all. PS: somehow, got baited into this 2016 article that might be related to this issue. VT Switching with Atomic Modeset. https://blog.ffwll.ch/2016/01/vt-switching-with-atomic-modeset.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #7 from Francisco González --- Created attachment 158955 --> https://bugs.kde.org/attachment.cgi?id=158955=edit Output before switching to TTY (drm_info) Sorry, had uploaded the wrong file before. Note that on line 5, says "DRM_CLIENT_CAP_ATOMIC not supported". Also, on line 166, mode is "1920x1080@74.97 driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Attachment #158953|0 |1 is obsolete|| --- Comment #6 from Francisco González --- Comment on attachment 158953 --> https://bugs.kde.org/attachment.cgi?id=158953 Output before switching to TTY (drm_info) >may 14 18:49:04 MSI-DESKTOP systemd[670]: Starting KDE Window Manager... >may 14 18:49:04 MSI-DESKTOP systemd[670]: Started KDE Window Manager. >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: No backend specified, >automatically choosing drm >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: kwin_wayland_drm: >drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU >"/dev/dri/card0" >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL vendor string: >AMD >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL renderer string: >AMD Radeon HD 7700 Series (verde, LLVM 15.0.7, DRM 3.52, 6.3.1-arch1-1) >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL version string: >4.6 (Core Profile) Mesa 23.0.3 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL shading language version >string: 4.60 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Driver: >Unknown >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GPU class: >Unknown >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: OpenGL version: >4.6 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GLSL version: >4.60 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Mesa version: >23.0.3 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Linux kernel version: >6.3.1 >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Requires strict binding: >no >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: GLSL shaders: >yes >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Texture NPOT support: >yes >may 14 18:49:04 MSI-DESKTOP kwin_wayland[711]: Virtual Machine: >no >may 14 18:49:05 MSI-DESKTOP kwin_wayland[711]: kwin_xkbcommon: XKB: >inet:323:58: unrecognized keysym "XF86EmojiPicker" >may 14 18:49:05 MSI-DESKTOP kwin_wayland[711]: kwin_xkbcommon: XKB: >inet:324:58: unrecognized keysym "XF86Dictate" >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: (WW) Option "-listen" >for file descriptors is deprecated >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: Please use "-listenfd" >instead. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: (WW) Option "-listen" >for file descriptors is deprecated >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[786]: Please use "-listenfd" >instead. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: The XKEYBOARD keymap >compiler (xkbcomp) reports: >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: > Warning: >Unsupported maximum keycode 708, clipping. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: > X11 >cannot support keycodes above 255. >may 14 18:49:05 MSI-DESKTOP kwin_wayland_wrapper[808]: Errors from xkbcomp are >not fatal to the X server -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #5 from Francisco González --- Created attachment 158954 --> https://bugs.kde.org/attachment.cgi?id=158954=edit Output after switching back from TTY (drm_info) Same deal with "DRM_CLIENT_CAP_ATOMIC not supported", but this time in line 166, mode was reverted to default "Mode: 1920x1080@60.00 preferred driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added Attachment #158953|Output before switching |Output before switching to description|back to TTY (drm_info) |TTY (drm_info) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #4 from Francisco González --- Created attachment 158953 --> https://bugs.kde.org/attachment.cgi?id=158953=edit Output before switching back to TTY (drm_info) Note that on line 5, says "DRM_CLIENT_CAP_ATOMIC not supported". Also, on line 166, mode is "1920x1080@74.97 driver phsync pvsync" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 --- Comment #3 from Francisco González --- Created attachment 158952 --> https://bugs.kde.org/attachment.cgi?id=158952=edit Output after switching back from TTY (journalctl --user-unit plasma-kwin_wayland.service --boot 0) This output was obtained after running journalctl, while the screen was corrupted, via SSH with my laptop. There is no difference in journalctl output from before and after switching to TTY (checked with diff). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469280] Screen corruption after switching back from TTY and after coming back from sleep.
https://bugs.kde.org/show_bug.cgi?id=469280 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469443] Broken graphics after waking up from sleep on Wayland session
https://bugs.kde.org/show_bug.cgi?id=469443 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com --- Comment #1 from Francisco González --- It sounds like a duplicate of mine (https://bugs.kde.org/show_bug.cgi?id=469280) Which AMD GPU do you have? Does the bug happen if you switch to a TTY and then switch back to the GUI? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 Francisco González changed: What|Removed |Added CC||fgonzalez.n...@gmail.com --- Comment #11 from Francisco González --- (In reply to WojtasJD from comment #10) > I have similar issue with corrupted screen ( > https://bugsfiles.kde.org/attachment.cgi?id=149347 ) in: > - openSUSE 15.4, kernel 5.14.x and KDE Plasma 5.24.4 (installed on disk) > - neon-user-20230420-0722.iso (kernel 5.19; KDE Plasma 5.27.4 ; with user > "neon" logged out from X11 and logged in to Wayland live session) > > I have AMD Radeon HD 6570 (GPU name: TURKS, generation: Northern Islands) - > with radeon driver; amdgpu does not support this card. > > In my case I don't need to suspend the machine, it is enough to switch from > TTY1...6 (text login prompt) to TTY8 (Plasma) and screen is corrupted (with > good mouse cursor). > To 'repair' this I need to switch to TTY7 (SDDM) and back to TTY8 (Plasma). > After repair, again switching to TTY1...6 (but not TTY7 (SDDM)) and back to > TTY8 (Plasma) - screen is distorted (with good mouse cursor)... > > Same behavior with KDE neon (TTY numbers different). Got a HD 7750 (VERDE, Southern Islands). In my system, the screen corruption appears with both of them radeon and amdgpu, in the same fashion and equally work-aroundable as yours. At this point, I'm unsure if this is a GPU driver bug, from KDE or even Wayland, since this doesn't happen in GNOME (Wayland). Maybe they implemented some way to switch back from TTY without screen artifacts. By the way, this corruption doesn't occur on XOrg. -- You are receiving this mail because: You are watching all bug changes.
