We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2019-11-18 14:31:40 +0200 |
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, not sure how to reliably reproduce, just happens after like 1-2 days of uptime
2 | No.2 Revision |
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, appname (also with qmlscene), not sure how to reliably reproduce, just happens after like 1-2 days of uptime
3 | No.3 Revision |
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)