Bug 365950

Summary: Neon 5.7.2 - Desktop icons stay highlighted
Product: [Plasma] plasmashell Reporter: pmb <s093x6f6>
Component: Desktop icons & Folder View widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: nate, notuxius, plasma-bugs-null, s093x6f6
Priority: NOR    
Version First Reported In: 5.7.2   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: graphic of icon during app running
graphic of icon after closing app

Description pmb 2016-07-21 16:13:43 UTC
First - transfer this where ever you choose - I don't know the correct area. Thank You
And also this report's area maybe Plasma5

Clicking an icon on the desktop starts a program and simultaneously changes the icon to an activated icon. This action has not changed except now the background colour changes also. Personally, I don't like that but just ignore that comment.

Also the changed desktop icon does not revert back to a 'normal' icon until another icon on the desktop is clicked. The closing of the started app has no effect on the modified icon. Opening a desktop folder and clicking an icon does not in anyway affect the modified desktop icon.

If this action is intentional on behalf of KDE then end this bug report.

I apologise, I do not know the correct terminology.


Reproducible: Always

Steps to Reproduce:
1. Click on a desktop icon
2. Close the resultant app or open a desktop folder icon
3

Actual Results:  
The icon remains highlighted long after the icon's opening and closing action

Expected Results:  
Closing the associated app should return the highlighted desktop icon to 'normal'

My workaround is to click any open space on the desktop and all icons return to 'normal'

Hope this helps.
Comment 1 pmb 2016-07-21 19:22:18 UTC
Created attachment 100237 [details]
graphic of icon during app running
Comment 2 pmb 2016-07-21 19:23:01 UTC
Created attachment 100238 [details]
graphic of icon after closing app
Comment 3 Alexander Mentyu 2017-12-08 15:37:24 UTC
I don't think this is a bug
Comment 4 Nate Graham 2020-01-22 16:28:37 UTC
This is fixed now.