GNOME Bugzilla – Bug 779342
tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
Last modified: 2017-05-20 05:01:24 UTC
I hope I've filed this under the correct product. tracker-extract: Installed: 1.8.3-0ubuntu0~xenial2 Candidate: 1.8.3-0ubuntu0~xenial2 Version table: *** 1.8.3-0ubuntu0~xenial2 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial This happens every two minutes, 24/7. I can think of now cause. Feb 27 19:30:10 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Feb 27 19:32:08 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Feb 27 19:34:14 localhost tracker-extract.desktop[3603]: (tracker-extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. -rw------- 1 chris chris 2 Feb 27 19:37 user -rw-rw-r-- 1 chris chris 60 Feb 22 15:13 dbus-session drwx------ 2 chris chris 60 Feb 27 19:38 dconf drwx--x--x 2 chris chris 60 Feb 22 15:13 gdm drwx------ 3 chris chris 60 Feb 22 15:14 gnome-shell dr-x------ 2 chris chris 0 Feb 22 15:14 gvfs drwx------ 2 chris chris 40 Feb 22 17:42 gvfs-burn drwx------ 2 chris chris 100 Feb 22 15:14 keyring drwx------ 2 chris chris 80 Feb 22 15:14 pulse drwx------ 3 chris chris 60 Feb 22 15:15 snap.wallpaperdownloader drwxr-xr-x 2 chris chris 80 Feb 22 15:13 systemd drwx------ 3 chris chris 60 Feb 22 15:13 upstart -rw-r--r-- 1 chris chris 5 Feb 22 15:14 upstart-dbus-bridge.3095.pid -rw-r--r-- 1 chris chris 5 Feb 22 15:14 upstart-file-bridge.3095.pid -rw-r--r-- 1 chris chris 5 Feb 22 15:13 upstart-udev-bridge.3095.pid To me, all permissions look correct and I haven't noticed them changing.
Created attachment 346920 [details] gdb backtrace of when problem takes place
Thanks for tracing it! I am attaching here the patch that I'm pushing to Tracker repository, and should fix the issue. Hopefully Ubuntu will pick it up soon :).
Created attachment 346935 [details] [review] tracker-extract: Cache TrackerConfig::max-bytes This is the only setting read from extractor modules. It turns out that under the right circumstances a g_settings_get_value() call can trigger open() calls with readwrite permissions from the caller thread. This is forbidden in extractor threads and triggers warnings like: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Also, since this setting is meaningless to update during tracker-extract lifetime, just drop the g_settings_bind() call, this means the setting is only read once on startup.
Attachment 346935 [details] pushed as e9e7cda - tracker-extract: Cache TrackerConfig::max-bytes
No problem Carlos, glad to be of assistance.
Apologies in advance, I haven't thought about this report I made since it appears to have stopped on March 24th at 1700. The reason I note the date/time here is that /var/log/apt/history.log shows on that day the following updates were made: Upgrade: gir1.2-tracker-1.0:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), tracker-extract:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), libtracker-control-1.0-0:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), tracker-gui:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), tracker-miner-fs:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), tracker:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), libtracker-sparql-1.0-0:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4), thunderbird-locale-en:amd64 (1:45.7.0+build1-0ubuntu0.16.04.1, 1:45.8.0+build1-0ubuntu0.16.04.1), libtracker-miner-1.0-0:amd64 (1.8.3-0ubuntu0~xenial2, 1.8.3+really1.8.0-2ubuntu1~xenial4) I had been running tracker version 1.8.* which was installed when I was using software from the Ubuntu Gnome PPA, 3.20.* however I did a regression back to the 3.18* versions after I removed the PPA. Now if I run apt-cache policy tracker tracker: Installed: 1.6.2-0ubuntu1.1 Candidate: 1.6.2-0ubuntu1.1 However in an attempt to correct the above issue I upgraded to 1.12 from source and tracker --version shows tracker --version Tracker 1.12.0 I'm not sure which version is currently running but I'll have to assume that it's 1.12. Either way the issue I noted in this bug report has stopped as of 1700 on March 24th.