info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.630: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.630: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.630: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.630: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.630: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.628: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.627: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.627: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.627: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
info xxx Dec xxx 2019 xxx:00:49 filebot: (process:4785): dconf-CRITICAL **: 18:00:49.627: unable to create file '/home/filebot/.cache/dconf/user': Permission denied. dconf will not work properly.
To be honest, this purely spams my logs and has no impact on the outcome--everything gets renamed properly. Just thought I'd mention it, in case this leads to further issues down the line.
dconf is a Gnome service, probably accessed implicitly by Java Swing when rendering the GUI on Linux. Just a Desktop Linux issue. Annoying, but unfortunately not something that can be fixed by me in the FileBot codebase. Might be a problem at runtime later, or it might not.
Then I'm out of ideas. It's something you'd have to fix on your system is though, probably. Maybe googling will yield a solution. That'd be interesting. It seems to be common, for all kinds of applications.
foo wrote: ↑14 Dec 2019, 19:53
Fair enough. It's not a critical bug, so I'll just see if it goes away on its own eventually.
It is weird that it only popped up after upgrading FileBot, though.
That is strange. Maybe there's a reason. Maybe it's just a coincidence. This one does come up in the forums once in a while, but I've never been able to reproduce it myself. Could be anything.