Slackware 15: unable to create directory '/run/user/.../dconf': Permission denied.

cdek · 05-05-2021, 01:53 AM

After a hard reboot I get the following error when trying to launch liferea:

Code:

(liferea:4342): dconf-CRITICAL **: 08:33:11.022: unable to create directory '/run/user/1026/dconf': Permission denied.  dconf will not work properly.

Indeed, in /run/user there's no folder with my UID. After manually creating this folder, I can start liferea again, but now I have to do this every time following a reboot.

Strangely, when I log in with another user, the folder for that user does get created.

I've had this problem before and starting with a fresh home folder temporarily fixed it. Now the problem came back after forcing a shutdown.

So what could have happened and can I fix it properly?

LuckyCyborg · 05-05-2021, 03:31 AM

Quote:

Originally Posted by cdek

After a hard reboot I get the following error when trying to launch liferea:

Code:

(liferea:4342): dconf-CRITICAL **: 08:33:11.022: unable to create directory '/run/user/1026/dconf': Permission denied.  dconf will not work properly.

Indeed, in /run/user there's no folder with my UID. After manually creating this folder, I can start liferea again, but now I have to do this every time following a reboot.

Strangely, when I log in with another user, the folder for that user does get created.

I've had this problem before and starting with a fresh home folder temporarily fixed it. Now the problem came back after forcing a shutdown.

So what could have happened and can I fix it properly?

Did you run the elogind daemon on the init system?

It should manage (dynamically) also that /run directory.

cdek · 05-05-2021, 02:42 PM

Quote:

Originally Posted by LuckyCyborg

Did you run the elogind daemon on the init system?

It should manage (dynamically) also that /run directory.

elogind daemon is running. From what I understand, elogind makes sure that /run/user is created if it doesn't exist.

Code:

start_elogind() {
  if [ -x /lib64/elogind/elogind ]; then
    if [ ! -d /run/user ]; then
      mkdir -p /run/user
    fi

However, the problem is that the subdirectory with the UID, e.g. /run/user/1026, is not created. When another user logs in the system, this folder with their UID does get created.

So I think the problem is not during the boot process, but during login.