Bug 994206

Summary: virt-manager doesn't save preferences
Product: [Fedora] Fedora Reporter: Tomas Smetana <tsmetana>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: berrange, crobinso, hbrock, jforbes, tsmetana, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-15 00:09:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of "virt-manager --debug" none

Description Tomas Smetana 2013-08-06 18:00:44 UTC 
Description of problem:
Any change in the virt-manager's preferences gets lost after virt-manager exits.

Version-Release number of selected component (if applicable):
virt-manager-0.10.0-1.fc19.noarch

How reproducible:
Always

Steps to Reproduce:
1. Start virt-manager
2. Go to "Edit"->"Preferences"
3. Change some setting (e.g. check "Enable system tray icon" or change the default storage format...)
4. Exit virt-manager
5. Start it again and take a look at the preferences

Actual results:
All the changes are lost

Expected results:
The changes remain persistent
Comment 1 Cole Robinson 2013-08-06 18:42:06 UTC 
Things work fine for me.

If you run virt-manager --debug and try to reproduce, do you see any error messages or backtraces? What desktop environment are you using?
Comment 2 Tomas Smetana 2013-08-09 03:53:17 UTC 
Created attachment 784714 [details]
Output of "virt-manager --debug"

This shows where the problem is:
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

Looks like GSettings requires dconf to be installed but doesn't require it.  I suppose this happens in the non-Gnome environments only -- I'm using Xfce.

Thanks for the hint about the debugging output.

I suppose this is NOTABUG from the virt-manager's perspective unless you decide to add hard requirement on the dconf to ensure the settings work as expected.  Up to you.
Comment 3 Cole Robinson 2013-08-15 00:09:14 UTC 
Thanks for the info. Weird that gsettings has that fallback but presumably there's a reason. Other gnome apps don't have a Require on dconf so virt-manager likely shouldn't either. Closing as NOTABUG