Bug 16250

Summary:	coolreader3 does not save settings
Product:	Mageia	Reporter:	Alex Loginov <loginov_alex>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	brtians1, davidwhodgins, ottoleipala1, sysadmin-bugs
Version:	5	Keywords:	validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	advisory, MGA5-32-OK
Source RPM:	coolreader3	CVE:
Status comment:

Description Alex Loginov 2015-06-29 23:03:38 CEST

Description of problem:
If configure coolreader3, exit from coolreader3 and run again, then new settings are not applied


Version-Release number of selected component (if applicable): coolreader3-3.0.56-4.mga5.i586.rpm


How reproducible: always


Steps to Reproduce:
1. run coolreader3
2. configure coolreader3
3. exit from coolreader3
4. run coolreader3


Reproducible: 

Steps to Reproduce:

Comment 1 Alex Loginov 2015-06-29 23:22:24 CEST

I have uploaded a patched package for Mageia 5.

Suggested advisory:
========================

Updated coolreader3 package fix:

- Added patch, which fix save settings bug
========================

Updated packages in core/updates_testing:
========================
coolreader3-3.0.56-5.mga5.rpm

Source RPM: 
coolreader3-3.0.56-5.mga5.src.rpm

Hardware: i586 => All
Assignee: bugsquad => qa-bugs

Comment 2 Dave Hodgins 2015-07-05 03:40:09 CEST

Advisory committed to svn.

CC: (none) => davidwhodgins
Whiteboard: (none) => advisory

Comment 3 Brian Rockwell 2015-07-07 04:37:18 CEST

MGA5-32-OK

Tested using MGA5-32 running on Gnome.  New version is saving settings properly.

Brian

CC: (none) => brtians1
Whiteboard: advisory => advisory, MGA5-32-OK

Comment 4 Otto Leipälä 2015-07-07 15:28:58 CEST

This can be validated as we test time to get list empty only one arch,i tested it too it works no problems.

Update validated sysadmins push to updates.

Keywords: (none) => validated_update
CC: (none) => ozkyster, sysadmin-bugs

Comment 5 Mageia Robot 2015-07-09 00:03:42 CEST

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0061.html

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