I have installed and configured Tumbleweed on four PCs previously without encountering this problem. I always park a Folder View widget on the panel for use as a quick-start launcher, and I point the widget to a folder called FaveApps in /home. Then I drag the most frequently used applications from the start menu into the FaveApps folder with the ‘Link here’ option and rename all the links to the actual application name, eliminating the nnnnn.desktop filename in favor of one that is immediately more recognizable.
Thereafter, as expected, clicking on the Folder View widget pops up a list of the contents of the FaveApps folder. Clicking on any folder item effects the desired quick-launch of the selected application.
Just installed Tumbleweed on my neighbor’s old Win7 -> Win10 PC, which had recently become irreparably confused. However, after adding the Folder View app and pointing it to a folder containing links to favorite apps, selecting an item from the Folder View’s popup list brings up Kate with the contents of the link file. Works the same for every link file! However if I right-click on any of the Folder View’s popup list and select ‘Open’, then it launches the app as expected. However, that’s intrusive, counter to how it works on every other Tumbleweed system I’ve set up, and is not what I would consider a quick-launch capability.
I’ve investigated fiddling with the File Associations for x-desktop without any success. I’m at a total loss why this one oddball won’t work as expected.
On 04/03/2017 05:26 PM, sblass wrote:
>
> I have installed and configured Tumbleweed on four PCs previously
> without encountering this problem. I always park a Folder View widget on
> the panel for use as a quick-start launcher, and I point the widget to a
> folder called FaveApps in /home. Then I drag the most frequently used
> applications from the start menu into the FaveApps folder with the ‘Link
> here’ option and rename all the links to the actual application name,
> eliminating the nnnnn.desktop filename in favor of one that is
> immediately more recognizable.
>
> Thereafter, as expected, clicking on the Folder View widget pops up a
> list of the contents of the FaveApps folder. Clicking on any folder item
> effects the desired quick-launch of the selected application.
>
> Just installed Tumbleweed on my neighbor’s old Win7 -> Win10 PC, which
> had recently become irreparably confused. However, after adding the
> Folder View app and pointing it to a folder containing links to favorite
> apps, selecting an item from the Folder View’s popup list brings up Kate
> with the contents of the link file. Works the same for every link file!
> However if I right-click on any of the Folder View’s popup list and
> select ‘Open’, then it launches the app as expected. However, that’s
> intrusive, counter to how it works on every other Tumbleweed system I’ve
> set up, and is not what I would consider a quick-launch capability.
Make sure that the folder that the files reside in has the “execute” bit
set.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Thanks for your answer. Was beginning to believe no one cared enough to write!
That’s what makes this so **** puzzling. The folder permissions on the offending system are identical to all other systems where the Folder View quick launch works as intended:
My offending system was created from the 20170329 snapshot, and it - like all the rest - is using Packman repository. So the time frame of the new installation jibes with your noticing it after a daily update several days ago.
That doesn’t work for me either as I have a fairly complex desktop with multiple folder views that are loaded from NFS shares so that any change made propagates to all of my computers as well as local folder views and widgets.
Background: by default, if you click on a application “link”, the user is asked whether to open the file in a text editor or execute it (for security reasons).
Maybe the user chose “Don’t show this again”, so the selection was saved and is not asked any more.
The folder view applet ignored this setting (and always run the application without asking) until recently, but that was fixed in 5.9.1.
That did the trick, and thank you so much. In retrospect, I think I probably shot myself in the foot on this. At the time of setting up the FolderView and launching the first application, I was mentally preoccupied with a few too many balls in the air. I probably selected ‘Open’ vs. ‘Execute’, as well as ‘Don’t show this again.’
