[bug]dconf-CRITICAL error messages in terminal

asked 2019-11-18 14:31:40 +0200

szopin gravatar image

updated 2019-11-24 12:20:39 +0200

screenshot Since around 3.1.0 after using device for some time running apps from terminal often results in dconf-CRITICAL spam as in the screenshot with message:
(process:17385): dconf-CRITICAL **: 13:24:42.949: unable to create file '/run/user/100000/dconf/user': Permission denied. dconf will not work properly.

Still happens on 3.2.0, happens both when using binary harbour-appname and sailfish-qml appname (also with qmlscene), not sure how to reliably reproduce, just happens after like 1-2 days of uptime

EDIT: Found a way to reproduce, seems to be related to having a root privileged app open (like root@tide, though it has to have a file open, or maybe just the keyboard extended is enough, just having it open on the initial menu is not enough to trigger) and switching ambiences (between light and dark does it for sure)

edit retag flag offensive close delete

Comments

1

any details how you start app, is using root privileges, output of ls -la /run/user/100000/dconf could be useful as well

coderus ( 2019-11-18 16:34:30 +0200 )edit

@coderus as user nemo just either qmlsceneing my wip app, but happens same if I start installed apps by binary or sailfish-qml, here's the output:

[nemo@Sailfish ~]$ ls -la /run/user/100000/dconf
total 4
drwx------ 2 nemo privileged 60 2019-11-18 09:53 .
drwx------ 12 nemo nemo 280 2019-11-18 15:43 ..
-rw------- 1 root nemo 2 2019-11-18 09:53 user

szopin ( 2019-11-18 16:46:07 +0200 )edit

Found a way to reproduce, seems to be related to having a root privileged app open (like root@tide, though it has to have a file open, or maybe just the keyboard extended is enough, just having it open on the initial menu is not enough to trigger) and switching ambiences (between light and dark does it for sure)

szopin ( 2019-11-24 12:19:30 +0200 )edit