[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #15 from Chandradeep Dey --- *** Bug 434362 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/720 -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Nicolas Fella changed: What|Removed |Added CC||edj7...@gmail.com --- Comment #12 from Nicolas

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #11 from Bug

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Nicolas Fella changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #10 from

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Chandradeep Dey changed: What|Removed |Added CC||k...@chandradeepdey.com --- Comment #9 from

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #8 from magnus.gros...@gmail.com --- Yes the desktop file contains %u -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #7 from Ahmad Samir --- It's not directly related to kopenwithdialog, it's more to do with the .desktop file Exec line not having %u or %U. Reading the report again, I see that you mentioned %u is used in the file, right? -- You are

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #6 from magnus.gros...@gmail.com --- Nope, this bug has nothing to do with kopenwithdialog. The desktop file is generated and made default by Telegram Desktop itself. -- You are receiving this mail because: You are watching all bug

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #5 from Ahmad

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 meso5 changed: What|Removed |Added CC||me...@gmx.com --- Comment #4 from meso5 --- I am

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #3 from magnus.gros...@gmail.com --- The problem is that when the desktop file does not define the MimeType handler but the user says that the program should be the default for that handler, then kde-open5 will open the service with the

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #2 from magnus.gros...@gmail.com --- Actually this is a KDE bug after all. While it is true, that the local desktop file does not contain the MimeType line, the ~/.config/mimeapps.list file contains a line, that the above mentioned local

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 magnus.gros...@gmail.com changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 magnus.gros...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG

[frameworks-kio] [Bug 439132] kioexec is used, even if the application enables its own network transparency with %u

https://bugs.kde.org/show_bug.cgi?id=439132 --- Comment #1 from magnus.gros...@gmail.com --- Sorry my bad, this is a bug from the Telegram side. They forgot to put the MimeType line into the local desktop file (but did not forget to put it into the systemwide desktop file). I will close this now.