Bug 428100 - Regression: A symbol on the desktop pointing to a file tries always to open a program and fails
Summary: Regression: A symbol on the desktop pointing to a file tries always to open a...
Status: RESOLVED DUPLICATE of bug 427797
Alias: None
Product: plasmashell
Classification: Plasma
Component: Icon widget (show other bugs)
Version: 5.20.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-22 11:39 UTC by Walther Pelser
Modified: 2020-10-26 18:45 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Walther Pelser 2020-10-22 11:39:04 UTC 
SUMMARY
Regression
Since 5.20 a symbol on my desktop can not open files anymore and I get error messages, opening programs works as before.

STEPS TO REPRODUCE
1. always after having upgraded to 5.20.0
2. 
3. 

OBSERVED RESULT 
Klicking on a symbol, which should open a file on my pc, it tries to open a program. If choosing "accept", I get always the comment, that the *.desktop file in /home/*/.local/share/plasma_icons/*.desktop is invalid. But this is not true. Opening this desktop file direct in /home/*/.local/share/plasma_icons/*.desktop works.
The properties of that symbol contains the right url.
The desktop file contains "Type=Link", this may cause the problems. If "type" is "application" it works normal.

EXPECTED RESULT
symbol should open the file mentioned in the url

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE TW current
(available in About System)
KDE Plasma Version: 5.20.0
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
5.20.0 has more issues with openSUSE TW
Comment 1 Walther Pelser 2020-10-24 12:06:52 UTC 
workaround is:
right klick on the symbol, choose "open with", then: "Dolphin (KF5)". This opens a file as a file.
Comment 2 Sven Wappler 2020-10-24 22:17:13 UTC 
I can confirm this problem.
Comment 3 Nate Graham 2020-10-26 18:45:33 UTC 

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