Summary: | On Wayland, real-fake-session-restored application not restored onto their virtual desktops | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | loma <lomaharshana> |
Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | alanjprescott, aleixpol, bugs.kde.org, fanzhuyifan, jlp, julien.dlq, m.kurz, nate, philipp.verpoort, postix |
Priority: | NOR | ||
Version: | 6.0.1 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=336990 https://bugs.kde.org/show_bug.cgi?id=390295 https://bugs.kde.org/show_bug.cgi?id=436318 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
loma
2024-03-08 04:45:11 UTC
I remember seeing a duplicate of this, but I can't find it now... There's Bug 336990, but it looks like there may be a bunch of different issues that need to be tracked separately. I can confirm that I'm seeing the exact same behaviour. Windows are restored on the virtual desktops where they were before when using X11, but it's broken on Wayland. I tested this by logging out, switching from Wayland to X11 (in the bottom left corner of the login screen), and logging back in again. Notably, this has nothing to do with restoring the Plasma user session. Windows should restore correctly even when simply restarting (or closing/reopening) Firefox. Meanwhile, Chromium windows restore just fine on the correct virtual desktops in Wayland. So it's a Firefox-specific issue. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) After some further testing, I can confirm that in Wayland the size of Firefox windows is restored correctly, but neither their position nor the specific screen (in a multi-screen system) nor the virtual desktop is restored. All windows just pop up in the centre of the primary screen on the current virtual desktop. *** Bug 484318 has been marked as a duplicate of this bug. *** |