Bug 1262561 - moving virt-manager window causes frequent writes with dconf
moving virt-manager window causes frequent writes with dconf
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Cole Robinson
Depends On:
  Show dependency treegraph
Reported: 2015-09-12 16:38 EDT by Miroslav
Modified: 2015-09-13 14:12 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-13 14:12:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
video of the problem (2.66 MB, application/octet-stream)
2015-09-12 16:38 EDT, Miroslav
no flags Details

  None (edit)
Description Miroslav 2015-09-12 16:38:58 EDT
Created attachment 1072757 [details]
video of the problem

Description of problem:
When moving virt-manager window in Gnome, dconf-service is having ~0.5MB/s write operations. It seems that with every pixel move, width and height gets updated.

Version-Release number of selected component (if applicable): 1.2.1

How reproducible:
Reproducible on arch linux with gnome.

Steps to Reproduce:
1. run 'dconf watch /org/virt-manager/'
2. with the same user that ran command in point 1., start virt-manager
3. move the virt-manager window left-right

Actual results:
Significant i/o (~0.5MB/s)

Expected results:
No frequent writes.

Additional info:
VM do not have to be started.
Comment 1 Cole Robinson 2015-09-13 14:12:00 EDT
Thanks for the clear bug report. Indeed we weren't being very smart here, fixed upstream now:

commit bcc13dca3188446e79f20eefce74346846e5ecac
Author: Cole Robinson <crobinso@redhat.com>
Date:   Sun Sep 13 14:07:43 2015 -0400

    virt-manager: Only save window dimensions on app exit (bz 1262561)
    Rather than on every window change event which spams dconf and hits
    the disk repeatedly. The new method is roughly what is suggested by

Note You need to log in before you can comment on or make changes to this bug.