From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: KDE URL-handling weirdness [solved]
Date: Thu, 31 Jan 2013 13:00:36 -0600 [thread overview]
Message-ID: <20130131130036.7c8e26eb@fuchsia.remarqs.net> (raw)
In-Reply-To: 20130131124107.19dfbc2c@fuchsia.remarqs.net
On Thu, 31 Jan 2013 12:41:07 -0600
»Q« <boxcars@gmx.net> wrote:
> I suppose this started when I upgraded to KDE 4.9.5, but I just
> noticed it today.
>
> In KDE's system settings, I have Firefox set as the default web
> browser. It worked fine before now. But now when I click on an
> http: or https: URL in some other application, KDE downloads the page
> to its local cache, then launches Firefox to open the local file. So
> my Firefox is opening a file such as
> file:///var/tmp/kdecache-q/krun/8144_0_
>
> I don't think I've changed any settings that should affect this, and I
> don't know what to change to fix it.
Sorry for the noise -- I didn't do enough searching before posting
here.
I fixed it by changing the command in Firefox's .desktop file from
"firefox" to "firefox %u".
prev parent reply other threads:[~2013-01-31 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 18:41 [gentoo-user] KDE URL-handling weirdness »Q«
2013-01-31 19:00 ` »Q« [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130131130036.7c8e26eb@fuchsia.remarqs.net \
--to=boxcars@gmx.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox