https://bugs.kde.org/show_bug.cgi?id=439132
Bug ID: 439132
Summary: kioexec is used, even if the application enables its
own network transparency with %u
Product: frameworks-kio
Version: 5.83.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: magnus.gros...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Download telegram-desktop
2. Register telegram-desktop's desktop file, by opening the Settings and
blindly typing the cheat code "registertg" (no input field focused)
3. Close Telegram Desktop
4. Run xdg-open 'tg://resolve?domain=durov'
OBSERVED RESULT
kio-exec terminates with error "unknown protocol tg://"
EXPECTED RESULT
Telegram Desktop starts with https://t.me/durov opened as chat
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
Deleting the local desktop file
~/.local/share/applications/userapp-Telegram-Desktop-HUPUW0.desktop solves the
problem.
HOWEVER, replacing the content of that same file with the content of the
system-wide /usr/share/applications/telegramdesktop.desktop does NOT solve the
problem.
So it must be a bug in the way that KDE parses local desktop files. kioexec
should not be used at all to download the url, it should just pass the argument
to Telegram.
Original issue at the telegram repo:
https://github.com/telegramdesktop/tdesktop/issues/16478
Output of the above xdg-open command:
command= "/usr/bin/telegram-desktop -workdir ~/.local/share/TelegramDesktop/ --
%u" args= ("/usr/bin/telegram-desktop -workdir ~/.local/share/TelegramDesktop/
-- %u", "tg://resolve?domain=durov")
kf.kio.core: Protocol Class of url QUrl("tg://resolve?domain=durov") , isn't
':local', cancelling job.
Copying QUrl("tg://resolve?domain=durov") to
QUrl("file:///~/.cache/kioexec/krun/7009_0/unnamed")
kf.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes
Protokoll „tg“.\n"
If I am not mistaken, the above command and args string seem to have parsed the
parameters incorrectly?
--
You are receiving this mail because:
You are watching all bug changes.
