Description of problem:
After updating KDE Frameworks to 5.70.0 .desktop link files for terminal programmes (Terminal=true) result in a message saying "konsole" can't be found. Opening a "konsole" from GUI menu works fine, so binary is available.
Blaming component "kf5-kio" is just a guess.
Linking to GUI apps woks anyway.
Create a .desktop link file ("[Desktop Entry]") with run in terminal option (binary file or script doesn't matter).
Run the Link by clicking on it. Error message appears.
Can you confirm the behavior remains after restarting your session? (ie, logout/login, or reboot)
(In reply to Rex Dieter from comment #1)
> Can you confirm the behavior remains after restarting your session? (ie,
> logout/login, or reboot)
Yes, even after reboot.
Plus, I've got the same result on a second system (both are clean F32 net-installs KDE with KDE-Apps, Admin-Tools and Libre-Office as extra option). Desktop-links worked fine, updated using DNF, logout/login ... and broken.
Cleaning qmlcaches in ~/.cache didn't help.
This is in the journal:
'Internal program error. QStandardPaths::findExecutable couldn't find "konsole" but our own logic found it at "/usr/bin/konsole".'
Oh my, it's found by internal logic and don't start anyway.
This commit fixing another bug might be related:
At least, the detection logic was changed and exactly those error text was added.
+ qWarning() << "Internal program error. QStandardPaths::findExecutable couldn't find" << executable << "but our own logic found it at" << candidate << ". Please report a bug at https://bugs.kde.org";
Ok, need to get this reported upstream @ bugs.kde.org asap. I'll be able to it later tonight or tomorrow, but if you (or anyone) could be me to it, would be much appreciated.
(In reply to Rex Dieter from comment #5)
> Ok, need to get this reported upstream @ bugs.kde.org asap. I'll be able to
> it later tonight or tomorrow, but if you (or anyone) could be me to it,
> would be much appreciated.
I've filed a bug. Please comment upstream, if there's something to add.
It turns out, the bug was already tracked and there's a commit, that could be included in a bug-fix build:
Pulled in upstream fix,
(In reply to Rex Dieter from comment #9)
> builds underway.
Gr8! Will test and comment in bodhi, when pushed in testing.
FEDORA-2020-81515f4932 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-81515f4932
FEDORA-2020-81515f4932 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-81515f4932`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-81515f4932
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-81515f4932 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.