| Summary: | Plasma does not correct start-up after upgrade to 5.23.5 | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | hasezoey |
| Component: | generic-multiscreen | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | nate, plasma-bugs |
| Priority: | NOR | ||
| Version: | 5.23.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
hasezoey
2022-01-28 14:27:07 UTC
i forgot to add: since upgrading to 5.23.5, some windows like VSCode (AUR) start-up on the left-most display, always, but in 5.23.4, it started where it last closed, which is in middle of the 3 displays > Graphics Processor: AMD Radeon RX Vega Very likely hitting https://bugzilla.kernel.org/show_bug.cgi?id=206387. *** This bug has been marked as a duplicate of bug 353975 *** > Very likely hitting https://bugzilla.kernel.org/show_bug.cgi?id=206387. i dont think that i am hitting *that* issue, because the display configuration is still there and mostly all windows start where they should (expected the mentioned ones like VSCode since 5.23.5) so the blackscreen and missing wallpaper is only that plasmashell (or whatever) does not correctly start-up also from what i can tell, my configuration of displays is correctly picked-up (kde is loading the display configuration correctly, but is missing the setting for "Primary Display", which should come with 5.24) here is my configuration: - Graphics card: AMD Vega 64, 2 HDMI ports, 2 Display Ports, 1 DVI (i think) - Display on the most left: HDMI connected Samsung 1080p monitor - Display in the middle: Displayport connected HP Omen 1440p monitor - Display on the most right: Displayport connected DELL 1080p monitor the only place where the displays are not correctly set-up is in SDDM, because i dont know where to change that (but that does not matter) > *** This bug has been marked as a duplicate of bug 353975 *** i also dont quite think this issue is exactly my issue, because yes it happened in 5.23.x before, but since 5.23.5 it happens *consistently*, i can reproduce it at each reboot since 5.23.5 my reproduction steps on 5.23.5: - boot-up - login for the first time on boot - logout (like i mentioned, because of the issue of the taskbar being on the wrong display, 5.24 should fix this with "Primary Display" like on X11) - log back in and the issue is there now - logging back out and back in again also bring up the issue, also rebooting again and doing the same steps it always happens in 5.23.5 from what i can tell, in 5.23.5, it so always chooses the left-most screen for the task-bar on first login (unlike in 5.23.4 and 5.23.x, where it only ~30% of the time chose the left most screen instead off the middle screen) also, like i mentioned, the workaround of using "kstart5 plasmashell" to resolve the issue of plasmashell (again, i dont know if this is the right component) starting up, in 5.23.x it always worked and started-up back right away after executing the command, but in 5.23.5 it somehow does not and also requires a extra argument to be added PS: because of this issue, 5.23.5 is not really usable for me and have to stay reverted to 5.23.4 for now Update for my case today: i booted up to the 5.23.5 install, and somehow it works today without issue what i did since upgrading: - upgrade from 5.23.4 (only time, just included for timeline) (on btrfs, root (not a snapshot) read-write, home (not a snapshot) read-write) - rebooted - noticed that it does not start-up correctly - rebooted and re-tried again (for 2 more times) - gave up and reverted to a snapshot before the upgrade (btrfs, snapshot for root was read-only, home (not a snapshot) was mounted read-write) - booted the mentioned snapshot for at least 2 times - tried latest install again, and everything works fine (btrfs, read-write root (not a snapshot) and read-write home (not a snapshot)) so i dont know what was the problem or how it happened, but it seems fixed for now (i mean the issue that it is reliably not starting, the occasional non-start comes still) |