Firefox KDE support

[moray33]

It worked for me in previous versions but not this time, I don't know what's the difference. Maybe it's because Firefox in the PPA was pending to be built and there wasn't that package there... A minutes ago, I updated and now I have the Firefox-KDE and the pin seems working fine again:

moray33@Jose:~$ sudo apt-cache policy firefox
[sudo] password for moray33:
firefox:
Instalados: 16.0.2+build1-0ubuntu0.12.04.1+ppa1
Candidato: 16.0.2+build1-0ubuntu0.12.04.1+ppa1
Tabla de versión:
*** 16.0.2+build1-0ubuntu0.12.04.1+ppa1 0
1000 http://ppa.launchpad.net/blue-shell/firefox-kde/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
16.0.2+build1-0ubuntu0.12.04.1 0
500 http://es.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
11.0+build1-0ubuntu4 0
500 http://es.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

[Mr_Bumpy]

I think moray33 is right. I didn't touch my pin setup, but when the Firefox package "disappeared" from the blue-shell PPA because it was still building, I was offered the upgrade to the Ubuntu Firefox package. When the blue-shell Firefox package was done building, then I was automatically upgraded again to the blue-shell version. So the pin works: as long as there is a firefox package in the blue-shell PPA, it will be given priority over other versions.

[geoaraujo]

That seems to be right. I'm running firefox blue-shell package again.
However, it would be nice if we could just automatically avoid those undesired updates....

[wrender]

Errg I am confused. What is the conclusion drawn from all this. What does a user have to do to use FF with kde support that is not lost?

I need to change pin numbers Yes/No?
Lock package files? Yes/No?

[Wallace]

Just follow my recipe above using the Force and Lock option in Muon.
This morning I noticed the blue-shell update, unlocked Firefox and Firefox-locale, forced the new version and updated.
Then I locked them again.

Could you expand on this a little bit more. I am having difficulty trying to find the prompt to force and lock. Thanks!

[Wallace]

OK.
1.You open Muon and type firefox in the search bar.
2.Now toggle the Status so installed items are on top.
To start select firefox and in the bottom half you select the Version tab.
You should see several (probably 3) versions of Firefox, select the one from the ppa and at the bottom there'll be a Force button to click.
Do the same for the Firefox-local version(s) you have installed and now Apply changes.
When done updating go back to 1. and 2. and right click the installed Firefox and Firefox locale and select Lock Package.
Done

Please be aware I'm running a Dutch version and a few things/tabs/buttons might have a slightly different translation in your version.

Can't force (greyed out) version on my computer.

"Muon always selects the most applicable version availeble. If you force a
different version from the default one, errors in the dependency handling can
occur.”

[Xplorer4x4]

I just upgraded to v17 from blue-shell ppa(confirmed it is not the gtk version as I did the upgrade over cli and watched 3 packages pulled from the blue-shell ppa). Is it just me or is middle clicking to open new tabs broken? When I click my mouse wheel to open new tabs, nothing happens. Actually I have InfoRSS Add on installed, which scrolls news from rss feeds across the top of the browser, and middle click does work there. :s I am running with add on compatibility checking disabled, because most of the time, the updates do not break compatibility. So it is possible to be an add on(I am thinking tab utilities), but just wanted to check here first.

[vinnywright]

clicking the mouse wheel opens a new tab @hear(if done where a new tab should be)

VINNY

[Xplorer4x4]

Yeah I was jsut about to update, it's a tab utilities bug, well actually it's bugs in firefox breaking TU according to the dev.

[jlittle]

I just upgraded to v17 from blue-shell ppa ... Is it just me or is middle clicking to open new tabs broken? ... I am running with add on compatibility checking disabled

When I ran it after the upgrade, Tab Mix plus was disabled, but I was offered a new version, which installed quickly. It gives the middle-click for me, so maybe you just need a new version of that add on.

Regards, John Little

[Xplorer4x4]

Tab Mix Plus and Tab Utilities are two different add ons.

[shadeslayer]

Hi everyone
Just wanted to let you know that firefox has been updated to v17 for Precise and Quantal. Please do post here if you find any issues, alternatively, please contact us via https://launchpad.net/~blue-shell/+contactuser

We will try and resolve your issues ASAP

Ninja Edit : Precise packages still need to be built.

[RussianNeuroMancer]

I just wondering, why you build 17.0 instead of 17.0.1?

btw, 17.0.1 with patches for KDE support is available in ppa:alexey-ivanov/firefox-kde.

[shadeslayer]

They *just* uploaded 17.01 , which is why we don't have it in the PPA yet, I'll upload 17.01 tomorrow

[SteveRiley]

They *just* uploaded 17.01 , which is why we don't have it in the PPA yet, I'll upload 17.01 tomorrow

This would be a good time to remind everyone who uses the Blue Shell PPA of the following. Because of the extra work required to recompile Mozilla's source code and test the KDE integrations with each new Firefox release, updates to the binary in the Blue Shell PPA will usually lag behind the official updates a few days. As I've discussed in various threads throughout the forum, security decisions always invole making some kind of risk trade-off. This is a perfect example of such.