Changes in "Configure Kid3..." are NOT saved

Bug #913725 reported by Amr Ibrahim
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kid3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I use Kid3-qt in Ubuntu 11.10 with Unity. When changes are made to "Configure Kid3...", they are saved as long as the program is open. But if I restart the program, settings return to their default.

What I expected to happen:
When I restart the program, changes in settings should be saved.

What happended instead:
No changes are saved, settings are retuned to their default.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: kid3-qt 1.6-2
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Jan 9 13:04:52 2012
ExecutablePath: /usr/bin/kid3-qt
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: kid3
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Urs Fleisch (ufleisch) wrote :

I cannot reproduce this. The configuration is stored in ~/.config/kid3.sourceforge.net/Kid3.conf. Does this file exist in your setup? Is it changed when Kid3 is terminated? Is Kid3 terminated correctly, i.e. not just killed?

Can you start Kid3 with strace and check if the file is opened on termination?

strace -e open kid3-qt 2>&1 | grep Kid3.conf
open("/home/fls/.config/kid3.sourceforge.net/Kid3.conf", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 7
open("/home/fls/.config/kid3.sourceforge.net/Kid3.conf", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 7
open("/home/fls/.config/kid3.sourceforge.net/Kid3.conf", O_RDWR|O_CREAT|O_LARGEFILE|O_CLOEXEC, 0666) = 8
open("/home/fls/.config/kid3.sourceforge.net/Kid3.conf", O_RDWR|O_CREAT|O_LARGEFILE|O_CLOEXEC, 0666) = 8
open("/home/fls/.config/kid3.sourceforge.net/Kid3.conf", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 8

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

(1) Yes, Kid3.conf exists.
(2) Yes, it is changed when Kid3 is correctly terminated.
(3) No, Kid3 is NOT killed.
But here's the thing, when Kid3 is re-opened, the changes in Kid3-qt and Kid3.conf are reverted.
I'll upload these files:
(a) Kid3.conf: default
(b) Kid3_2.conf: after Kid3 is correctly terminated with some changes have been made in "Context Menu Commands"
(c) Kid3_3.conf: after Kid3 is re-opened then terminated without any changes
(d) strace.txt: for case (b)
(e) strace_2.txt: for case (c)

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :
Revision history for this message
Urs Fleisch (ufleisch) wrote :

Thanks for the additional information, now it is clear.
Comparing Kid3.conf and Kid3_2.conf: ID3v1 Text encoding is set to ISO-8859-1, all User Actions/Context Menu Commands are deleted.
Comparing Kid3_2.conf and Kid3_3.conf: The ID3v1 Text encoding is still set to ISO-8859-1, so it was correctly saved and reloaded, but the User Actions/Context Menu Commands have been restored to their default values.

A configuration option is restored when it is missing. This makes it possible to start with a default configuration when the configuration file is missing. In your case, the context menu commands are restored because all of them were deleted (actually you cannot delete them all, so I suppose that you deleted all up to the last and cleared the last entry). You have to keep at least one non-empty entry, and then also the context menu commands will be correctly saved and reloaded when Kid3 is restarted.

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Yes, you're absolutely right. I deleted all the entries to the last one, and I did what you said, I kept at least one non-empty entry and the configurations were saved.

Thanks so much for your support. That problem was making me crazy since Natty 11.04 :D

I think the bug does not exist now (exists only for people who don't know about the "deleting all entries" thing) :D

Revision history for this message
Urs Fleisch (ufleisch) wrote :

This issue is now fixed in Kid3 2.1. All user actions can be deleted.

Changed in kid3 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.