[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #66 from Victor Ryzhykh --- (In reply to Nate Graham from comment #63) > It's quite possible there are still bugs, or the hooks are interfering with > some other distro-provided or user-initiated setting. > > Hassles like this are why I personally avoid NVIDIA hardware, FWIW. I had my first laptop with ati radeon. I was disappointed in it when the manufacturer's support quickly ended. In 2010, I gave it to my son. Since then, I have had six more laptops. All with an nvidia video card. And now I have my third desktop computer, and all were with an nvidia video card. This is the best video card. And it has no problems with kde. There has never been and never will be a stronger fan of kde than me. And I am just an amateur, not a crazy fan, of nvida. They work great together for me. There are nuances, but I hope they can be solved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #65 from Fotios Valasiadis --- (In reply to Victor Ryzhykh from comment #64) > Created attachment 173326 [details] > My file for correct work of exit from sleep mode > > (In reply to Fotios Valasiadis from comment #62 > > Back to debugging I guess. > For me, it turned out to be a revelation that for Wayland, to exit sleep > mode, each necessary kernel module needs to be entered into the file > /etc/dracut.conf.d/10-nvidia.conf > So far, only VirtualBox modules have not been added there. > I had to add network modules so that after waking up from sleep mode, the > network would start working. > After a long period of sleep, the network could not connect. > On kernel 6.10.X, these network modules are already in the kernel, > so I removed the last two lines from the file > /etc/dracut.conf.d/10-nvidia.conf Fedora works OOTB on wayland on that PC with a 1050 Ti so yeah the issue is definitely solvable. I (gladly) don't use said PC anymore though, and linux on it was a pain for more than that. Nvidia not supporting VRAM spilling onto system RAM made it unusable even for 1080p couch gaming at 60 fps. Dual boot windows it is to play games that work perfectly fine with proton, sadge. But I am thinking I will still look into solving this issue in void linux because I don't value my time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #64 from Victor Ryzhykh --- Created attachment 173326 --> https://bugs.kde.org/attachment.cgi?id=173326&action=edit My file for correct work of exit from sleep mode (In reply to Fotios Valasiadis from comment #62 > Back to debugging I guess. For me, it turned out to be a revelation that for Wayland, to exit sleep mode, each necessary kernel module needs to be entered into the file /etc/dracut.conf.d/10-nvidia.conf So far, only VirtualBox modules have not been added there. I had to add network modules so that after waking up from sleep mode, the network would start working. After a long period of sleep, the network could not connect. On kernel 6.10.X, these network modules are already in the kernel, so I removed the last two lines from the file /etc/dracut.conf.d/10-nvidia.conf -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #63 from Nate Graham --- It's quite possible there are still bugs, or the hooks are interfering with some other distro-provided or user-initiated setting. Hassles like this are why I personally avoid NVIDIA hardware, FWIW. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #62 from Fotios Valasiadis --- (In reply to Nate Graham from comment #61) > Thanks everyone. So I brought this to the attention of a KWin developer who > brought it to the attention of an NVIDIA developer. > > The conclusion here is that NVreg_PreserveVideoMemoryAllocations=1 is not a > workaround, and *should be* used. The only reason it's not turned on by > default is because if it's turned on without the appropriate pre-suspend > hooks in place, suspend will get broken. NVIDIA distributed systemd unit > files for these hooks, but they don't trust distros and users to install and > activate them, and of course those using non-systemd distros will have to > figure something else out as well. So they leave it off by default to avoid > having to handle those cases. > > This information has been added to > https://community.kde.org/Distributions/ > Packaging_Recommendations#Proprietary_NVidia_driver_configuration, and I've > emailed distros about it. > > So from a KDE perspective this is basically a downstream/distro issue at > this point. I encourage everyone to go contact their distros about it as > well, and ideally submit patches if you're a distro packager or like to play > one on TV. Honestly, replicating the exact same systemd scripts you mention to get suspend working on runit did not work for me. Looking online I found other users experiencing the same exact problem when enabling NVreg_PreserveVideoMemoryAllocations=1 even on systemd distros using the exact same setup. Back to debugging I guess. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #61 from Nate Graham --- Thanks everyone. So I brought this to the attention of a KWin developer who brought it to the attention of an NVIDIA developer. The conclusion here is that NVreg_PreserveVideoMemoryAllocations=1 is not a workaround, and *should be* used. The only reason it's not turned on by default is because if it's turned on without the appropriate pre-suspend hooks in place, suspend will get broken. NVIDIA distributed systemd unit files for these hooks, but they don't trust distros and users to install and activate them, and of course those using non-systemd distros will have to figure something else out as well. So they leave it off by default to avoid having to handle those cases. This information has been added to https://community.kde.org/Distributions/Packaging_Recommendations#Proprietary_NVidia_driver_configuration, and I've emailed distros about it. So from a KDE perspective this is basically a downstream/distro issue at this point. I encourage everyone to go contact their distros about it as well, and ideally submit patches if you're a distro packager or like to play one on TV. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #60 from Victor Ryzhykh --- (In reply to Ilya Bizyaev from comment #57) > To me, it sounds like the “fix” above basically boils down to > NVreg_PreserveVideoMemoryAllocations=1, which is a well-known workaround: > https://wiki.archlinux.org/title/NVIDIA/ > Tips_and_tricks#Preserve_video_memory_after_suspend > > It basically saves the entire video memory to RAM or disk, then restores it. > I could be wrong, but I don't think requiring users to enable a hack is a > proper fix. I will return to this issue again. Before the latest changes to my configs, I periodically encountered problems after exiting sleep mode. This only happened when the dracut command was run after installing the nvidia kernel modules. If the dracut command was not executed after installing kernel modules, then I had no problems after waking up from sleep mode. Recently, after getting another error when waking up from sleep, I sent the log file to the nvidia developers, in this message https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/241?u=victorr2007 I got a reply a few days later in this message https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/262?u=victorr2007 It turned out that file /etc/modprobe.d/nvidia-power-management.conf was ignored in the wayland session. Then I decided to add a record about this file to file /etc/dracut.conf.d/10-nvidia560.conf, where I had previously added other configuration files for use. It turned out to be the right decision. Now everything works perfectly for me. I'm not sure that kde can restore video memory on its own when exiting sleep mode. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #59 from Victor Ryzhykh --- (In reply to Ilya Bizyaev from comment #57) > To me, it sounds like the “fix” above basically boils down to > NVreg_PreserveVideoMemoryAllocations=1, which is a well-known workaround: > https://wiki.archlinux.org/title/NVIDIA/ > Tips_and_tricks#Preserve_video_memory_after_suspend > > It basically saves the entire video memory to RAM or disk, then restores it. > I could be wrong, but I don't think requiring users to enable a hack is a > proper fix. The fact is that Nvidia is on Wayland does not directly use files from /etc/modprobe.d/ Also Nvidia on Wayland does not use file /etc/X11/xorg.conf.d/nvidia.conf Will boot and work on Wayland, even if there is no file on the system /etc/X11/xorg.conf.d/nvidia.conf It just won't be possible to start session x11. All these files are used only in session x11. Because of this, parameter NVreg_PreserveVideoMemoryAllocations=1, is not taken into account when entering sleep mode. For a Wiland session, configs for Nvidia must either be written into the kernel parameters via file /etc/default/grub, or written to the kernel initrd using draсut in file /etc/dracut.conf.d/10-nvidia.conf. I make myself an nvidia package without using file /etc/default/grub for configuration, and only file /etc/dracut.conf.d/10-nvidia.conf is used for configuration. Everything works fine for me, both X11 and Wayland. I make this nvidia package https://abf.rosalinux.ru/x11_backports/nvidia560 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #58 from Fotios Valasiadis --- Additionally, said hack doesn't work for everyone, and even Nvidia themselves marked this as experimental without a change of status for quite some time. Personally, after trying that fix in my void Linux install(had to recreate the systemd scripts on runit), suspend would no longer work at all and my fans would start spinning at full capacity. Searching online I found other users experiencing the exact same issue after employing this hack. Wayland worked fine on KDE 5 with the exact same setup btw. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Ilya Bizyaev changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #57 from Ilya Bizyaev --- To me, it sounds like the “fix” above basically boils down to NVreg_PreserveVideoMemoryAllocations=1, which is a well-known workaround: https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend It basically saves the entire video memory to RAM or disk, then restores it. I could be wrong, but I don't think requiring users to enable a hack is a proper fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #56 from Nate Graham --- Great, sounds like it was a series of NVIDIA driver and configuration issues. Ethan, are you able to resolve these issues as well by following those steps? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #55 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #51) > Previously, I couldn’t understand why the sleep mode works and then stops > working. I figured out what the problem was. Nvidia developers helped. Now waking up from sleep mode on Nvidia drivers in a wayland session always works correctly for me. There are no glitches or image artifacts. Here about my settings for the nvidia560 driver. https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/265?u=victorr2007 I added the path to the /etc/modprobe.d/nvidia-power-management.conf file to the /etc/dracut.conf.d/10-nvidia.conf file The new file /etc/dracut.conf.d/10-nvidia560.conf now looks like this add_drivers+=" nvidia nvidia-drm nvidia-modeset nvidia-uvm " install_optional_items+=" /etc/modprobe.d/nvidia-power-management.conf " install_optional_items+=" /etc/modprobe.d/nvidia560-blacklist-nouveau.conf " install_optional_items+=" /etc/modprobe.d/nvidia560-wayland.conf " Contents of the /etc/modprobe.d/nvidia-power-management.conf file "options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp" Contents of the /etc/modprobe.d/nvidia560-blacklist-nouveau.conf file "blacklist nouveau" Contents of the /etc/modprobe.d/nvidia560-wayland.conf file "options nvidia_drm modeset=1 fbdev=1" Now exiting sleep mode occurs without errors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Serge Droz changed: What|Removed |Added CC||se...@drozilla.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Niels changed: What|Removed |Added CC||nvaert1...@hotmail.com --- Comment #54 from Niels --- (In reply to Michael from comment #53) > (In reply to Fushan Wen from comment #52) > > I can confirm the latest kernel fixed the bug for amdgpu. > I have still this issue on >Operating System: Manjaro Linux >KDE Plasma Version: 6.0.5 >KDE Frameworks Version: 6.4.0 >Qt Version: 6.7.2 >Kernel Version: 6.6.41-1-MANJARO (64-bit) >Graphics Platform: X11 >Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics >Graphics Processor: AMD Radeon Graphics > @Fushan Wen: What did you mean with "latest kernel"? I'd appreciate if > someone would add [AMD] again to the summary. He's either referring to kernel 6.9.12 or 6.10.2 or higher or 6.6.43 or higher, depending on whether he's running a current or LTS kernel. You're on the LTS kernel. You could try using a more recent kernel or updating to the latest LTS kernel to see if it resolves the issue for you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #53 from Michael --- (In reply to Fushan Wen from comment #52) > I can confirm the latest kernel fixed the bug for amdgpu. I have still this issue on Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.41-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Graphics Processor: AMD Radeon Graphics @Fushan Wen: What did you mean with "latest kernel"? I'd appreciate if someone would add [AMD] again to the summary. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Fushan Wen changed: What|Removed |Added Summary|[AMD, NVIDIA] kwin on |[NVIDIA] kwin on Wayland |Wayland black screen with |black screen with cursor |cursor after most |after most resume-from-RAM |resume-from-RAM | --- Comment #52 from Fushan Wen --- I can confirm the latest kernel fixed the bug for amdgpu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #38 from postix --- (In reply to Fushan Wen from comment #37) > Can also sometimes reproduce on AMDGPU, so it seems not NVIDIA only. Me too on Fedora 40, Plasma 6.0.5, Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #37 from Fushan Wen --- Can also sometimes reproduce on AMDGPU, so it seems not NVIDIA only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Fotios Valasiadis changed: What|Removed |Added CC||fvalas...@gmail.com --- Comment #36 from Fotios Valasiadis --- Hello, I am also experiencing the graphical glitches after resume from suspend. plasmashell --replace is mandatory to get the system working again. KDE 6.0.4 Nvidia GTX 1050 Ti 555.42.2 drivers but noticed this bug in the stable version of the driver 550.78 too! Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 vilim changed: What|Removed |Added CC||onl...@vil.im --- Comment #35 from vilim --- I am also experiencing a version of this bug, after wakeup there are parts of the screen flickering, certain apps (like the system monitor) have 90% of text missing. KDE 6.0.4 Wayland NVIDIA GeForce RTX 3080 550.78 drivers -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 oso changed: What|Removed |Added Flags||performance+, Wayland+, ||X11+, Catalyst+, dpi+, ||Gallium3D+, Intel+, Mesa+, ||nouveau+, NVIDIA+, r300g+, ||r600g+, Decision-Required+, ||Triaged+, ReviewRequest+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 oso changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=448866, | |https://bugs.kde.org/show_b | |ug.cgi?id=475605, | |https://bugs.kde.org/show_b | |ug.cgi?id=476563, | |https://bugs.kde.org/show_b | |ug.cgi?id=478090, | |https://bugs.kde.org/show_b | |ug.cgi?id=478231| CC||osobuko...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 nilskemail+...@gmail.com changed: What|Removed |Added CC||nilskemail+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Marco Schmidlin changed: What|Removed |Added CC||ner...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #34 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #32) > When I used drivers 545, I had no crashes after exiting sleep mode, but > after switching to drivers 550, problems appeared. Although it is possible > that the transition to new drivers simply coincided with some other change. Oops. I have now reinstalled the system. The system exits sleep mode on the 550 drivers, on wayland, without errors. Apparently the old system had accumulated errors from constant testing of different versions of the compiled packages for KDE6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #33 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #32) > (In reply to Victor Ryzhykh from comment #17) > > Nvidia 545 driver is used. > When I used drivers 545, I had no crashes after exiting sleep mode, but > after switching to drivers 550, problems appeared. Although it is possible > that the transition to new drivers simply coincided with some other change. Operating System: ROSA Fresh Desktop 2023.1 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-generic-1rosa2023.1-x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.5 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B250M-D3H -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #32 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #17) > Nvidia 545 driver is used. When I used drivers 545, I had no crashes after exiting sleep mode, but after switching to drivers 550, problems appeared. Although it is possible that the transition to new drivers simply coincided with some other change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Alper Şal changed: What|Removed |Added CC|alpersal...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #31 from stefan...@posteo.de --- Created attachment 167313 --> https://bugs.kde.org/attachment.cgi?id=167313&action=edit glitches -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #30 from stefan...@posteo.de --- Created attachment 167312 --> https://bugs.kde.org/attachment.cgi?id=167312&action=edit journcal ctl logs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 stefan...@posteo.de changed: What|Removed |Added CC||stefan...@posteo.de --- Comment #29 from stefan...@posteo.de --- Created attachment 167311 --> https://bugs.kde.org/attachment.cgi?id=167311&action=edit dmesg logs Not sure, if this is related, but after hibernate and waking up, I see so much glichtes and artefacts, that the desktop gets unusable such that I have to restart the desktop. Distribution: KDE Neon Desktop: KDE Plasma 6.0.2 Qt Version: 6.6.2 Graphics Platform: Wayland Graphics Card: NVIDIA GTX 1060 NVIDIA Driver Version: 535.161.07 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 cow70...@omeie.com changed: What|Removed |Added CC||cow70...@omeie.com --- Comment #28 from cow70...@omeie.com --- Same issue. It happens any time going idle, or closing laptop lid. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: LENOVO Product Name: 20NF0018US System Version: ThinkPad E595 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Dashon changed: What|Removed |Added CC||dashonww...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Alper Şal changed: What|Removed |Added CC||alpersal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 rodolfosil...@tutanota.com changed: What|Removed |Added Blocks||482772 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=482772 [Bug 482772] kwin on X11 Intel Graphics black screen with cursor sometimes after screenlocks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #27 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #26) > But if we talk about kde6, it is very good. Today this is the best of the > kde6 for me. Working on kde6 is very convenient. It’s a shame that I have to > go back to kde5. I hope this doesn't last very long. > P.S. > In the distribution, the main one is KDE5, and I cannot compile them so that > they can be installed simultaneously with KDE6. I'm sorry. Accidentally wrote in the wrong bar. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #26 from Victor Ryzhykh --- But if we talk about kde6, it is very good. Today this is the best of the kde6 for me. Working on kde6 is very convenient. It’s a shame that I have to go back to kde5. I hope this doesn't last very long. P.S. In the distribution, the main one is KDE5, and I cannot compile them so that they can be installed simultaneously with KDE6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #25 from Victor Ryzhykh --- Created attachment 166095 --> https://bugs.kde.org/attachment.cgi?id=166095&action=edit Nvidia build config (In reply to Victor Ryzhykh from comment #23) > When idle, the computer goes into sleep mode, as configured in the energy > saving settings. All previously running applications continue to run after > waking up. The nvidia driver is compiled using the following configs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #24 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #23) > When idle, the computer goes into sleep mode, as configured in the energy > saving settings. All previously running applications continue to run after > waking up. The nvidia driver is compiled using the following configs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #23 from Victor Ryzhykh --- Build version 6.0.0. Operating System: ROSA Fresh Desktop 2023.1 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-generic-1rosa2023.1-x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.5 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B250M-D3H When idle, the computer goes into sleep mode, as configured in the energy saving settings. All previously running applications continue to run after waking up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #22 from Victor Ryzhykh --- (In reply to fanzhuyifan from comment #18) > Could you paste the output of `journalctl -b` and `sudo dmesg` on the > reported working system with plasma 6 and nvidia? Just wanted to check which > suspend level the system entered. Did you manage to see anything useful? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #21 from Victor Ryzhykh --- Created attachment 165926 --> https://bugs.kde.org/attachment.cgi?id=165926&action=edit sudo dmesg (In reply to fanzhuyifan from comment #18) > and `sudo dmesg` on the > reported working system with plasma 6 and nvidia? Just wanted to check which > suspend level the system entered. Done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #20 from Victor Ryzhykh --- Created attachment 165925 --> https://bugs.kde.org/attachment.cgi?id=165925&action=edit journalctl -b (In reply to fanzhuyifan from comment #18) > Could you paste the output of `journalctl -b` Done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #19 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #17) > Nvidia 545 driver is used. There is a file in the nvidia driver /etc/modprobe.d/nvidia-power-management.conf with text # The destination should not be using tmpfs, so we prefer # /var/tmp instead of /tmp options nvidia NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #18 from fanzhuyi...@gmail.com --- (In reply to Victor Ryzhykh from comment #17) > (In reply to fanzhuyifan from comment #16) > > What Nvidia driver version are you using? After suspending and resuming, > > could you check the output of "cat > > /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us"? > Nvidia 545 driver is used. > I made a disk image to test the functionality of Wayland on my desktop > computer. > I specifically provided a link to the disk image so that others could also > test how Wayland works on Nvidia. > I can't install KDE6 on my desktop computer until program Lokalize is ported > to kf6. > I have KDE5 running on my desktop computer. > I have KDE6 installed on my ASUS ROG Zephyrus M16 (GU603HE-K8007) laptop. > But it has hybrid graphics, so there is no such possibility for verification. > On a laptop with KDE 6, it works well on X11 and Wayland. > I hope that someone will be able to check Wayland’s work on NVIDIA, using > the image of the disk that I applied above. Could you paste the output of `journalctl -b` and `sudo dmesg` on the reported working system with plasma 6 and nvidia? Just wanted to check which suspend level the system entered. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #17 from Victor Ryzhykh --- (In reply to fanzhuyifan from comment #16) > What Nvidia driver version are you using? After suspending and resuming, > could you check the output of "cat > /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us"? Nvidia 545 driver is used. I made a disk image to test the functionality of Wayland on my desktop computer. I specifically provided a link to the disk image so that others could also test how Wayland works on Nvidia. I can't install KDE6 on my desktop computer until program Lokalize is ported to kf6. I have KDE5 running on my desktop computer. I have KDE6 installed on my ASUS ROG Zephyrus M16 (GU603HE-K8007) laptop. But it has hybrid graphics, so there is no such possibility for verification. On a laptop with KDE 6, it works well on X11 and Wayland. I hope that someone will be able to check Wayland’s work on NVIDIA, using the image of the disk that I applied above. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #16 from fanzhuyi...@gmail.com --- (In reply to Victor Ryzhykh from comment #15) > It seems that on KDE6 there is no such problem on Wayland with Nvidia > drivers. > I just made that image https://disk.yandex.ru/d/QgccYm1t71gLWw > I downloaded it to my computer in livecd mode. > > Operating System: ROSA Fresh Desktop 2023.1 > KDE Plasma Version: 5.93.0 > KDE Frameworks Version: 5.249.0 > Qt Version: 6.7.0 > Kernel Version: 6.7.4-generic-2rosa2023.1-x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz > Memory: 15.5 ГиБ of RAM > Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2 > Manufacturer: Gigabyte Technology Co., Ltd. > Product Name: B250M-D3H > > I assembled the kernel according to this recommendation > https://community.kde.org/Distributions/ > Packaging_Recommendations#Kernel_configuration > > I put the computer into standby mode several times and after exiting standby > mode there were no problems with the operation of the Nvidia driver. What Nvidia driver version are you using? After suspending and resuming, could you check the output of "cat /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us"? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #15 from Victor Ryzhykh --- It seems that on KDE6 there is no such problem on Wayland with Nvidia drivers. I just made that image https://disk.yandex.ru/d/QgccYm1t71gLWw I downloaded it to my computer in livecd mode. Operating System: ROSA Fresh Desktop 2023.1 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-generic-2rosa2023.1-x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.5 ГиБ of RAM Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B250M-D3H I assembled the kernel according to this recommendation https://community.kde.org/Distributions/Packaging_Recommendations#Kernel_configuration I put the computer into standby mode several times and after exiting standby mode there were no problems with the operation of the Nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- Ever confirmed|1 |0 --- Comment #14 from Nate Graham --- Not a duplicate of that issue, my mistake. That's X11-only and this is on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #13 from Nate Graham --- *** This bug has been marked as a duplicate of bug 475605 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Neal Gompa changed: What|Removed |Added CC||ekurzin...@nvidia.com, ||ngomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Dmitrii Chermnykh changed: What|Removed |Added CC||chermnykh2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Edward Oubrayrie changed: What|Removed |Added CC||edoubray...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #12 from etnguyen03+kdeb...@gmail.com --- Created attachment 165084 --> https://bugs.kde.org/attachment.cgi?id=165084&action=edit DRM debug logs 2024-01-20 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #11 from etnguyen03+kdeb...@gmail.com --- Created attachment 165083 --> https://bugs.kde.org/attachment.cgi?id=165083&action=edit kwin logs 2024-01-20 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 etnguyen03+kdeb...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #10 from etnguyen03+kdeb...@gmail.com --- Hi - sorry for the late response, I was away for a few weeks. On kwin 5.27.10-2, I have noticed that this happens less often -- or sometimes something slightly different happens (I can unlock my session fine, but then one of my monitors, and every window that I drag into it more than 50%, appears black or does not update). Logs of this are attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 whel...@gmail.com changed: What|Removed |Added CC||whel...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nuno Costa changed: What|Removed |Added CC||sv...@nunocosta.dev -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added CC||bugs@oneyv.org --- Comment #9 from Nate Graham --- *** Bug 437808 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=451386| CC||stephenackerma...@gmail.com --- Comment #8 from Nate Graham --- *** Bug 451386 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Zamundaaa --- Please put > QT_LOGGING_RULES="kwin_wayland_*.debug=true" into /etc/environment, reboot, and then test this again and attach the KWin log afterwards. You can get that (filtered to only KWin) with > journalctl --user-unit plasma-kwin_wayland --boot 0 If you could record a drm debug log as described in https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues that could also be useful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478231 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478090 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Nate Graham changed: What|Removed |Added Keywords||wayland CC||n...@kde.org Severity|normal |critical Summary|kwin on Wayland black |[NVIDIA] kwin on Wayland |screen with cursor after|black screen with cursor |most resume-from-RAM|after most resume-from-RAM Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
