Bug 433731

SUMMARY: Double clicking Icons on New or Custom Activity Desktop does nothing if using a custom Location instead of the default Desktop Folder


STEPS TO REPRODUCE:

1. Create a New Activity
   Right Click on the desktop
   Select 'Show Activity Switcher'
   At the very bottom, click on '+ Create Activity...'
   Give the new Activity an Icon, a Name & Description
   Press OK

Change the "Location:" from the default settings of 'Desktop' to a custom made folder
Configure Desktop and Wallpaper > Location: Change this to custom location
Apply

2. Add an app icon to the desktop via right-clicking on an app from the Application Launcher menu and choosing
   Add to Desktop

3. Double click on the app icon on the desktop


OBSERVED RESULT:

The .desktop file is treated as a normal file with an attempt to open it up with another app


EXPECTED RESULT:

To run the actual app the icon represents, just like on the normal default activitys desktop


SOFTWARE/OS VERSIONS:

Linux/KDE Plasma: 

Operating System: openSUSE Tumbleweed 20210223
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.11.1-2.g992837b-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD PITCAIRN


ADDITIONAL INFORMATION:

Double clicking Icons on New or Custom Activity Desktop does nothing if using a custom Location instead of the default Desktop Folder:




CONCLUSION:

Double clicking on .desktop files, either in the original Desktop folder or ones that have been copied into another folder
will not result in the application launching

Properties in any normal icon on the desktop, under TAB: Application, in field 'Command:' will show just an application name to run,
but no PATH from which to run it from

The only explanation i can think of for the application(s) being able to run in the normal default activity, is because the applications executables are already in the PATH (possibly the PATH Environment variable)

File Managers will just treat all .desktop files as a 'file to be run with an application'
It does not matter if the folder its either the normal Desktop folder or the path /usr/share/applications/ where there are also .desktop files

Custom Activitys also assume this same behavior as file managers, and treat all .desktop files as files to be 'opened' with an application
There is no recognition that the .desktop files are themselves pointers/links to actual executable apps.
Presumably the PATH to these apps is not seen in custom Activitys