Firefox KDE support

[Wallace]

What I have found though is that Firefox won't display the application to use in the dialog box when I click on a link. It always says "open with browse". For example previously with the blue-shell version (kubuntu 12.04), when I clicked on a .nzb link it would show "open with Kwooty" in the dialog box, not now.

SOLVED: Downloaded firefox-kde-support and all is well.

[SteveRiley]

I pinned the blue-shell version to 1001 and did dist-upgrade which downgraded me to 16.0.1. But I assume now I am NOT running the blue-shell version - correct? (Kubuntu 12.10)

The three asterisks point to the one that's installed. After you pinned the Blue Shell PPA, you can tell that this is the one that's installed because it's the one indicated by the asterisks.

Something that we should all be aware of is that the Firefox binary in the Blue Shell PPA is recompiled from source, and it may not always contain the absolute latest bits from Mozilla. If, for instance, Mozilla fixes a security vulnerability and the standard Ubuntu Firefox is updated, there's no guarantee that the Blue Shell Firefox will be updated at the exact same time.

Also, to answer potential questions in advance, there is no blame to place here. Package maintainers operate on their own schedules. Even the Ubuntu packages might be a bit behind the Mozilla fix; if you really want the bleedingest edge, you'll have to compile from source yourself. To use the Blue Shell PPA, knowing that it may involve occasional delays in being updated, is a risk decision each of us must make on our own.

[Wallace]

wallace@wallace-P35C-DS3R:~$ apt-cache policy firefoxfirefox:
  Installed: 16.0.2+build1-0ubuntu0.12.10.1
  Candidate: 16.0.2+build1-0ubuntu0.12.10.1
  Version table:
 *** 16.0.2+build1-0ubuntu0.12.10.1 0
        500 [url]http://kr.archive.ubuntu.com/ubuntu/[/url] quantal-updates/main amd64 Packages
        500 [url]http://security.ubuntu.com/ubuntu/[/url] quantal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     16.0.1+build1-0ubuntu2~ppa1 0
       1000 [url]http://ppa.launchpad.net/blue-shell/firefox-kde/ubuntu/[/url] quantal/main amd64 Packages
     16.0.1+build1-0ubuntu1 0
        500 [url]http://kr.archive.ubuntu.com/ubuntu/[/url] quantal/main amd64 Packages

I pinned the blue-shell version to 1001 and did dist-upgrade which downgraded me to 16.0.1. But I assume now I am NOT running the blue-shell version - correct? (Kubuntu 12.10)

wallace@wallace-P35C-DS3R:~$ apt-cache policy firefoxfirefox:
  Installed: 16.0.1+build1-0ubuntu2~ppa1
  Candidate: 16.0.1+build1-0ubuntu2~ppa1
  Version table:
     16.0.2+build1-0ubuntu0.12.10.1 0
        500 [url]http://kr.archive.ubuntu.com/ubuntu/[/url] quantal-updates/main amd64 Packages
        500 [url]http://security.ubuntu.com/ubuntu/[/url] quantal-security/main amd64 Packages
 *** 16.0.1+build1-0ubuntu2~ppa1 0
       1000 [url]http://ppa.launchpad.net/blue-shell/firefox-kde/ubuntu/[/url] quantal/main amd64 Packages
        100 /var/lib/dpkg/status
     16.0.1+build1-0ubuntu1 0
        500 [url]http://kr.archive.ubuntu.com/ubuntu/[/url] quantal/main amd64 Packages

How do I install the blue-shell version.

[claydoh]

shadeslayer: nice to see you here

What is the possibility of modifying the Kubuntu Firefox installer to point to the PPA? Is that not kosher?
if not, how much of kmozillahelper is needed just to add mimetype support for Kubuntu's Firefox users? I.e. leave out the theming, filepicker, printer, etc, just to allow for a stock Firefox (Well. a stock Ubnuntu version that is) to work properly?

[DeadlyOats]

Thanks, very much! You were quite helpful.

[shadeslayer]

Correct.

Depends on what you want. If you exclusively use KDE, I would recommend the KDE Patched firefox. It follows the same buton style as KDE ( Apply on the left, Cancel on the right, unlike gnome which has the buttons swiched the other way around ), support for mimetype handling with KDE apps, etc etc.

[DeadlyOats]

Thanks, very much for your reply.

To be sure I understand you, by "latter" you mean I get the 'strait-up Mozilla version of Firefox' from the kickoff Install Firefox icon, but if I add the PPA, I get KDE's flavor of Firefox, instead. Is that right?

Which is the better version for Kubuntu 12.04, are there bugginess issues with either one, or are there advantages of one over the other, or is it just a matter of preference?

[shadeslayer]

It's the latter, you can only get the patched KDE version if you have added the PPA. If in case you have added the PPA and then install it via the Kickoff, you'll get the KDE patched version.

tl;dr don't add the PPA, you'll get the unpatched version of FF

[DeadlyOats]

In Ubuntu, you get the Ubuntu 'flavor' of Firefox. I just installed Kubuntu 12.04 LTS on my machine (again). I want Mozilla's - strait-up - Firefox. If I click on the "Install Firefox" icon in the Kubuntu 'Kickoff Application Launcher', is that the same as the Ubuntu 'flavored' Firefox, or is that a Kubuntu 'flavored' Firexfox, or is it Firefox - strait-up - Mozilla style?

Which 'flavor' is most recommended for installing in Kubuntu 12.04?

[shadeslayer]

Alrighty, I did the complete dance now, and I believe the issue is probably because you don't have the getdeb repos enabled. Have you enabled the getdeb repos by following this : http://www.getdeb.net/updates/Ubuntu...how_to_install ?

[Xplorer4x4]

Hi
Can you make sure apturl-kde is installed?

Installed and newest version. Did you try the link? For me it looks and acts like it installed, says package info refreshed, then I get a pop up that says (I think) it failed to locate the package.

[shadeslayer]

Hi
Can you make sure apturl-kde is installed?

[Xplorer4x4]

AptURL seems to work fine here on my Firefox (Kubuntu 12.04 w/ KDE 4.9.2).

Thanks, can you confirm if it works here:
http://www.getdeb.net/software/RSSOwl

[Mr_Bumpy]

Can any one else verify if this bug is still present:
https://bugs.launchpad.net/ubuntu/+s...rl/+bug/476853

AptURL seems to work fine here on my Firefox (Kubuntu 12.04 w/ KDE 4.9.2).

[ti_tux]

@ti_tux
You can try a quick test - try with a new/clean profile to see does the issue persist

Indeed, with a new profile, no issue anymore...