Bug 14813

Summary:	iceape 2.31 crashes when updating a profile created by 2.30
Product:	Mageia	Reporter:	Christiaan Welvaart <cjw>
Component:	RPM Packages	Assignee:	Christiaan Welvaart <cjw>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	4
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	iceape-2.31-3.mga4.x86_64.rpm	CVE:
Status comment:

Description Christiaan Welvaart 2014-12-16 01:06:07 CET

When a user who started iceape for the first time at version 2.30 launches iceape again after an upgrade to 2.31, the program crashes while showing the *checking plugin compatibility* dialog.

How to reproduce:
1. have iceape-2.30-1 installed
2. make sure $HOME/.mozilla/seamonkey does not exist
3. launch iceape, close it again
4. upgrade to iceape-2.31-3
5. launch iceape

It will now likely crash. Profiles created using earlier iceape versions like 2.26 apparently do not trigger this crash.

Workaround: remove the profile ($HOME/.mozilla/seamonkey) created by version 2.30 .

Reproducible: 

Steps to Reproduce:

Comment 1 Samuel Verschelde 2015-09-21 13:18:08 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 Christiaan Welvaart 2015-09-21 23:31:06 CEST

AFAIK this problem was fixed in the next update.

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