Bug 15034

Summary: Iceape does not correctly execute extensions depending on "seamonkey" in the user agent.
Product: Mageia Reporter: andré blais <andr999>
Component: RPM PackagesAssignee: Christiaan Welvaart <cjw>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal Keywords: Triaged
Version: 4   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: iceape CVE:
Status comment:

Description andré blais 2015-01-13 18:44:01 CET
Iceape replaces "Seamonkey" with "Iceape" in the user agent, and thus will not correctly execute extensions which depend on "Seamonkey" in the user agent.

In my case it was the Colorfultabs extension.
Since Iceape corrects some upstream bugs, as well as being available compiled and localized in 64bits, it is preferable to upstream Seamonkey.

The solution is to add "Seamonkey" to the current user agent string.
(For Colorfultabs, the case doesn't matter, but it may for other extensions.)

As a workaround until Iceape is fixed, the user_agent_switcher can be installed,
then :
1) add a new user agent, by simply adding " seamonkey" to the end of the default string that is presented.  (I called it "+sm".)

2) select the new user agent under tools

3) Under about:config, add using the context menu, the boolean variable
"useragentswitcher.reset.onclose" with the value of false.
If not added, the user agent setting will be erased on start up, thus not allowing activation of the extension(s) affected.

4) This can be tested by help:restart (unselecting "restart with module deactivated").

A quick search didn't locate where Iceape has to be patched.
Manuel Hiebel 2015-01-14 18:45:20 CET

Keywords: (none) => Triaged
Assignee: bugsquad => cjw
Source RPM: (none) => iceape

Comment 1 Samuel Verschelde 2015-09-21 13:19:36 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 2 Marja Van Waes 2015-10-27 06:56:56 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD