Bug 511662 - 6.5.1 messed up desktop folder
Summary: 6.5.1 messed up desktop folder
Status: RESOLVED DUPLICATE of bug 511131
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop icons & Folder View widget (other bugs)
Version First Reported In: 6.5.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-05 07:36 UTC by Peter Tselios
Modified: 2025-11-06 16:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Tselios 2025-11-05 07:36:23 UTC
SUMMARY
At the latest update of my Tumbleweed, I ended up with 6.5.1. 

I use X11. The update messed up my desktop big time and it's definitely a "downgrade" in terms of usability. Starting with "decisions" taken automatically for me, which was to enable "Desktop" view instead of my Desktop Folder that i use for years. Then, we have 2 bugs (that I have discovered so far): 

1. When I use Desktop Folder, icons are stuck at the top left of the primary screen and I am not able to move them no matter what (confusing) settings I choose. Lock in place is *disabled*. Sort by is set to Manual. This is a really nasty regression especially since I use a number of widgets in my primary screen and now either the widgets aren't visible or he icons aren't there! 

2. When I shade a window (and I do that a lot!), on the screen I see a while line of the window's frame! This happens to GTK (eg Firefox/Chrome) and KDE apps. 

STEPS TO REPRODUCE
1. Upgrade to 6.5.1 and use X11

OBSERVED RESULT
As above

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: openSUSE Tumbleweed 20251031
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version:  6.17.6.1

ADDITIONAL INFORMATION
X11
Comment 1 David Edmundson 2025-11-06 16:32:58 UTC

*** This bug has been marked as a duplicate of bug 511131 ***