#5 Anaconda Launcher from LiveCD Desktop doesn't "auto-launch"
Opened by sfaulken. Modified

At the moment, with the F40 LXQt Spin, when clicking on the "Install to Hard Drive" launcher, the desktop asks the user "what do you want to do with the file" and gives you the option of "Open" and "Execute"

Open opens the .desktop file in the text editor
Execute launches Anaconda.

Mime configuration issue maybe?


At the moment, with the F40 LXQt Spin, when clicking on the "Install to Hard Drive" launcher, the desktop asks the user "what do you want to do with the file" and gives you the option of "Open" and "Execute"

Open opens the .desktop file in the text editor
Execute launches Anaconda.

Mime configuration issue maybe?

We bumped into this in Lubuntu as well. It might be a slightly different problem but here is initial bug report - https://bugs.launchpad.net/bugs/1813687
The issue we had wasn't the so much with the desktop entry but what the platform was expecting to have for the metadata. I patched libfm-qt since upstream wanted to do their own thing. Not sure if Fedora is expecting the same thing or not.

It's probably the same issue. I think there were similar bugs reported in the F38 timeframe for both LXDE and LXQt.

Though, I wonder... how are we supposed to set that metadata?

Yeah, it's not something I've had to deal with before, because we don't have a live-installer with openSUSE.

And imagine that, upstream wanting to do their own thing… Where have I heard that before.

I also found notes on the internet about this issue going away if the desktop file is owned by the running user and marked as executable (which, huh? really?).

Anyone want to test if that fixes it? If it does, a patch could be submitted to livesys-lxqt from livesys-scripts.

Metadata Update from @ngompa:
- Issue tagged with: experience

I also found notes on the internet about this issue going away if the desktop file is owned by the running user and marked as executable (which, huh? really?).

Anyone want to test if that fixes it? If it does, a patch could be submitted to livesys-lxqt from livesys-scripts.

Yeah, I can try that.

So on booting into the live environment, the file in question is /home/liveuser/Desktop/liveinst.desktop

Permissions are:

liveuser@localhost-live:~/Desktop$ ls -la liveinst.desktop 
-rw-r--r--. 1 liveuser liveuser 10662 Aug  2 08:32 liveinst.desktop

So user/group is fine, but doing a chmod +x livinst.desktop doesn't change the behavior when trying to launch the installer.

manually setting gio set ~/liveinst.desktop metadata::trusted true in a booted live environment, and then logging out/in to reload the desktop also doesn't do anything.

Try metadata:trust instead.

Try metadata:trust instead.

Yup, running gio set ~/liveinst.desktop metadata::trust true and then logging does the trick.

so then we should decide whether we want to apply Lubuntu's patch to use trusted instead of trust or not. Does any other desktop use this metadata::trusted thing?

I am not aware of another desktop or application outside of LXQt that links against libfm-qt, so I honestly don't know. I've never run into this issue before anywhere else, so I suspect not?

If no other desktop has a similar requirement, let's just use metadata::trust. Can you send a patch to livesys-scripts for this?

I certainly can, just be a few.

https://pagure.io/livesys-scripts/pull-request/22

Still a problem in F41 apparently

Metadata