Bug 422270 - Desktop link files with Terminal=true don't work after KDE Frameworks 5.70.0 update
Summary: Desktop link files with Terminal=true don't work after KDE Frameworks 5.70.0 ...
Status: RESOLVED DUPLICATE of bug 421374
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.70.0
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-30 21:27 UTC by samoht0
Modified: 2020-05-31 06:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description samoht0 2020-05-30 21:27:27 UTC
SUMMARY

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.

Journal error text:
'Internal program error. QStandardPaths::findExecutable couldn't find "konsole" but our own logic found it at "/usr/bin/konsole".'

Linking to GUI apps works anyway.

Seems related to this bugfix commit:
https://bugs.kde.org/show_bug.cgi?id=415567

The detection logic was changed and exactly the above mentioned 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";

STEPS TO REPRODUCE
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.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 32
KDE Frameworks Version: 5.70.0
Qt Version: 5.13.2
Comment 1 samoht0 2020-05-30 21:28:28 UTC
Fedora bugtracker:
https://bugzilla.redhat.com/show_bug.cgi?id=1841860
Comment 2 Ahmad Samir 2020-05-31 06:52:16 UTC

*** This bug has been marked as a duplicate of bug 421374 ***