https://bugs.kde.org/show_bug.cgi?id=467074
--- Comment #22 from LabHamster <kde.1m...@simplelogin.com> --- Is KDE still patching x11 at this point in time? I'm asking to determine if I should be focusing replication of a healthy state on x11, Wayland, or both as I know some distros like Fedora are planning to be Wayland only w/ Plasma 6.0.0. This ticket mentions x11 and potentially working on 5.27.0, but I tried Wayland on 5.26.5 and still get the all black screen w/ mouse issue. As luck would have it, I was able to update my KDE system HW to use a 2080 Ti w/ proprietary drivers and I have two monitors over DisplayPort, so it's a matter of x11 vs Wayland being the only major factor in trying to replicate a known healthy state of another bug experiencer. With the following I can replicate this issue, so it doesn't seem like it was working on Wayland in 5.26.5: Operating System: Fedora Kinoite Linux 37.20230215.0 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 How to replicate software side to hunt for the release that corresponds to this bug while I continue to experiment to try to find a prior healthy state. 1. Have bug in first place with KDE 2. Install Fedora Kinoite 3. If not on Fedora Kinoite 37 rebase with: rpm-ostree rebase fedora:fedora/37/x86_64/kinoite 4. Iterate through ostree commits using a command like: rpm-ostree deploy 37.20230215.0 5. Reboot after getting to said commit 6. While logged on launch a few apps to see if they vanish later on 7. Try to trigger the bug. For me, it's switching to another system with a KVM switch for period of time and then back to the KDE system. Currently using 5 minutes, but will try to make it smaller and smaller to increase ability to iteration through ostree commits -- You are receiving this mail because: You are watching all bug changes.
