Summary: | Icons on active activity reorder after screen connect/disconnect | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Gábor Katona <katonag> |
Component: | Desktop icons & Folder View widget | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aleixpol, alexvkaam, hein, katonag, nate, notmart |
Priority: | NOR | ||
Version: | 5.26.90 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-desktop/commit/a9fece2eaa7e848253548b96a0f4481b1965021f | Version Fixed In: | 5.27.3 |
Sentry Crash Report: | |||
Attachments: |
Desktop icons arranged originally
Desktop icons after disconnecting external screen Desktop icons after reconnecting external screen |
Description
Gábor Katona
2023-01-26 21:06:02 UTC
I have just made further tests. It seems that log out and log in is not affected in reality. The case is that when I logged out, there was screen change (the built-in screen is activated). When logging out without external screen attached the issue does not happen. So it is connected to screen management, maybe the component should be changed Well, that's progress at least. :) Are these desktop icons that keep getting re-ordered files and folders, or are they launcher widgets for apps? Definitely great progress so far, although I still have problems with detecting the screens attached to docking station, but I think this is hardware detection problem. I guess (maybe) launcher widgets for apps, for me these are just icons to start a program: I have set the desktop to show a folder, which contains .desktop files to start applications. This is from plasma-org.kde.plasma.desktop-appletsrc positions={"1920x1080":["1"\\,"20"\\,"file:///home/katonag/.Desktop/Firefox"\\,"0"\\,"0"\\,"file:///home/katonag/.Desktop/Krusader"\\,"0"\\,"1"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"0"\\,"2"\\,"file:///home/katonag/.Desktop/Windows10"\\,"0"\\,"3"]\\,"1920x1200":["4"\\,"20"\\,"file:///home/katonag/.Desktop/Windows10"\\,"3"\\,"5"\\,"file:///home/katonag/.Desktop/Firefox"\\,"3"\\,"8"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"3"\\,"6"\\,"file:///home/katonag/.Desktop/Krusader"\\,"3"\\,"7"]\\,"0x0":["1"\\,"20"\\,"file:///home/katonag/.Desktop/Firefox"\\,"0"\\,"0"\\,"file:///home/katonag/.Desktop/Krusader"\\,"0"\\,"1"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"0"\\,"2"\\,"file:///home/katonag/.Desktop/Windows10"\\,"0"\\,"3"]} Originally Firefox was the last entry in a row at the top left edge. More info: issuing kquitapp5 plasmashell && kstart plasmashell restores the set order Does this still happen if you only have a single activity? Or is it limited to the multi-activity use case? Sorry for the late reply. I have tested it by creating a fresh user. I have logged in, the desktop had Trash and Home as default. I have added Firefox and System setting simply by copying from the panel. Ordered them (see fig 1.png) in reverse alphabetical order and Trash moved away. After disconnecting the external screen the icons were reordered in some random way (2.png). Reconnecting the external screen resulted again in reordering (3.png), now in alphabetical order, except Trash, which is moved to the top left corner, where it was originally. Created attachment 156021 [details]
Desktop icons arranged originally
Created attachment 156022 [details]
Desktop icons after disconnecting external screen
Created attachment 156023 [details]
Desktop icons after reconnecting external screen
Thanks for the info. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1409 Git commit ea3ab420547dfbbe861275ca37dbf8e032a787fe by Marco Martin. Committed on 03/03/2023 at 11:15. Pushed by mart into branch 'Plasma/5.27'. Partly revert "make sure screen numbers are consecutive" This partly reverts commit 074e4efecba92e32b7fefffe68f9734be0a61e8b. That patch for screen consistency was quite error prone: when a screen gets removed, only the mappings of the current activity will be removed, therefore the assumption that the screens on itemsOnDisabledScreens have all an id major than the ones in screenMapping does not hold. at every plasma startup therefore itemsOnDisabledScreens would get ids reassigned to numbers that won't make sense M +3 -22 containments/desktop/plugins/folder/screenmapper.cpp https://invent.kde.org/plasma/plasma-desktop/commit/ea3ab420547dfbbe861275ca37dbf8e032a787fe Git commit a9fece2eaa7e848253548b96a0f4481b1965021f by Marco Martin. Committed on 03/03/2023 at 11:37. Pushed by mart into branch 'master'. Partly revert "make sure screen numbers are consecutive" This partly reverts commit 074e4efecba92e32b7fefffe68f9734be0a61e8b. That patch for screen consistency was quite error prone: when a screen gets removed, only the mappings of the current activity will be removed, therefore the assumption that the screens on itemsOnDisabledScreens have all an id major than the ones in screenMapping does not hold. at every plasma startup therefore itemsOnDisabledScreens would get ids reassigned to numbers that won't make sense M +3 -22 containments/desktop/plugins/folder/screenmapper.cpp https://invent.kde.org/plasma/plasma-desktop/commit/a9fece2eaa7e848253548b96a0f4481b1965021f It is partly offtopic, but could you advise me where to report screen detection issues? The screens connected to usb-c dock are not detected reliably. Maybe it is also connected to KDE screen management, because I feel like it became worse since 5.27, but not sure. I feel more like a hardware detection issue (sometimes even the screen EDIDs are mixed up) *** Bug 466869 has been marked as a duplicate of this bug. *** The same bug is still present in KDE6, as I reported in 484806 |