Describe the bug
Launcher .desktop file keys such as Terminal= and Path= are ignored when clicking a launcher from the desktop. The same .desktop files work fine is set up as a panel or menu launcher.
This isn't a strictly beta issue - it exists in 19.1 and I think it was introduced with Nemo 4.0.6 and this commit which fixed a failure for launchers with pkexec in the Exec=
''Stack trace''
If you are reporting a crash. Go to "Software Sources" and enable the debug symbols. Then go to "System Reports" and extract the stack trace for your crash and paste it here.
''Dmesg''
If you type dmesg in a terminal, you should see a line corresponding to the crash. Paste it here.
Additional context
Add any other context about the problem here.
Describe the bug Launcher .desktop file keys such as Terminal= and Path= are ignored when clicking a launcher from the desktop. The same .desktop files work fine is set up as a panel or menu launcher.
This isn't a strictly beta issue - it exists in 19.1 and I think it was introduced with Nemo 4.0.6 and this commit which fixed a failure for launchers with pkexec in the Exec=
https://github.com/linuxmint/nemo/commit/816659bb5d1be67ddf3059dddfe91286af3a8eb5
It would be nice to get it fixed in the current beta bug fix run....
Related issues.
https://github.com/linuxmint/nemo/issues/2009 https://github.com/linuxmint/nemo/issues/2078 https://github.com/linuxmint/cinnamon/issues/8425
To Reproduce Steps to reproduce the behavior:
Please see linked issues.
Expected behavior
Working launchers without workarounds
Frequency Does the issue happen:
Edition (Desktop environment): In which edition is this happening?
Live or post-install: Indicate if this is happening after the installation, or during the live session:
Locale: Paste the output of
locale
.Drivers: Paste the output of
inxi -Gxx
.Crash report:
''Stack trace'' If you are reporting a crash. Go to "Software Sources" and enable the debug symbols. Then go to "System Reports" and extract the stack trace for your crash and paste it here.
''Dmesg'' If you type
dmesg
in a terminal, you should see a line corresponding to the crash. Paste it here.Additional context Add any other context about the problem here.