https://bugs.kde.org/show_bug.cgi?id=347715
Anatoly Roschenya <anatol.ro...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anatol.ro...@gmail.com
--- Comment #17 from Anatoly Roschenya <anatol.ro...@gmail.com> ---
(In reply to Martin Sandsmark from comment #1)
> KDE uses kio, which by default opens URLs in the appropriate application
> based on mimetype (text files are opened in your text editor, images are
> opened in your image viewer, packages are opened in your package manager,
> etc.).
>
> If you want to change this behaviour go to System Settings, Applications,
> Default Applications, Web Browser and change the setting there to whatever
> you want.
I arrived at this report while researching a different problem. My mistake was
the same, so i'll just explain it for fellow idiots.
In my case the URL being fed to kio was a https link with a bad certificate;
instead of launching the web browser, konsole first fired up a "Server
Authentication" window listing the reasons why the server failed the
authenticity check. After agreeing to continue anyway, i got my browser which
offered a similar certificate error. There's really no point in kio's warning
before going to the browser, but it can't be helped because kio wants to
retrieve the mimetype and needs to establish a https connection before knowing
to launch the browser.
What's worse is that on certain URLs this warning never appeared - the
notification window freezes and i get myself a handful of unaccessible konsole
tabs. Killing the frozen warning window killed the parent along with all its
tabs. I never cared to debug what was causing the freeze, likely local to my
build, but the resolution is to set the default web browser. Thanks Martin!
Another case for this: with kio, dead URLs get no launch feedback from konsole,
only a very tiny plasma notification, and a timeout pop-up after the timeout,
which leaves you lost until it appears. Expected behaviour would be for kio to
trigger launch feedback while attempting to connect, should this be filed
somewhere?
--
You are receiving this mail because:
You are watching all bug changes.
