Description of problem: Some days ago, Mozilla released Firefox 5 with new functionalities and security issues solved. The new release is into the new Mozilla's release cicle (a mayor version every some weeks). So now, the Firefox 4.0.1 users have those vulnerabilities and in the future the problem will be bigger and bigger for Firefox 4 users. Will you apply the new release cicle into Mageia or we will have Firefox 4 until a new Mageia release? Thanks.
as FF4 is on EOF, we will provide FF5 in updates sooner or later ( sooner i hope, i need to fix patches in the rpm first )
CC: (none) => dmorganec
EOL of course
CC: (none) => boklmComponent: New RPM package request => SecurityHardware: i586 => AllSummary: Will you update to Firefox 5? => Firefox 5 update
CC: (none) => goofyfa04Hardware: All => i586Target Milestone: --- => Mageia 1
*** Bug 2089 has been marked as a duplicate of this bug. ***
CC: (none) => info
Depends on: (none) => 2090
Assignee: bugsquad => dmorganec
CC: (none) => marianne
Hi all I think that it's important to have the firefox updates more quickly than today. Firefox 5.01 fixes some bugs that fixes bugs of Firefox 4.01. My other PC that is under Debian Squeeze, turn now with Firefox 5.01 !!!
CC: (none) => p.opter
FWIW, bug 1880 should maybe block the update, it's cosmetic, yes, but it's very visible to the users.
CC: (none) => enzolyte
Is there some progress here? I'm using locally built, from cauldron backported Firefox 5 packages since over 1 month without a problem. AFAIK, there isn't even an update candidate?
CC: (none) => doktor5000
yes this is ready to go in updates but please stop arguing this required a lot of work as the packaging changed. arguing won't help packagers to work faster. I will push today in updates_testing
Sorry, maybe you misunderstood. I didn't want to argue, only wanted to know if there is some progress or already an ETA. But thanks for the information.
CC: (none) => stormi
CC: (none) => marcello.anni
thanks, its works on my x86_64 OS
is there packages to rebuild too ? like extensions, ...
I don't use rpm package extension, maybe ask TV ?
*firefox-ext-adblock-plus *firefox-ext-download-statusbar *firefox-ext-firebug *firefox-ext-foxyproxy *firefox-ext-greasemonkey *firefox-ext-xmarks doesn't work maybe me can all firefox-ext-* ? [root@vosdook ~]# urpmq -fy firefox-ext firefox-ext-adblock-plus-1.3.6-1.mga1.noarch firefox-ext-bugzilla-tweaks-1.10-1.mga1.noarch firefox-ext-download-statusbar-0.9.8-1.mga1.noarch firefox-ext-firebug-1.7.1-1.mga1.noarch firefox-ext-foxyproxy-2.22.6-1.mga1.noarch firefox-ext-greasemonkey-0.9.2-1.mga1.noarch firefox-ext-noscript-2.1.0.3-1.mga1.noarch firefox-ext-xmarks-3.9.9-2.mga1.noarc
most of the extension need to be updated in order to work with firefox 5. the maxVersion from extensions's install.rdf in Mga 1 are: firefox-ext-adblock-plus 4.2a1pre firefox-ext-bugzilla-tweaks 6.0a1 firefox-ext-download-statusbar 4.0.* firefox-ext-firebug 4.0.* firefox-ext-foxyproxy 4.0.* firefox-ext-greasemonkey 4.0.* firefox-ext-noscript 6.0a1 firefox-ext-xmarks 4.2a1pre some extensions must be updated in cauldron also; maxVersion for extensions in cauldron: firefox-ext-adblock-plus 7.0a1 firefox-ext-bugzilla-tweaks 6.0a1 firefox-ext-download-statusbar 4.0.* firefox-ext-firebug 4.0.* firefox-ext-foxyproxy 4.0.* firefox-ext-greasemonkey 7.* firefox-ext-noscript 8.0a1 firefox-ext-xmarks 6.0a1 btw, I wonder if we shouldn't translate the maxVersion from the install.rdf, in rpm's Requires: firefox <= %{firefox_epoch}:maxVersion. e.g. maxVersion = 6.0a1 => Requires: firefox <= %{firefox_epoch}:6.0 regards, Luc
CC: (none) => lmenut
(In reply to comment #10) > is there packages to rebuild too ? like extensions, ... Packages depending on xulrunner and libxulrunner maybe ? I heard that some packages break easily upon update of libxulrunner, but I don't know if it's still true and why.
From bug 2276, please test that myspell dictionaries still work with FF5; according to the OP in that bug, myspell dictionaries aren't picked up with FF5 (in the brief test I did in Cauldron, neither myspell nor hunspell dictionries are picked up from the system).
Depends on: (none) => 2276
Well, as far as launch feedback, goes, i also set this to 3 seconds in systemsettings, and firefox respects that. Also spellchecking seems working here, at least english. On right-click in a text field -> Languages it only shows English / United States of America And i have also set spellchecker.dictionary to de-DE, seems to have no effect anymore. Also since Firefox 3 not myspell is used but hunspell, so what myspell packages are installed is irrelevant. Firefox does not seem to pickup the dictionary anymore. But shouldn't the user need to install additional dictionaries himself? http://support.mozilla.com/en-US/kb/Using%20the%20spell%20checker http://kb.mozillazine.org/Spell_checking
D'mn, wrong bug report. Sorry for the noise.
Additional packages to check beid-middleware esteid-browser-plugin packagekit-browser-plugin parole-browser-plugin
CC: (none) => davidwhodgins
The plugin esteid-browser-plugin was tested on 64-bit system and works fine with Firefox 5.0.1.
CC: (none) => jaanus.ojangu
The plugin esteid-browser-plugin was tested on 32-bit system and works fine with Firefox 5.0.1.
Blocks: (none) => 2090Depends on: 2090 => (none)
Blocks: 2090 => (none)Depends on: (none) => 2090
(In reply to comment #15) > From bug 2276, please test that myspell dictionaries still work with FF5; > according to the OP in that bug, myspell dictionaries aren't picked up with FF5 > (in the brief test I did in Cauldron, neither myspell nor hunspell dictionries > are picked up from the system). System myspell-* dictionaries should work with firefox-5.0.1-1.2 in core/updates_testing.
Tested, but seems englisch dictionary is missing. [doktor5000@mageia1 ~]$ rg myspell | sort myspell-de_AT-1.0.2-30.mga1 myspell-de_CH-1.0.2-30.mga1 myspell-de_DE-1.0.2-30.mga1 myspell-en_US-1.0.2-30.mga1 Of those 4, only the de_* dictionaries get picked up. Would that be correct?
(In reply to comment #22) > Tested, but seems englisch dictionary is missing. > > [doktor5000@mageia1 ~]$ rg myspell | sort > myspell-de_AT-1.0.2-30.mga1 > myspell-de_CH-1.0.2-30.mga1 > myspell-de_DE-1.0.2-30.mga1 > myspell-en_US-1.0.2-30.mga1 > > Of those 4, only the de_* dictionaries get picked up. > Would that be correct? No, all of them should work. I tested installing: myspell-en_US myspell-fr_FR myspell-de_DE and I get: English / United States French German / Germany in firefox spell checking options (accessed by right clicking a misspelled word). What's the output of: ls -l /usr/lib*/firefox-5.0.1/dictionaries ls -l /usr/lib*/firefox-5.0.1/dictionaries/ Also please test in a new FF profile.
[doktor5000@mageia1 ~]$ ls -l /usr/lib*/firefox-5.0.1/dictionaries lrwxrwxrwx 1 root root 31 Jul 30 23:57 /usr/lib64/firefox-5.0.1/dictionaries -> ../../../usr/share/dict/mozilla/ [doktor5000@mageia1 ~]$ ls -l /usr/lib*/firefox-5.0.1/dictionaries/ insgesamt 0 lrwxrwxrwx 1 root root 16 Jun 4 11:08 de-AT.aff -> ../ooo/de_AT.aff lrwxrwxrwx 1 root root 16 Jun 4 11:08 de-AT.dic -> ../ooo/de_AT.dic lrwxrwxrwx 1 root root 16 Jun 4 11:12 de-CH.aff -> ../ooo/de_CH.aff lrwxrwxrwx 1 root root 16 Jun 4 11:12 de-CH.dic -> ../ooo/de_CH.dic lrwxrwxrwx 1 root root 16 Jun 4 11:09 de-DE.aff -> ../ooo/de_DE.aff lrwxrwxrwx 1 root root 16 Jun 4 11:09 de-DE.dic -> ../ooo/de_DE.dic New profile doesn't change anything. Something must have removed the two english dictionaries: [doktor5000@mageia1 ~]$ LC_ALL=C rpm -qV myspell-en_US missing /usr/share/dict/mozilla/en-US.aff missing /usr/share/dict/mozilla/en-US.dic
firefox-5.0.1-1.2 has a pre installation scriptlet which deletes %{_libdir}/firefox-5.0.1/dictionaries, which has nothing to do with /usr/share/dict/mozilla/en-US*
https://bugs.mageia.org/show_bug.cgi?id=2276#c9 Hello, So,with the bug fix "firefox-5.0.1-1.2.mga1.x86_64" it works for me now. The French dictionary is present On right-click in a text field -> Languages -> English / United States of America French And for The StartupNotify, i also set this to 5 seconds in systemsettings, and firefox respects that. It's OK for me and thank you to all the team.
CC: (none) => geiger.david68210
The startup notification should work now correctly with firefox-5.0.1-1.3 in core/updates_testing (without any workaround in systemsettings config).
Extra, it works perfectly. report bug 2276
firefox-ta_LK-5.0.1-1.1.mga1.noarch has a summary of %{langname_ta_LK} interface for Firefox and a description %{langname_ta_LK} localization for Firefox web browser. What language is this for?
ta is the Tamil language, LK is Sri Lanka.
CC: (none) => margot
Hello, firefox-5.0.1-1.3 functions without problem. The French dictionary is well installed. The problem of cursor flickering during a few seconds after the starting of firefox disappeared. Thank You
I forgot to mention, I'm x86 Linux version 2.6.38.8-desktop586-4.mga (iurt@jonund.mageia.org) (gcc version 4.5.2 (GCC) ) #1 SMP Fri Jul 8 01:45:11 UTC 2011 mageia 1
firefox-ext-adblock-plus is updated on testing. the next one will follow
all extension seems now working here (but I don't know why) so for me it's ok (x86_64)
adding qa-bugs in CC so that the QA team still gets the messages and that it appears in saved searches
CC: (none) => qa-bugs
forget what I said in comment 34, with a new user *firefox-ext-download-statusbar *firefox-ext-firebug *firefox-ext-foxyproxy *firefox-ext-greasemonkey *firefox-ext-xmarks does not work (firefox seems had update itself some extension) sorry :(
@dmorgan for firefox-ta_LK Summary : %{langname_ta_LK} interface for Firefox Description : %{langname_ta_LK} localization for Firefox web browser. please fix that
CC: (none) => am2605
ok for me, i for comment #37, i will look. for the extensions, i fixed firefox-ext-download-statusbar locally and it works. i will commit and test the other ones today.
(In reply to comment #18) > Additional packages to check > > beid-middleware done
CC: (none) => maarten.vanraes
Hello, Why not propose updates to thunderbird and firefox with no extensions to these are available more quickly in filing update. The extensions are available as xpi on the mozilla site and work well. Firefox and Thunderbird are already at version 6 and mageia offers only the 4 and 3 for firefox to thunderbird. Thank You
firefox-ta_LK-5.0.1-1.1.mga1.noarch still needs Summary : %{langname_ta_LK} interface for Firefox Description : %{langname_ta_LK} localization for Firefox web browser. to be fixed.
updating to FF 6
Summary: Firefox 5 update => Firefox 6 update
Please test FF from testing, this is firefox 6 and all extension that wasn't working have been updated. firefox-l10n is now fixed regarding firefox-ta_LK.
btw one package still need to be updated ( is on the BS ) is xulrunner.
hello, nothing to report at this time. mageia in 1 32-bit, everything works. plugin ok flash 10.3.r183 rpm ok flash 1.0.6.26 rpm extension: eid 1.0.12 xpi ok Flagfox 4.1.5 xpi ok
*** Bug 2469 has been marked as a duplicate of this bug. ***
Depends on: (none) => 2456
Using Firefox 6.0 as a private rebuild from cauldron since a bit over a week, together with latest Flashplayer 11 beta2, also rebuilt from cauldron. No problems so far, but it feels quite snappier loading new tabs. Will also test the version from updates_testing.
esteid-browser-plugin still needs to be updated for firefox 6.
(In reply to comment #48) > esteid-browser-plugin still needs to be updated for firefox 6. Why?!
CC: (none) => sander.lepik
So,tested on Mageia release 1 (Official) for x86_64 . I have nothing to report ,it's Ok for me. ->For the StartupNotify ,still Ok. ->And for the French dictionary,nothing to report, still OK. ->Also,I test the flash-player-plugin11 in cauldron deposit and it's Ok: flash-player-plugin11-kde-11.0.1.98-0.b2.080811.2.mga2.nonfree flash-player-plugin11-11.0.1.98-0.b2.080811.2.mga2.nonfree Thanks for all the Team Mageia.
Oops! I forgot a question : Is it necessary to uninstall these packages? -lib64xulrunner2.0.1-2.0.1-1.mga1 -lib64xulrunner5.0.1-5.0.1-1.1.mga1 If so, for uninstall them : Why not do it automatically as the package xulrunner ?
Installed ff6 and as far as I can say it works for my needs.
CC: (none) => anaselli
fwiw moonlight does not install in ff6
what do you mean exactly ?
i mean that i downloaded moonlight (mono implementation of silverlight) because i could not watch some tv programs from www.rai.it and after the download, firefox said moonlight cannot be installed because it is not comlatible to firefox 6
(In reply to comment #45) > hello, > > nothing to report at this time. mageia in 1 32-bit, everything works. > > plugin > ok flash 10.3.r183 rpm > ok JAVA 1.0.6.26 rpm JAVA is not flash, of course ........
NoScript 2.1.0.3 is incompatible with firefox 6 (in the stable) (the 2.1.2.6 is in cauldron)
hello, file xulrunner and ibxulrunner, they are already officially in the repository update core testing? I found it in, for example: ftp://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/xulrunner-6.0-1.3.mga1.i586.rpm since 48 hours, but not in others. Is this normal? Thank You
(In reply to comment #49) > (In reply to comment #48) > > esteid-browser-plugin still needs to be updated for firefox 6. > > Why?! In tools/addons/extensions, I get Estonian ID Card PKCS11 module loader is incompatible with Firefox 6.0.
(In reply to comment #59) > In tools/addons/extensions, I get > > Estonian ID Card PKCS11 module loader is incompatible with Firefox 6.0. You are talking about extension (mozilla-esteid), not about plugin. https://bugs.mageia.org/show_bug.cgi?id=2456 Update validated, needs sysadmins to push it. What else is stopping fx update?
i think this is OK now. For moonlight i don't see this blocking but this will need an update soon.
I have updates testing enabled, so I shouldn't be seeing the message about the Estonian ID module being incompatible with Firefox 6. That given, I don't think this should block the release of firefox 6. I also don't think a plugin such as moonlight should block release either. I'm in favour of validating the firefox 6 release.
When firefox-ext-noscript will be updated, I would be the same opinion. :)
firefox-ext-noscript is in testing now.
(In reply to comment #51) > Oops! I forgot a question : > > Is it necessary to uninstall these packages? > > -lib64xulrunner2.0.1-2.0.1-1.mga1 > -lib64xulrunner5.0.1-5.0.1-1.1.mga1 > > If so, for uninstall them : > Why not do it automatically as the package xulrunner ? hello, Can i uninstall these packages or not?
if nothing depend on them yes. We never obsolete old libs ( not only for xulrunner, this is a policy ).
Created attachment 737 [details] Extensions not compatible with firefox 6. Something is wrong. I'm still seeing both noscript and the estonian card reader extensions as being incompatible with firefox 6. The Estonian card reader extension, I would not consider blocking the update for, but the noscript, I consider a blocker.
you used the last rpm for noscript ?
(In reply to comment #67) > Something is wrong. I'm still seeing both noscript and the estonian card > reader extensions as being incompatible with firefox 6. Create a new emtpy profile (firefox -P -no-remote) and test there. To me it seems to be some problem with profiles. Extension itself should be OK (at least esteid one).
I deleted ~/.mozilla, and that cleared up the Estonian card reader extension being shown as imcompatible. For noscript though, it's still showing 2.1.0.3 as disabled. # rpm -qa |grep firefox-ext-noscript firefox-ext-noscript-2.1.0.3-1.1.mga1
I think we need new policy that restricts importing Mozilla extensions that can be downloaded from amo. Latest NoScript is 2.1.2.6, our update is 2.1.0.3. That doesn't make any sense. And it really makes updating proccess hard to happen :/
please test new firefox-ext-noscript
(In reply to comment #71) > I think we need new policy that restricts importing Mozilla extensions that can > be downloaded from amo. Latest NoScript is 2.1.2.6, our update is 2.1.0.3. That > doesn't make any sense. And it really makes updating proccess hard to happen :/ The benefit of installing a rpm package, is that it's system wide, so a system with many users won't have the same plugin/extension installed for every user. The problem, is that firefox will encourage users to update to the latest version, resulting in duplication anyway, and it slows down our testing. I'm in favour of restricting updates that can be downloaded via the get plugins/extensions, and removing those we have.
With the package from the srpm firefox-ext-noscript-2.1.2.3-0.1.mga1.src.rpm installed, all extensions and plugins are now working in firefox 6. For the list of srpm packages that need to be pushed, I have firefox-6.0-1.1.mga1.src.rpm firefox-ext-adblock-plus-1.3.9-1.1.mga1.src.rpm firefox-ext-download-statusbar-0.9.8-1.1.mga1.src.rpm firefox-ext-adblock-plus-1.3.9-1.1.mga1.src.rpm firefox-ext-firebug-1.8.1-1.1.mga1.src.rpm firefox-ext-foxyproxy-3.1.2-1.1.mga1.src.rpm firefox-ext-greasemonkey-0.9.8-1.1.mga1.src.rpm firefox-ext-noscript-2.1.2.3-0.1.mga1.src.rpm firefox-ext-xmarks-4.0.1-1.1.mga1.src.rpm firefox-l10n-6.0-1.1.mga1.src.rpm xulrunner-6.0-1.3.mga1.src.rpm Am I missing any?
no, seems perfect to me. can someone write an advisory ?
Can someone from the sysadmin team push the srpm packages firefox-6.0-1.1.mga1.src.rpm firefox-ext-adblock-plus-1.3.9-1.1.mga1.src.rpm firefox-ext-download-statusbar-0.9.8-1.1.mga1.src.rpm firefox-ext-adblock-plus-1.3.9-1.1.mga1.src.rpm firefox-ext-firebug-1.8.1-1.1.mga1.src.rpm firefox-ext-foxyproxy-3.1.2-1.1.mga1.src.rpm firefox-ext-greasemonkey-0.9.8-1.1.mga1.src.rpm firefox-ext-noscript-2.1.2.3-0.1.mga1.src.rpm firefox-ext-xmarks-4.0.1-1.1.mga1.src.rpm firefox-l10n-6.0-1.1.mga1.src.rpm xulrunner-6.0-1.3.mga1.src.rpm from Core Updates Testing to Core Updates Advisory: Firefox 6 is a maintenance release with approximately 1300 updates to Firefox 5, which is now end of life. For a complete list of updates, see http://www.mozilla.org/en-US/firefox/6.0/releasenotes/buglist.html
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
in progress
update pushed.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Hello, Tested firefox-6.0.1-1.1.mga1 on Mageia release 1 (Official) for x86_64 and for me it's Ok. Nothing to report. ->For the StartupNotify ,still Ok. ->And for the French dictionary,nothing to report, still OK. ->Also,I test the flash-player-plugin11 in cauldron deposit and it's Ok: flash-player-plugin11-kde-11.0.1.98-0.b2.080811.2.mga2.nonfree flash-player-plugin11-11.0.1.98-0.b2.080811.2.mga2.nonfree ->For extension "ext" I don't know because I use "xpi" extension and it works perfectly. A big thank you to D Morgan ,for this great job quickly and efficiently.
CC: boklm => (none)