dconf-service performs 20K write-operation to ~/.config/dconf/user on every caps-lock hit

Asked by Andreas Korth

Everytime when I hit the caps-lock key, the “dconf-service” seems to perform a 20K write-operation to the “~/.config/dconf/user”. The file doesn’t increase in size but the date of last change is changing.

I found that out by looking to the output of “iotop -oa” while hitting caps-lock several times, what gave the assumption that the toggle of caps lock (one hit) produces a 20K write operation to disk.

After that I looked for the specific file which dconf-service writes to by using “watch -n 1 "lsof -p <process-id of dconf-service>"”. If you hit caps-lock for multiple times, you will see that there is an operation to the file “~/.config/dconf/user”, indicated by the following lines, which are displayed additionally:

COMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dconf-ser 1904 andreas mem REG 8,1 15587 165262 /home/andreas/.config/dconf/user
dconf-ser 1904 andreas 17u REG 8,1 15587 165269 /home/andreas/.config/dconf/user

I just wonder whether this behaviour is desired or a bug because it may be not necessary. Other users with a similar configuration confirmed this behaviour, users with other distributions and/or desktop environments confirmed that this behaviour doesn’t appear.

Release: Ubuntu 11.10
Arch: amd64
Package: dconf-gsettings-backend
Uname: Linux 3.0.0-12-generic x86_46
Using Unity

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu d-conf Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Achim (ach1m) said :
#1

If it is really a bug I don't know, but I can confirm, that by pressing caps-lock dconf writes ca. 29K to disk.

Revision history for this message
Launchpad Janitor (janitor) said :
#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Andreas Korth (andreaskorth) said :
#3

Currently I have no additional information but the problem still exists.

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Andreas Korth (andreaskorth) said :
#5

Once again and nothing new yet. I wonder that nobody else seems to recognise this question.

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
MaxNegro (maxnegro) said :
#7

why don't you file a bug?

Revision history for this message
Ben Shadwick (benshadwick) said :
#8

I opened a bug because I just discovered this issue myself.

Revision history for this message
johnny lee (johnnyl33-k) said :
#9

This bug still continues/exists on xubuntu 16.04 with dconf-service. It happens on my machine when I open more than one instance of mousepad, the I/O disk write increments and the HDD led doesn't stop blinking, until I close one of the instances of mousepad.