Debian Bug report logs - #732209
unable to create file '/run/user/1000/dconf/user': Permission denied

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Stephen Crowley <scrowley@canaccord.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: (gnome-control-center:11187): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Sun, 15 Dec 2013 11:16:32 -0600

Package: gnome-control-center
Version: 1:3.8.3-4
Severity: important

dist-upgraded to testing, as reported earlier, in gnome Flashback
session the gnome-control-center keyboard shortcuts dont farking work
at all. 

(gnome-control-center:11187): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.

dunno if that msg I just pasted has anything to do with it or they are
seperate bugs

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-control-center depends on:
ii  accountsservice            0.6.34-2
ii  apg                        2.2.3.dfsg.1-2
ii  colord                     1.0.2-1
ii  desktop-file-utils         0.22-1
ii  gnome-control-center-data  1:3.8.3-4
ii  gnome-desktop3-data        3.8.4-2
ii  gnome-icon-theme           3.10.0-1
ii  gnome-icon-theme-symbolic  3.10.1-1
ii  gnome-menus                3.8.0-2
ii  gnome-settings-daemon      3.8.5-2
ii  gsettings-desktop-schemas  3.8.2-2
ii  libaccountsservice0        0.6.34-2
ii  libatk1.0-0                2.10.0-2
ii  libc6                      2.17-97
ii  libcairo2                  1.12.16-2
ii  libcanberra-gtk3-0         0.30-2
ii  libcanberra0               0.30-2
ii  libcheese-gtk23            3.10.1-1sid1
ii  libcheese7                 3.10.1-1sid1
ii  libclutter-gtk-1.0-0       1.4.4-3
ii  libcolord-gtk1             0.1.25-1.1
ii  libcolord1                 1.0.2-1
ii  libcups2                   1.6.4-2
ii  libdbus-glib-1-2           0.100.2-1
ii  libfontconfig1             2.11.0-2
ii  libgdk-pixbuf2.0-0         2.28.2-1+b1
ii  libgl1-mesa-glx [libgl1]   9.2.2-1
ii  libglib2.0-0               2.36.4-1
ii  libgnome-bluetooth11       3.8.1-2
ii  libgnome-desktop-3-7       3.8.4-2
ii  libgoa-1.0-0               3.8.3-2
ii  libgtk-3-0                 3.8.6-1
ii  libgtop2-7                 2.28.5-2
ii  libibus-1.0-5              1.5.4-1
ii  libkrb5-3                  1.11.3+dfsg-3+nmu1
ii  libnm-glib-vpn1            0.9.8.0-5
ii  libnm-glib4                0.9.8.0-5
ii  libnm-gtk0                 0.9.8.4-1
ii  libnm-util2                0.9.8.0-5
ii  libpango-1.0-0             1.36.0-1
ii  libpangocairo-1.0-0        1.36.0-1
ii  libpolkit-gobject-1-0      0.105-4
ii  libpulse-mainloop-glib0    4.0-6+b1
ii  libpulse0                  4.0-6+b1
ii  libpwquality1              1.2.3-1
ii  libsmbclient               2:4.0.13+dfsg-1
ii  libsocialweb-client2       0.25.20-6
ii  libupower-glib1            0.9.23-2+b1
ii  libwacom2                  0.8-1
ii  libx11-6                   2:1.6.2-1
ii  libxi6                     2:1.7.2-1
ii  libxml2                    2.9.1+dfsg1-3

Versions of packages gnome-control-center recommends:
ii  cups-pk-helper         0.2.5-1
ii  gkbd-capplet           3.6.0-1
ii  gnome-online-accounts  3.8.3-2
ii  gnome-user-guide       3.8.2-1
ii  gnome-user-share       3.8.3-1
ii  iso-codes              3.48-1
ii  mesa-utils             8.1.0-2
ii  mousetweaks            3.8.0-1
ii  network-manager-gnome  0.9.8.4-1
ii  ntp                    1:4.2.6.p5+dfsg-3
ii  policykit-1-gnome      0.105-2
ii  rygel                  0.20.1-1
ii  rygel-tracker          0.20.1-1
ii  system-config-printer  1.4.3-1

Versions of packages gnome-control-center suggests:
ii  gnome-screensaver        3.6.1-1
ii  gstreamer1.0-pulseaudio  1.2.1-1
ii  libcanberra-gtk-module   0.30-2
ii  libcanberra-gtk3-module  0.30-2
ii  x11-xserver-utils        7.7+1
ii  xscreensaver             5.23-1

-- no debconf information

Message #10 received at 732209@bugs.debian.org (full text, mbox, reply):

From: merc1984@f-m.fm

To: 732209@bugs.debian.org

Subject: (gnome-control-center:11187): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Sun, 14 Sep 2014 09:24:06 -0700

See, we can report bugs forever and they will never get anywhere.  I
have this bug too.

Debian is just out of control.



-- 
http://www.fastmail.fm - Access all of your messages and folders
                          wherever you are

Message #15 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: gnome-control-center: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Wed, 12 Nov 2014 22:33:52 +0100

Package: gnome-control-center
Version: 1:3.14.1-1
Followup-For: Bug #732209

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Maintainer,

I am still able to reproduce this bug just as it is described in the
forum post: http://forums.debian.net/viewtopic.php?f=10&t=110035, so I
thought I'd report it.

The exact steps I use to repduce this are below.

- - open a terminal 
- - run "gksu gedit" 
- - close gedit

Now try to use the topleft hot corner in GNOME (the Super button) and
you'll get locked.

Temporary workaround:

1. Switch back to console with CTRL+ALT+F1 and log in as root
2. Do a 'chown 1000:1000 /run/user/1000/dconf/user'
3. Switch to the 1000 uid user in the console
4. Do a ' pkill -f /usr/bin/gnome-shell -HUP'
5. Switch back to your GNOME session. 

At the moment I do not know what is causing it. My echo $XDG_RUNTIME_DIR
variable is correctly set to /run/user/1000. 

Please let me know once you find the fix.

Thanks and regards,
Miklos

- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-control-center depends on:
ii  accountsservice            0.6.37-3+b1
ii  apg                        2.2.3.dfsg.1-2
ii  colord                     1.2.1-1+b1
ii  desktop-file-utils         0.22-1
ii  gnome-control-center-data  1:3.14.1-1
ii  gnome-desktop3-data        3.14.1-1
ii  gnome-icon-theme           3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-settings-daemon      3.14.1-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  libaccountsservice0        0.6.37-3+b1
ii  libatk1.0-0                2.14.0-1
ii  libc6                      2.19-12
ii  libcairo-gobject2          1.14.0-2.1
ii  libcairo2                  1.14.0-2.1
ii  libcanberra-gtk3-0         0.30-2.1
ii  libcanberra0               0.30-2.1
ii  libcheese-gtk23            3.14.1-1
ii  libcheese7                 3.14.1-1
ii  libclutter-1.0-0           1.20.0-1
ii  libclutter-gtk-1.0-0       1.6.0-1
ii  libcolord-gtk1             0.1.25-1.1+b1
ii  libcolord2                 1.2.1-1+b1
ii  libcups2                   1.7.5-7
ii  libdbus-glib-1-2           0.102-1
ii  libfontconfig1             2.11.0-6.1
ii  libgdk-pixbuf2.0-0         2.31.1-2+b1
ii  libgl1-mesa-glx [libgl1]   10.3.2-1
ii  libglib2.0-0               2.42.0-2
ii  libgnome-bluetooth13       3.14.0-1
ii  libgnome-desktop-3-10      3.14.1-1
ii  libgoa-1.0-0b              3.14.1-1
ii  libgoa-backend-1.0-1       3.14.1-1
ii  libgrilo-0.2-1             0.2.11-2
ii  libgtk-3-0                 3.14.4-2
ii  libgtop2-7                 2.28.5-2+b1
ii  libibus-1.0-5              1.5.9-1
ii  libkrb5-3                  1.12.1+dfsg-11
ii  libmm-glib0                1.4.0-1
ii  libnm-glib-vpn1            0.9.10.0-3
ii  libnm-glib4                0.9.10.0-3
ii  libnm-gtk0                 0.9.10.0-2
ii  libnm-util2                0.9.10.0-3
ii  libpango-1.0-0             1.36.8-2
ii  libpangocairo-1.0-0        1.36.8-2
ii  libpolkit-gobject-1-0      0.105-7
ii  libpulse-mainloop-glib0    5.0-13
ii  libpulse0                  5.0-13
ii  libpwquality1              1.2.3-1
ii  libsmbclient               2:4.1.13+dfsg-2
ii  libsoup2.4-1               2.48.0-1
ii  libupower-glib3            0.99.1-3
ii  libwacom2                  0.8-1
ii  libx11-6                   2:1.6.2-3
ii  libxi6                     2:1.7.4-1+b1
ii  libxml2                    2.9.1+dfsg1-4

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime               2.9.2-1
ii  cups-pk-helper                 0.2.5-2+b1
ii  gkbd-capplet                   3.6.0-1
ii  gnome-online-accounts          3.14.1-1
ii  gnome-user-guide               3.14.1-1
ii  gnome-user-share               3.14.0-1
ii  iso-codes                      3.57-1
ii  libnss-myhostname              0.3-9
ii  lxsession [policykit-1-gnome]  0.5.1-1
ii  mesa-utils                     8.2.0-1
ii  mousetweaks                    3.12.0-1
ii  network-manager-gnome          0.9.10.0-2
ii  policykit-1-gnome              0.105-2
ii  realmd                         0.15.1-1+b2
ii  rygel                          0.24.1-1
ii  system-config-printer          1.4.6-1

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.4.3-2
ii  libcanberra-gtk-module   0.30-2.1
ii  libcanberra-gtk3-module  0.30-2.1
ii  x11-xserver-utils        7.7+3+b1

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUY9I3AAoJECII8s4/zqDTKMkIAJ90reKn8g04SwhRE18ca2lo
Sbdm5B8dj4TAkdgk5Wd4cfN10PXx9U15LiHB8idO09blwdxX4AuwaYBEHlgebPfG
LaTOIjk4gQiPMiFaqh5UMZHwFKvBgjasbCzja4EOZjKypq31mzKcRSgxjKQi7M0U
xRwjCmF11OOR0LFICKOavFFqWApCha5UCiXJxVi26QRqi9zBqcEMPL2W0sK3Tj4H
1b4UfCkq7RRkTOYTGd3nWCnCNZWOzqpKHCo1mFy3KfJdyClTWLwIMctV0g4GlDfH
b6TGTWtnv2Dnl03VU6FicJRLXO8hZLLISA8L02EetifbsPH0c9wBc02Bx21pm90=
=V4H+
-----END PGP SIGNATURE-----

Message #20 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: 732209@bugs.debian.org, control <control@bugs.debian.org>

Cc: Miklos Quartus <inbox@miklos.info>, Stephen Crowley <scrowley@canaccord.com>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Wed, 26 Nov 2014 15:39:15 +0300

reassign 732209 libpam-systemd 215-6
thanks


Hi,

Messing with /run/user/1000/dconf/user ownership seems to be the work
of libpam-systemd - somewhat similar things had been happening before,
as reported in [1] (and the merged reports).

See also another bug report [2] about the similar issue.


[1] https://bugs.debian.org/731300
[2] https://bugs.debian.org/766464

Message #31 received at 732209@bugs.debian.org (full text, mbox, reply):

From: "Crowley, Stephen" <SCrowley@canaccordgenuity.com>

To: Vlad Orlov <monsta@inbox.ru>, "732209@bugs.debian.org" <732209@bugs.debian.org>

Cc: Miklos Quartus <inbox@miklos.info>, "crowlogic@nym.hush.com" <crowlogic@nym.hush.com>

Subject: RE: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Wed, 26 Nov 2014 21:31:58 +0000

Curious, why am I  being CC'ed on ths? Not that I am upset about anything... also, hi Linas, long time no chat, is this some attempt to get me back as an active member of the Debian project? :)

--Stephen
________________________________________
From: Vlad Orlov [monsta@inbox.ru]
Sent: Wednesday, November 26, 2014 6:39 AM
To: 732209@bugs.debian.org; control
Cc: Miklos Quartus; Crowley, Stephen
Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

reassign 732209 libpam-systemd 215-6
thanks


Hi,

Messing with /run/user/1000/dconf/user ownership seems to be the work
of libpam-systemd - somewhat similar things had been happening before,
as reported in [1] (and the merged reports).

See also another bug report [2] about the similar issue.


[1] https://bugs.debian.org/731300
[2] https://bugs.debian.org/766464

Message #36 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: "Crowley, Stephen" <SCrowley@canaccordgenuity.com>

Cc: 732209@bugs.debian.org

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 27 Nov 2014 10:56:46 +0300

Hi,

I just decided to nofity all the participants here, in case
this new info might be interesting or useful  :)

Message #41 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: libpam-systemd: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Wed, 03 Dec 2014 21:39:43 +0100

Package: libpam-systemd
Version: 215-7
Followup-For: Bug #732209

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Vlad , et al.,

Thanks for the clarification about sending references to earlier cases,
when this bug surfaced. Now, I am sending a follow-up for this bug as it
still happens in the latest up-to-date Jessie. I can still reproduce it
at least in two different ways. See the steps how to reproduce it below.

Pre-requisites.
a. have a fat32 formatted usb flash drive ready
b. your user should be just a regular user on your system without root
privileges

Steps to reproduce.
1. Log in with your regular user into your GNOME session.
2. Open up a root terminal by typing Windows key -> (type 'root' in the
search bar and hit Enter to the Root Terminal icon)
3. Type 'watch -n 1 ls -l /run/user/1000/dconf/user' as root to see when
the permission of the file changes automatically. Instead of '1000',
replace the number of your login user account. In my case it's 1000.
4. Open up the 'dconf Editor' by typing the Windows key -> (type 'dconf'
in the search bar and hit Enter to the 'dconf Editor' icon.
5. Close the dconf Editor.
6. See the file permission's change in the root terminal window.

When this happens, it locks your entire GNOME session rendering your
graphical user interface unusable. Unfortunately, I don't have a patch
to fix it. 

Vlad, 
BTW, this only happens with GNOME sessions. With other window managers
(e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a
systemd bug, rather it's related to GNOME. Do you agree to reassign this
bug against either the 'gnome-session' or the 'gnome-shell' package?

The related package versions I am still able to reproduce this bug are:

gnome-session	3.14.0-2
gnome-desktop-environment	1:3.14+1
gnome-shell	3.14.1-1

Kind regards,
Miklos


- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-systemd depends on:
ii  dbus               1.8.12-1
ii  libc6              2.19-13
ii  libcap2            1:2.24-6
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  multiarch-support  2.19-13
ii  systemd            215-7
ii  systemd-sysv       215-7

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUf3UFAAoJECII8s4/zqDTrT8IAKWJCmn8DucyL4jnet/Bh1M9
7BBxzAoCMTHOEE8Xb4/+IK8vjFPJeGmbnIsMGMpJ7fP7vcilPX8zMZrXCwTFyYac
N1+zZTEZI6hzLSWsD0wEvO0AM5OTyTOX53TgobIUCuuu/ObWiNqSls6lcmMxmro0
FWFPHQ5hobIeybhCcs6XmM9YShoZZvXNxIMCIN6Cf5GB95kiLFqaQKDqqxO0tMDG
6Gqv52jb4nJMG+wffS0J+2opQyiQoFNfkM4weGXE68PFYuK/ZSKDwV4fNR6SFX8/
3tFWHRBOKkRA4eK3AZmXgdYvoa8jqyW439J6TnjDfXoCh1nqCc3dXjlXoO+MYG0=
=bd/C
-----END PGP SIGNATURE-----

Message #46 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Miklos Quartus <inbox@miklos.info>

Cc: 732209@bugs.debian.org, Linas Vepstas <linasvepstas@gmail.com>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 04 Dec 2014 14:13:57 +0300

Hi,

> BTW, this only happens with GNOME sessions. With other window managers
> (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a
> systemd bug, rather it's related to GNOME. Do you agree to reassign this
> bug against either the 'gnome-session' or the 'gnome-shell' package?

No, I don't agree. I can reproduce it 100% in MATE desktop environment and
also in Cinnamon, see [1]. I'm actually thinking of merging that bug report with
this one.

Please read the comments from Linas Vepstas there, they confirm that it's not
a desktop environment or a text editor itself that causes it. Also, systemd had
been messing up the ownership of /run/user/1000/dconf/user in the past, see [2].


[1] https://bugs.debian.org/766464
[2] https://bugs.debian.org/731300

Message #61 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: 732209@bugs.debian.org, control <control@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Fri, 05 Dec 2014 15:31:28 +0300

found 732209 217-3
thanks


Also tried systemd 217-3 from Experimental, the issue is still present.

Message #68 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Vlad Orlov <monsta@inbox.ru>, 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Fri, 05 Dec 2014 18:41:01 +0100

[Message part 1 (text/plain, inline)]

control: tags -1 moreinfo unreproducible

Am 05.12.2014 um 13:31 schrieb Vlad Orlov:
> found 732209 217-3
> thanks
> 
> 
> Also tried systemd 217-3 from Experimental, the issue is still present.

I cannot reproduce this issue with 215-8

Can you please provide step-by-step instructions, how to setup the test
environment (which packages are installed, which environment is running)
and which commands to use to trigger the problem.

The mentioned examples like running "gksu gedit" or opening a root
terminal and starting dconf-editor doesn't trigger the issue here when
running it under GNOME (and with systemd being PID 1).

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #75 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Sat, 06 Dec 2014 22:15:57 +0100

Package: libpam-systemd
Version: 215-7
Followup-For: Bug #732209

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Maintainer,

I can still reproduce the problem. 

> Can you please provide step-by-step instructions, how to setup the test
> environment (which packages are installed, which environment is running)
> and which commands to use to trigger the problem.

Let me give you a few details about my environment in the hopes that you
(or someone else) will be able to reproduce it. I'd be grateful if you
could provide a few pointers how to get rid of this annoying bug.

1. Init system installed on my system is systemd.
root@localhost:~# ps -p1 f
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:03 /sbin/init
root@localhost:~# ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Nov 28 07:37 /sbin/init -> /lib/systemd/systemd
root@localhost:~#

2. This happens under GNOME session after you log in via gdm3 as a
regular (non-root) user. Related package versions are as below.

gnome-shell:	3.14.1-1
gnome-session: 3.14.0-2
gnome-core:	1:3.14+1
gnome-desktop-environment: 	1:3.14+1
gdm3:	3.14.1-3

3. It is worth noting that I have a gvfsd-fuse and a tmpfs line showing
up in my /etc/mtab. I am not sure they're related.

root@localhost:~# grep "/run/user/1000" /etc/mtab
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=394008k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0

4. My APT package manager is completely healthy and has got no
failed/broken packages, all repositories are used from official Debian
mirrors and are brought up-to-date to Jessie. 

"
deb http://ftp.hu.debian.org/debian jessie main contrib non-free
deb http://security.debian.org/ stable/updates main contrib non-free
"

I also tried with a clean, newly created user (i.e. test) and the
problems happens there, too. So this clears me of any user-specific
tweaks. Besides, my GNOME session works completely well. I hope the
above helps. Let me know if you need anything else.

Regards,
Miklos


- -- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-systemd depends on:
ii  dbus               1.8.12-1
ii  libc6              2.19-13
ii  libcap2            1:2.24-6
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  multiarch-support  2.19-13
ii  systemd            215-7
ii  systemd-sysv       215-7

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUg3IIAAoJECII8s4/zqDT8BkH/3d7xbFS4QoC8Vc9wnPtmskw
etYqiiu7G3JrAhQPSnd1/JKlcLvyglbaOoIKny/5FvCRusn36gfLhYQ6z3Chi9Uz
S/qk8z/xFGjHVwi2mJjCegZTdxrYn4BLcF8s7BLbIq8k7eTYGZexU91Hx1RUMPd8
ERzS0eok7wFJQeJol+ISJDjtEHAoV7iXfWlO1O9ZztSHn20FVMalnr/sS1DaGzGF
XBOFbcUoAXk7EtaH6gJ1WZe2uMsmm0iMv4tGDqn8rgGN2DXYzL5VWNmk1Fe2FZUL
VwYvFE9x1mtvS3KzoXL/X2/u2pi5ZmguqGObkokaDT2WYEysc77Pm1a9xNC602c=
=to91
-----END PGP SIGNATURE-----

Message #80 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Michael Biebl <biebl@debian.org>, 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Sun, 07 Dec 2014 18:42:36 +0300

Hi,

> Can you please provide step-by-step instructions, how to setup the test
> environment (which packages are installed, which environment is running)
> and which commands to use to trigger the problem.

The best way I know is to run MATE's text editor (pluma) via gksu, as
I've described in [1]. I ran it under MATE desktop environment, but it
will probably trigger the issue under other DEs as well.

You can easily set up a minimal MATE environment by installing the
mate-desktop-environment-core meta-package. After that, only installing
pluma is needed.

Please also look at the comments by Linas Vepstas in that bug report.


[1] https://bugs.debian.org/766464

Message #85 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <qmi@upcmail.hu>

To: 732209@bugs.debian.org

Date: Tue, 30 Dec 2014 22:47:30 +0100

Content-Type: multipart/mixed; boundary="===============1764408977=="
MIME-Version: 1.0
From: Miklos Quartus <inbox@miklos.info>
To: Debian Bug Tracking System <732209@bugs.debian.org>
Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied
Message-ID: <20141230213601.24606.52599.reportbug@localhost>
X-Mailer: reportbug 6.6.1
Date: Tue, 30 Dec 2014 22:36:01 +0100

This is a multi-part MIME message sent by reportbug.


--===============1764408977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: libpam-systemd
Version: 215-8
Followup-For: Bug #732209

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear GNOME Maintainer,

Here's some progress on the bug I am still experiencing in Jessie. I
found that this bug can only be reproduced in a GNOME session if the
root terminal window is in focus. 

So to the steps to reproduce the bug - if you have not managed to so far
- - slightly changes as below. 

1. Get a root terminal window running and make sure it's in focus (in a
GNOME session hit the Super key, type 'root ..' in the search bar and
hit <Enter> to the run the app.

2. Run the 'Files' file manager app (not the PCManFM or other) or the
'dconf Editor' app (hit the Super key, type the app name) and once the
window is active, do some one simple action (i.e. click on a menu item).

3. Close the application window.

4. Watch the file permission changes -> /run/user/1000/dconf/user which
effectively locks up your GNOME session.

At the moment I don't have any patch or further information as to what
might be the root cause leading up to this issue. I am using the latest
up-to-date Jessie from official Debian repositories. It is also worth
mentioning that I am using the GNOME minimalist installation, I have
the 'core-only' as described on https://wiki.debian.org/Gnome . (i.e. I
don't have the gnome-desktop-environment package installed, I have the
extra stuff :-/). This way I am perfectly happy user of Debian and GNOME.

gnome-session: 3.14.0-2
gnome-shell: 3.14.2-3
gnome-core: 1:3.14+3
gnome-desktop-environment: not installed
gnome-desktop: not installed

Inform me of any progress.

Kind regards,
- --
Miklos


- -- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus               1.8.12-3
ii  libc6              2.19-13
ii  libcap2            1:2.24-6
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  multiarch-support  2.19-13
ii  systemd            215-8
ii  systemd-sysv       215-8

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUoxqyAAoJECII8s4/zqDTrKIIALGo5P7P5xsgGweHcxBQr4Zu
e6HOiR2Sc91xudDP+Tty/iXAciG01fRi1vrcc6rlAgTa44/+RC5UJTY5Ar8IL7xC
G5w7ChYd+y9gWlMHzLAi/eiC37UFW5HQzp1bsvTWI8y9p5l/lWyP7/56eiKIzNEj
+6kLK99EJ92qXscC45SFggiT8871d7y9wW52HbFZHoMzsJfPAel57fMDiupvxZut
ndO8mSkUDCD8xn6fpks2Vu2PYhP7NO/w6ip2XYHz/axyj51Wz4y2lQnAFgAS6Twk
ubzDQeH0ub6iu7ILkoDImuLlCRAYOR09H7ufCOWDhHDJcybpk3fs+qKxVMf6lyA=
=4tzM
-----END PGP SIGNATURE-----

--===============1764408977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="gnome-shell-errormsg.txt"

Dec 30 22:13:12 localhost gnome-session[21484]: (gnome-settings-daemon:21555): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

--===============1764408977==--

Message #90 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Goonie Windy <monsieur.goonie@gmail.com>

To: 732209@bugs.debian.org

Subject: I have exact same bug under jessie as well as sid

Date: Sun, 11 Jan 2015 18:49:59 +0100

[Message part 1 (text/plain, inline)]

for some reason /run/user/1000/dconf/user gets owned by root instead of
1000 causing a gnome freeze

[Message part 2 (text/html, inline)]

Message #99 received at 732209@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

To: Miklos Quartus <inbox@miklos.info>

Cc: 732209@bugs.debian.org

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Wed, 21 Jan 2015 15:16:28 +0100

> 1. Init system installed on my system is systemd.
> root@localhost:~# ps -p1 f
> PID TTY      STAT   TIME COMMAND
>   1 ?        Ss     0:03 /sbin/init

Well, that's a bit weird. On my systemd system, it looks like this.

glaubitz@z6:~> ps -p1 f
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:54 /lib/systemd/systemd --system --deserialize 20
glaubitz@z6:~>

What does systemctl | head say?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Message #104 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Sun, 25 Jan 2015 00:08:57 +0100

Package: libpam-systemd
Version: 215-8
Followup-For: Bug #732209

> What does systemctl | head say?

systemctl | head 
UNIT                                                                                                LOAD   ACTIVE SUB       DESCRIPTION
proc-sys-fs-binfmt_misc.automount                                                                   loaded active running   Arbitrary Executable File Formats File System Automount Point
sys-devices-pci0000:00-0000:00:02.0-backlight-acpi_video0.device                                    loaded active plugged   /sys/devices/pci0000:00/0000:00:02.0/backlight/acpi_video0
sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2dLVDS\x2d1-intel_backlight.device             loaded active plugged   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
(...)

Also, see below:

"
root@localhost:~# ps -p1 -o pid,cmd,comm
  PID CMD                         COMMAND
    1 /sbin/init                  systemd
root@localhost:~# type systemd
systemd is /bin/systemd
root@localhost:~# readlink /bin/systemd
/lib/systemd/systemd
root@localhost:~#
"

Apparently, systemd is in charge. 

Regards,
Miklos

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus               1.8.12-3
ii  libc6              2.19-13
ii  libcap2            1:2.24-6
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  multiarch-support  2.19-13
ii  systemd            215-8
ii  systemd-sysv       215-8

libpam-systemd recommends no packages.  
libpam-systemd suggests no packages.

-- no debconf information

Message #109 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Miklos Quartus <inbox@miklos.info>

Cc: 732209@bugs.debian.org

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Mon, 16 Feb 2015 13:36:26 +0300

Hi Miklos,


For some reason, now I'm having trouble reproducing the ownership
change of /run/user/1000/dconf/user to root using my method from [1].

I've tried it on two Jessie installations, one has traditional sysvinit and
another has systemd-sysv. Both systems are fully updated, the version
of systemd is 215-11.

Can you confirm whether your method (in Gnome session) still works
in the current Jessie or not? Does /run/user/1000/dconf/user get owned
by root?


[1] https://bugs.debian.org/766464

Message #114 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Mon, 16 Feb 2015 20:37:26 +0100

Package: libpam-systemd
Version: 215-11
Followup-For: Bug #732209

Hi Vlad,

Yes, I am still able to reproduce this bug in my GNOME session in my
latest Jessie, indeed. After opening the root terminal window and in
focus, I can use three ways to trigger:

1. In a standar user terminal open a shell and run "gksu gedit".
2. Type Super key and search dconf-Editor and run it.
3. Type Super key and search for Files file manager and run it. 

I do not use MATE so I don't know how that works. My system otherwise is
working fine. I don't have access to unstable or experimental distro, so
I cannot test it. 

My system is a healthy Debian Jessie 8 with systemd-sysv:

"
root@localhost:~# systemctl status sysinit.target
● sysinit.target - System Initialization
   Loaded: loaded (/lib/systemd/system/sysinit.target; static)
   Active: active since Sun 2015-02-15 18:57:11 CET; 1 day 1h ago
     Docs: man:systemd.special(7)
root@localhost:~# date
Mon Feb 16 20:31:46 CET 2015
root@localhost:~# cat /etc/debian_version 
8.0
"

gnome-session: 	3.14.0-2
libpam-systemd: 	215-11
gnome-shell: 		3.14.2-3+b1

Package gnome-desktop-environment is *not* installed. 

Regards,
--
Miklos


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus               1.8.12-3
ii  libc6              2.19-13
ii  libcap2            1:2.24-6
ii  libpam-runtime     1.1.8-3.1
ii  libpam0g           1.1.8-3.1
ii  multiarch-support  2.19-13
ii  systemd            215-11
ii  systemd-sysv       215-11

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

Message #119 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Miklos Quartus <inbox@miklos.info>

Cc: 732209@bugs.debian.org

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Tue, 17 Feb 2015 10:50:07 +0300

Weird... today I'm able to reproduce it with "gksu pluma" again, 100%.
I'm out of clues :-/

Message #124 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Miklos Quartus <inbox@miklos.info>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Fri, 17 Apr 2015 15:01:04 +0200

[Message part 1 (text/plain, inline)]

On Mon, 16 Feb 2015 20:37:26 +0100 Miklos Quartus <inbox@miklos.info> wrote:
> Package: libpam-systemd
> Version: 215-11
> Followup-For: Bug #732209
> 
> Hi Vlad,
> 
> Yes, I am still able to reproduce this bug in my GNOME session in my
> latest Jessie, indeed. After opening the root terminal window and in
> focus, I can use three ways to trigger:
> 
> 1. In a standar user terminal open a shell and run "gksu gedit".
> 2. Type Super key and search dconf-Editor and run it.
> 3. Type Super key and search for Files file manager and run it. 

Using GNOME here as well. I'm not able to reproduce the problem with the
steps you outlined.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #129 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Tycho Lürsen <tycholursen@gmail.com>

To: 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Fri, 17 Apr 2015 16:56:13 +0200

I'm able to reproduce this bug using Mate.
In my case it always boils down to right-clicking a file or dir and try 
to delete it in caja (bypasing the 'prullenbak' in Dutch, probably 
something like trash bin in English), then caja crashes and 
/run/user/1000/dconf/user is owned by root.
Timestamp of /run/user/1000/dconf/user (owned by root) is usualy at 
least 2 hours before the crash occurs, strange (UTC? my timezone differs 
2 hours with utc).

Typical this crash happens when doing this right-click and delete in 
caja more the 10 times. Don't know if that means anything though...

Op 17-04-15 om 15:01 schreef Michael Biebl:
> On Mon, 16 Feb 2015 20:37:26 +0100 Miklos Quartus <inbox@miklos.info> wrote:
>> Package: libpam-systemd
>> Version: 215-11
>> Followup-For: Bug #732209
>>
>> Hi Vlad,
>>
>> Yes, I am still able to reproduce this bug in my GNOME session in my
>> latest Jessie, indeed. After opening the root terminal window and in
>> focus, I can use three ways to trigger:
>>
>> 1. In a standar user terminal open a shell and run "gksu gedit".
>> 2. Type Super key and search dconf-Editor and run it.
>> 3. Type Super key and search for Files file manager and run it.
> Using GNOME here as well. I'm not able to reproduce the problem with the
> steps you outlined.
>
>
>

Message #138 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Miklos Quartus <inbox@miklos.info>, Tycho Lürsen <tycholursen@gmail.com>

Cc: 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Thu, 28 May 2015 14:31:05 +0300

Hi,

Can you please try the patch for systemd from [1]
and check if the issue is still present?


[1] https://github.com/linuxmint/systemd/commit/f7ab85f1e1169ac1598dfc1fba1c01063840b3c5.patch

Message #147 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Daryl King <allnatives.online@gmail.com>

To: 732209@bugs.debian.org

Subject: I tried the workaround in message #15 and got this...

Date: Sat, 20 Jun 2015 00:42:33 +1000

[Message part 1 (text/plain, inline)]

(I haven't chimed-in here at bugs.debian before but I would like to help
out with this bug)
I tried workaround in message #15 and then made sure my echo
$XDG_RUNTIME_DIR variable was correctly set to /run/user/1000. I then
proceeded to open my editing programmes with gksu.
"gksu nautilus" resulted in this log:
Jun 20 00:34:12 debiandog dbus[608]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service'
Jun 20 00:34:12 debiandog dbus[608]: [system] Successfully activated
service 'org.freedesktop.hostname1'

"gksu gedit" resulted in this log:
Jun 20 00:36:05 debiandog gnome-session[1699]: Window manager warning:
Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for
0x2600f6a (Unsaved Do)

sometimes followed by a block of 5 or 6 repetitive messages :
Jun 20 00:13:11 debiandog org.gnome.Terminal[1743]:
(gnome-terminal-server:3027): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.
Jun 20 00:13:11 debiandog org.gnome.Terminal[1743]:
(gnome-terminal-server:3027): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.
Jun 20 00:13:11 debiandog org.gnome.Terminal[1743]:
(gnome-terminal-server:3027): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.
Jun 20 00:13:11 debiandog org.gnome.Terminal[1743]:
(gnome-terminal-server:3027): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.
Jun 20 00:13:11 debiandog org.gnome.Terminal[1743]:
(gnome-terminal-server:3027): dconf-CRITICAL **: unable to create file
'/run/user/1000/dconf/user': Permission denied.  dconf will not work
properly.

(of course these are the problematic messages that, before I used the
workaround, ran out of control and filled the syslog and resulted in a
locked-up gnome.

I hope this helps towards a fix..

[Message part 2 (text/html, inline)]

Message #152 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Daryl King <allnatives.online@gmail.com>

To: 732209@bugs.debian.org

Subject: update to my last post

Date: Wed, 24 Jun 2015 11:16:41 +1000

[Message part 1 (text/plain, inline)]

It seems that, for me anyway, this problem may have been caused by an
incorrectly compiled Nvidia Proprietary Driver (which HAS to be used due to
my particular hardware). I haven't had any of these dconf permission errors
since recompiling.

[Message part 2 (text/html, inline)]

Message #157 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Wiktor Pekalski <wiktor.p1991@gmail.com>

To: 732209@bugs.debian.org

Subject: systemd, gnome, gnome-settings-daemon

Date: Thu, 27 Aug 2015 22:28:38 +0200

[Message part 1 (text/plain, inline)]

Hello,

Sorry for my English - it's not my native language.

I can reproduce bug in 3 machines:

1. PC: C2D E6400 with GF 8400GS (PCIE)
2. Notebook: i5-2430M with GF 520MX.
3. VMWare Player 7 on notebook with W8.1, i5-5200U, Intel HD (no NV GPU)

File: debian-8.1.0-amd64-CD-1.iso (stable)

In my case (the same install procedure for 3 machines):
Debian 8.1 installed from USB (created by RUFUS, on VM directly from ISO).
What I do:
1. Install Debian without graphic desktop.
2. Login.
3. Install sysvinit, sysvinit-core, sysvinit-utils.
4. Reboot.
5. Install MC.
6. Remove CD from repo list in /etc/apt/sources.lst with mcedit.
7. Remove systemd with --purge and --auto-remove.
8. Ban package 'systemd-sysv' with local-pin-init file (as described in
update guide) with mcedit.
9. Install gnome.
10. Reboot.
11. Login as regular user (user name: u or user).

What I know:

1. I don't think, that all above needs to be done. Other users report bug
on standard installation (with systemd).

2. It's hard to reproduce bug because (probably?) there must be an issue
with gnome menu to make this bug "working".
How to find out, if machine has a bug?
When you run game Nibbles, there is no menu there! The same thing for
keyboard layout, other games and apps (but not all - maybe its QT, GTK
issue etc).

Example:
http://i.imgur.com/RLedPOM.png

3. Gnome hangs only when you're using root permission with "remember for
this session".

4. Maybe (I',m not sure) there must be autologin option turned on.

5. It works (probably) only on standard GNOME (not gnome classic, not gnome
wayland).

6. Removing
'/usr/lib/gnome-settings-daemon-3.0/keyboard.gnome-settings-plugin' (as
described in web) will NOT fix that.

How to reproduce? It's quite easy:
1. After login, run root terminal (enter root password, check remember for
session - here is  your strange root permission/uid for the file created).
Probably now you could close terminal, but let it stay on.
2. Open Nibbles and click coupe times in place, where menu should be, move
window, click once again. Close it.
3. Open language list from system bar, click show layout. Should be menu
there? Probably yes. Click couple times, move window, close.
4. Click on terminal.
5. Click top left corner (superbutton/supermenu or as you called)
6. And it's gene...

Animation is stopped (for example file download/GDebi progress bar) or
whatever you do in background, mouse working.
I can do Ctrl+Alt+F(x) do open another tty. I can log on as root.
In HTOP I see high cpu usage by gnome-settings-daemon. Stopping this
process don't change anything - gnome not responding.
I also see dconf errors described above.

Temporary solution is do this:
1. (optionally?) remove '/run/user/1000/dconf/user' file
2. kill gnome-shell process.
Then switch to Ctrl+Alt+F7, wait few seconds and gnome start working.

Extra info:
In gnome-tweak-tool I've switched on minimize/maximize buttons.
In theme section, in last position "shell theme" select box is empty, and
there is red exclamation sign next to the select box.

Bug is also in MATE an Cinnamon, because both has systemd in depend tree
(like gnome) - LXDE/XFCE dont use it, so both are safe. Need proof?

When you try to use this instruction (with systemd lock):
https://community.spiceworks.com/how_to/117634-gnu-linux-debian-without-systemd
This will happen:
- your gnome would be removed with systemd
- after systemd lock, you would not be able to install gnome, mate,
cinnamon due dependencies (lxde,xfce install without problem)


Regards,
Wiktor

[Message part 2 (text/html, inline)]

Message #162 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Lexel <frum4@arcor.de>

To: 732209@bugs.debian.org

Subject: 732209@bugs.debian.org

Date: Sat, 9 Jan 2016 20:50:50 +0100

Hallo all,

I have trouble with this bug too.
In my opinion it is a serious issue.
I've found out the temporarly solution too (as described in this forum): 
change the ownership of
/run/user/1000/dconf/user.
If I don't change the permission the system is not usable and the 
logfile fills the diskspace .
A normal user without shell experience etc. comes here to a dead end.

Is there anything new about this "bug"?

Cheers
Alex

Message #167 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Joseph Hurtado <p20ph37@gmail.com>

To: 732209@bugs.debian.org

Subject: Fix or workaround?

Date: Fri, 1 Apr 2016 15:12:54 -0700

Is there a fix or workaround for this bug?

Message #206 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>

Subject: Re: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 14 Apr 2016 17:00:12 +0200

[Message part 1 (text/plain, inline)]

On Wed, 26 Nov 2014 15:39:15 +0300 =?UTF-8?B?VmxhZCBPcmxvdg==?=
<monsta@inbox.ru> wrote:
> reassign 732209 libpam-systemd 215-6
> thanks
> 
> 
> Hi,
> 
> Messing with /run/user/1000/dconf/user ownership seems to be the work
> of libpam-systemd - somewhat similar things had been happening before,
> as reported in [1] (and the merged reports).

I'm not convinced it is libpam-systemd which is responsible here.

In all cases I read so far, the user was using gksu or su "without -".
So the environment is not cleared and the
XDG_RUNTIME_DIR environment still points to the one from the calling user.

As soon as a dconf-using program is started, this will change the
permissions of the dconf db (as expected).

The user should use "su -" and gksu should make sure to clear the
environment.

Afaics, there is not to fix on the libpam-systemd/systemd side here.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #211 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 14 Apr 2016 17:34:19 +0200

[Message part 1 (text/plain, inline)]

Am 14.04.2016 um 17:00 schrieb Michael Biebl:
> On Wed, 26 Nov 2014 15:39:15 +0300 =?UTF-8?B?VmxhZCBPcmxvdg==?=
> <monsta@inbox.ru> wrote:
>> reassign 732209 libpam-systemd 215-6
>> thanks
>>
>>
>> Hi,
>>
>> Messing with /run/user/1000/dconf/user ownership seems to be the work
>> of libpam-systemd - somewhat similar things had been happening before,
>> as reported in [1] (and the merged reports).
> 
> I'm not convinced it is libpam-systemd which is responsible here.
> 
> In all cases I read so far, the user was using gksu or su "without -".
> So the environment is not cleared and the
> XDG_RUNTIME_DIR environment still points to the one from the calling user.
> 
> As soon as a dconf-using program is started, this will change the
> permissions of the dconf db (as expected).
> 
> The user should use "su -" and gksu should make sure to clear the
> environment.
> 
> Afaics, there is not to fix on the libpam-systemd/systemd side here.

To verify that point:
Open a shell
unset XDG_RUNTIME_DIR
gksu xterm
→ XDG_RUNTIME_DIR won't be set

I studied the su man page and it resets
$HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS
Contrary to sudo, which by default clears the environment (or pkexec).



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #216 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 14 Apr 2016 17:47:55 +0200

[Message part 1 (text/plain, inline)]

Am 14.04.2016 um 17:34 schrieb Michael Biebl:

> To verify that point:
> Open a shell
> unset XDG_RUNTIME_DIR
> gksu xterm
> → XDG_RUNTIME_DIR won't be set
> 
> I studied the su man page and it resets
> $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS
> Contrary to sudo, which by default clears the environment (or pkexec).

Found this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794972

Contrary to what's been mentioned in the bug report, I can not confirm
that "su" resets XDG_RUNTIME_DIR in Debian.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #221 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 14 Apr 2016 17:57:42 +0200

[Message part 1 (text/plain, inline)]

Am 14.04.2016 um 17:47 schrieb Michael Biebl:
> Am 14.04.2016 um 17:34 schrieb Michael Biebl:
> 
>> To verify that point:
>> Open a shell
>> unset XDG_RUNTIME_DIR
>> gksu xterm
>> → XDG_RUNTIME_DIR won't be set
>>
>> I studied the su man page and it resets
>> $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS
>> Contrary to sudo, which by default clears the environment (or pkexec).
> 
> Found this
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794972
> 
> Contrary to what's been mentioned in the bug report, I can not confirm
> that "su" resets XDG_RUNTIME_DIR in Debian.

To summarize: The issue happens if you run
su <command>
gksu <command>
because it doesn't clear the environment.

If you use
su -l <command> (or su - <command>)
gksu -l <command>
you get a login-like session with the environment reset.

So, if you insist on using su or gksu to run X/GNOME applications (which
is imho not a good idea), I would suggest that you use it only in
combination with "-l".




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #228 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Sun, 17 Apr 2016 13:30:48 +0200

[Message part 1 (text/plain, inline)]

Am 14.04.2016 um 17:57 schrieb Michael Biebl:
> Am 14.04.2016 um 17:47 schrieb Michael Biebl:
>> Am 14.04.2016 um 17:34 schrieb Michael Biebl:
>>
>>> To verify that point:
>>> Open a shell
>>> unset XDG_RUNTIME_DIR
>>> gksu xterm
>>> → XDG_RUNTIME_DIR won't be set
>>>
>>> I studied the su man page and it resets
>>> $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS
>>> Contrary to sudo, which by default clears the environment (or pkexec).
>>
>> Found this
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794972
>>
>> Contrary to what's been mentioned in the bug report, I can not confirm
>> that "su" resets XDG_RUNTIME_DIR in Debian.
> 
> To summarize: The issue happens if you run
> su <command>
> gksu <command>
> because it doesn't clear the environment.
> 
> If you use
> su -l <command> (or su - <command>)
> gksu -l <command>
> you get a login-like session with the environment reset.
> 
> So, if you insist on using su or gksu to run X/GNOME applications (which
> is imho not a good idea), I would suggest that you use it only in
> combination with "-l".

In unstable, this problem still persists (obviously).
The only difference is, that gnome shell doesn't lock up anymore because
of that. If that is due to a change dconf or gnome-shell, I haven't
investigated.
That said, this issue needs to be addressed at the su/gksu level anyway
afaics.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #233 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: Michael Biebl <biebl@debian.org>, 732209@bugs.debian.org

Cc: Miklos Quartus <inbox@miklos.info>, Wiktor Pekalski <wiktor.p1991@gmail.com>, Michael Franzl <office@michaelfranzl.com>, pkr <piiker@walla.com>, MrC <marco_cantu_ranzani@libero.it>, Edilson Azevedo <edilsona6@aim.com>

Subject: Re: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Wed, 20 Apr 2016 17:00:14 +0300

Hi,


> I'm not convinced it is libpam-systemd which is responsible here.

You can check [1] to get some info about libpam-systemd doing
something wrong here.

Also we had this issue for months in Linux Mint before Clement Lefebvre
made a patch [2] that fixed it. After the patched libpam-systemd had been
released for Mint, the problem was gone. That was it. No patching gksu,
no patching dconf.


> So, if you insist on using su or gksu to run X/GNOME applications (which
> is imho not a good idea), I would suggest that you use it only in
> combination with "-l".

Well, that seems to work for me (I'm using MATE though - but it's affected by
the issue as well). But it's not a complete solution. Some apps are meant to
be run via gksu and have gksu without '-l' in their .desktop files. For example,
some of the reporters simply launched a root terminal and then ran some apps
in it. The .desktop file for launching that root terminal is shipped with gksu
itself and has no '-l' in it. Even if you tell users to remember to always run apps
manually with gksu (instead of using root terminal) and always specify '-l', they
might easily forget about that.

I heard several times it's not a good idea to use gksu, but no one suggested
a good, complete replacement for it. The current situation is that we have to use
it sometimes. A few apps like Synaptic or GParted have pkexec support, others
don't have it and we use gksu with them.

> In unstable, this problem still persists (obviously).
> The only difference is, that gnome shell doesn't lock up anymore because
> of that. If that is due to a change dconf or gnome-shell, I haven't
> investigated.

Ok, so maybe it's time to remove 'moreinfo' and 'unreproducible' tags?


[1] https://bugzilla.redhat.com/show_bug.cgi?id=753882
[2] https://github.com/linuxmint/systemd-betsy/commit/f7ab85f1e1169ac1598dfc1fba1c01063840b3c5.patch

Message #238 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Christian Gogolin <debian@cgogolin.de>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Wed, 18 May 2016 17:48:30 +0200

Package: libpam-systemd
Version: 229-5
Followup-For: Bug #732209

I can see this exact error message repeated over and over again on the console
after installing and starting evlution on an otherwhise freshly installed
minimal stretch system. I am running evolution under xmonad, which I start
directly from my xinitrc via startx. No Gnome desktop is installed, only the
minimal dependencies that are pulled when installing evolution and xmonad. I am
roporting this with the hope that the fact that the error is 100% reproducible
on a very minimal system might lead to new insights concerning the nature of
the problem.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus            1.10.8-1
ii  libc6           2.22-7
ii  libpam-runtime  1.1.8-3.2
ii  libpam0g        1.1.8-3.2
ii  libselinux1     2.5-2
ii  systemd         229-5
ii  systemd-sysv    229-5

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

Message #247 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Vlad Orlov <monsta@inbox.ru>, 732209@bugs.debian.org

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Fri, 10 Jun 2016 16:03:58 +0200

Control: tag -1 -moreinfo -unreproducible +wontfix

Vlad Orlov [2016-04-20 17:00 +0300]:
> You can check [1] to get some info about libpam-systemd doing
> something wrong here.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=753882

This was fixed up to the extent possible in
https://github.com/systemd/systemd/commit/baae0358f, i. e. 2.5 years
ago.

> Also we had this issue for months in Linux Mint before Clement Lefebvre
> made a patch [2] that fixed it. After the patched libpam-systemd had been
> released for Mint, the problem was gone. That was it. No patching gksu,
> no patching dconf.

That's a very optimistic. Sure, we could (partially) clean up after
su's brokenness forever, but (1) this makes the fundamental problem
only a bit smaller, but not go away, and (2) we would then have to
maintain this wrong patch forever and taking the blame for it instead
of fixing it at the root cause.

The problem is not "gone" in any sense of the word -- which of the
leaked environment variables do you want libpam-systemd to unset in
su's stead? XDG_RUNTIME_DIR? DBUS_SESSION_BUS_ADDRESS?
DESKTOP_SESSION? MAIL? XDG_CONFIG_DIRS? SSH_AUTH_SOCK? GPG_AGENT_INFO?

The fundamental problem is that it's not at all defined what "su"
without -l actually wants to be: Switching to a different user like a
suid program? Then you need the *entire* environment and not change a
few selected variables like $HOME only. Or be like "login"? Then you
need to clean the env like su -l or sudo. Both of the latter have
well-defined behaviour, whereas the current "su" has no conceptual or
consistent (or safe) behaviour at all.

> Ok, so maybe it's time to remove 'moreinfo' and 'unreproducible' tags?

Yes, I agree about that. But libpam-systemd is still neither the
correct nor even a possible place to fix this.

AFAICS, the behaviour of "su" without -l either needs to be properly
defined and fixed, or it should be completely deprecated, perhaps
making it do the same thing as -l.

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Message #258 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Martin Pitt <mpitt@debian.org>, 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>, login@packages.debian.org

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Fri, 10 Jun 2016 16:17:13 +0200

[Message part 1 (text/plain, inline)]

CCing the login maintainer, maybe he has some input on this matter.


Am 10.06.2016 um 16:03 schrieb Martin Pitt:
> Control: tag -1 -moreinfo -unreproducible +wontfix
> 
> Vlad Orlov [2016-04-20 17:00 +0300]:
>> You can check [1] to get some info about libpam-systemd doing
>> something wrong here.
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=753882
> 
> This was fixed up to the extent possible in
> https://github.com/systemd/systemd/commit/baae0358f, i. e. 2.5 years
> ago.
> 
>> Also we had this issue for months in Linux Mint before Clement Lefebvre
>> made a patch [2] that fixed it. After the patched libpam-systemd had been
>> released for Mint, the problem was gone. That was it. No patching gksu,
>> no patching dconf.
> 
> That's a very optimistic. Sure, we could (partially) clean up after
> su's brokenness forever, but (1) this makes the fundamental problem
> only a bit smaller, but not go away, and (2) we would then have to
> maintain this wrong patch forever and taking the blame for it instead
> of fixing it at the root cause.
> 
> The problem is not "gone" in any sense of the word -- which of the
> leaked environment variables do you want libpam-systemd to unset in
> su's stead? XDG_RUNTIME_DIR? DBUS_SESSION_BUS_ADDRESS?
> DESKTOP_SESSION? MAIL? XDG_CONFIG_DIRS? SSH_AUTH_SOCK? GPG_AGENT_INFO?
> 
> The fundamental problem is that it's not at all defined what "su"
> without -l actually wants to be: Switching to a different user like a
> suid program? Then you need the *entire* environment and not change a
> few selected variables like $HOME only. Or be like "login"? Then you
> need to clean the env like su -l or sudo. Both of the latter have
> well-defined behaviour, whereas the current "su" has no conceptual or
> consistent (or safe) behaviour at all.
> 
>> Ok, so maybe it's time to remove 'moreinfo' and 'unreproducible' tags?
> 
> Yes, I agree about that. But libpam-systemd is still neither the
> correct nor even a possible place to fix this.
> 
> AFAICS, the behaviour of "su" without -l either needs to be properly
> defined and fixed, or it should be completely deprecated, perhaps
> making it do the same thing as -l.
> 
> Thanks,
> 
> Martin
> 


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #263 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Linas Vepstas <linasvepstas@gmail.com>

To: Martin Pitt <mpitt@debian.org>, 732209@bugs.debian.org, Vlad Orlov <monsta@inbox.ru>, login@packages.debian.org

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Fri, 9 Sep 2016 14:09:05 -0500

[Message part 1 (text/plain, inline)]

The suggestion below, that the core issue is that "su" is leaking the
user-space env variables into the root shell, where they are then used to
clobber the user-space, seems like a good root-cause analysis of the bug.
I agree, it seems like "su" needs to be fixed.

I the meanwhile, can we get a work-around? There are 8 bugs duped to this
one in Debian; there are several dupes in redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=753882 as well as Linux Mint:
https://github.com/mate-desktop/mate-settings-daemon/issues/44  and dozens
of help forums discuss this.

This has been biting untold zillions of people for 3-4-5 years now, and the
fix-process is stalled due to finger-pointing.  Yes, the right fix seems to
be to fix "su", but in the meanwhile... something?

The current Linux Mint work-around is here:
https://github.com/linuxmint/systemd-betsy/commit/f7ab85f1e1169ac1598dfc1fba1c01063840b3c5

--linas

Am 10.06.2016 um 16:03 schrieb Martin Pitt:
> Control: tag -1 -moreinfo -unreproducible +wontfix
>
> Vlad Orlov [2016-04-20 17:00 +0300]:
>> You can check [1] to get some info about libpam-systemd doing
>> something wrong here.
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=753882
>
> This was fixed up to the extent possible in
> https://github.com/systemd/systemd/commit/baae0358f, i. e. 2.5 years
> ago.
>
>> Also we had this issue for months in Linux Mint before Clement Lefebvre
>> made a patch [2] that fixed it. After the patched libpam-systemd had been
>> released for Mint, the problem was gone. That was it. No patching gksu,
>> no patching dconf.
>
> That's a very optimistic. Sure, we could (partially) clean up after
> su's brokenness forever, but (1) this makes the fundamental problem
> only a bit smaller, but not go away, and (2) we would then have to
> maintain this wrong patch forever and taking the blame for it instead
> of fixing it at the root cause.
>
> The problem is not "gone" in any sense of the word -- which of the
> leaked environment variables do you want libpam-systemd to unset in
> su's stead? XDG_RUNTIME_DIR? DBUS_SESSION_BUS_ADDRESS?
> DESKTOP_SESSION? MAIL? XDG_CONFIG_DIRS? SSH_AUTH_SOCK? GPG_AGENT_INFO?
>
> The fundamental problem is that it's not at all defined what "su"
> without -l actually wants to be: Switching to a different user like a
> suid program? Then you need the *entire* environment and not change a
> few selected variables like $HOME only. Or be like "login"? Then you
> need to clean the env like su -l or sudo. Both of the latter have
> well-defined behaviour, whereas the current "su" has no conceptual or
> consistent (or safe) behaviour at all.
>
>> Ok, so maybe it's time to remove 'moreinfo' and 'unreproducible' tags?
>
> Yes, I agree about that. But libpam-systemd is still neither the
> correct nor even a possible place to fix this.
>
> AFAICS, the behaviour of "su" without -l either needs to be properly
> defined and fixed, or it should be completely deprecated, perhaps
> making it do the same thing as -l.
>
> Thanks,
>
> Martin
>

[Message part 2 (text/html, inline)]

Message #268 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: 732209@bugs.debian.org, Martin Pitt <mpitt@debian.org>, Michael Biebl <biebl@debian.org>

Cc: Linas Vepstas <linasvepstas@gmail.com>

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 15 Sep 2016 14:45:58 +0300

Hi,

Is su actually used for running graphical apps? Most people seem to use gksu
for that. But gksu --help shows a weird warning about using -l argument:

  --login, -l
    Make this a login shell. Beware this may cause
    problems with the Xauthority magic. Run xhost
    to allow the target user to open windows on your
    display!

Hmm, what? Some easily-broken magic? Isn't gksu supposed to handle stuff like
that automatically? :)

There's also this problem... no one still volunteered to actually help fixing
su or gksu/libgksu.

What's the status of gksu and libgksu anyway? I see no new upstream releases
since 2009, and upstream bug tracker seems to be completely abandoned.

Message #273 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Vlad Orlov <monsta@inbox.ru>

To: 732209@bugs.debian.org, Martin Pitt <mpitt@debian.org>, Michael Biebl <biebl@debian.org>

Cc: Linas Vepstas <linasvepstas@gmail.com>

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 15 Sep 2016 15:21:59 +0300

Hi,

Just found a link to a pam module [1] (posted in the comment at [2]).

> It's a pam module that removes the XDG_RUNTIME_DIR environment variable from
> the environment if the user authenticating is different from the user owning
> it.  This is for the case of programs like gksu clobbering the users' dconf
> settings.

I don't know if this would be an acceptable workaround for this problem.
Can you please give your opinion on it?


[1] https://github.com/sbalneav/libpam-envclean
[2] https://github.com/mate-desktop/mate-settings-daemon/issues/44#issuecomment-247147445

Message #278 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Linas Vepstas <linasvepstas@gmail.com>

To: Vlad Orlov <monsta@inbox.ru>

Cc: 732209@bugs.debian.org, Martin Pitt <mpitt@debian.org>, Michael Biebl <biebl@debian.org>

Subject: Re: Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Thu, 15 Sep 2016 12:21:25 -0500

[Message part 1 (text/plain, inline)]

On Thu, Sep 15, 2016 at 6:45 AM, Vlad Orlov <monsta@inbox.ru> wrote:
>
>
> Is su actually used for running graphical apps?


In my case, I either accidentally typed into an su window, or possibly ran
the gconf editor as root, for some possibly good or bad reason, possibly
having to do with xdm, gdm whateverdm, or possibly some intentional or
unintentional debugging of audio or video playback. This is the "shit
happens" category, and based on the rate of reports streaming in, "shit
happens" every now and then for everyone. If it happened a lot, the problem
would be fixed. If it happened very rarely, there would be no heat.

>
> There's also this problem... no one still volunteered to actually help
> fixing
> su or gksu/libgksu.
>

 "fixing" su could have very long-running reprecussions: it is a
40-year-old utility, and I know for a fact that there are people out there
who run 40-year-old shell scripts (I have a friend who works at a company
that specializes in porting ancient, undocumented code to modern systems.)
 If you "fix" it, the various vendors (red-hat, ubuntu, debian) will very
slowly start accumulating bug reports related to the change. These reports
will arrive at the rate of a few a year, for a decade (similar to the rate
of reporting on this bug-- which is now 3-4 years old, and gets a new
complaint every now and then). The knee-jerk reaction will be to undo
whatever the "fixes" were. So the volunteer needs to not only fix the
problem, update the man page, etc. but then be persistent for many years.
That's hard.

--linas

[Message part 2 (text/html, inline)]

Message #283 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Arv Evans <arvid.evans@gmail.com>

To: 732209@bugs.debian.org

Subject: It is still there (13 November 2016)

Date: Sun, 13 Nov 2016 08:13:37 -0700

[Message part 1 (text/plain, inline)]

Bug is reproducible in Debian Jessie using MATE desktop launcher for
Arduino IDE

[Message part 2 (text/html, inline)]

Message #288 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michał Milanowski <emsoft1@gmail.com>

To: 732209@bugs.debian.org

Subject: Re: (gnome-control-center:11187): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Mon, 6 Feb 2017 09:29:20 +0100

Issue is still there on most recent (at the moment) Debian Sid /
Cinnamon. It seems to be completly random, Cinnamon freezes and I need
to reboot computer from console. After 1-2 hours or even after 5 hours
after login to Cinnamon.

Isn't there any fix yet? This is quite annoying.

Message #293 received at 732209@bugs.debian.org (full text, mbox, reply):

From: JOHN MICHAEL <anisahaziz83@gmail.com>

To: undisclosed-recipients:;

Subject: how are you doing today..

Date: Mon, 8 May 2017 12:16:25 +0100

how are you doing today..

Message #303 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Dan F <mrsweet06@hotmail.com>

To: "732209@bugs.debian.org" <732209@bugs.debian.org>

Subject: Re: (gnome-control-center:11187): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.

Date: Tue, 9 May 2017 02:12:35 +0000

FWIW -

I have encountered this only one time(as of now), on ParrotSec OS (I 
know it's debian, I believe it is stretch) after installing firejail and 
running thunderbird firejail'd (pluma was also open at the time, as was 
the Mate panel editor and a couple folders). The computer slowing down 
was caused by process kswapd0, and the process hogging all the RAM was 
mate-settings-d. Also, the computer didn't become wholly unresponsive, 
but it was close. For instance, the mouse arrow moved very, very slowly, 
and no clicks or other commands would register until kswapd0 got done. I 
closed out all firejail'd applications and killed the mate-settings-d 
process in the terminal and the computer runs fine, no other steps 
needed (although it did take a minute for the kill command to take 
effect. Once it did, though, the computer was immediately back to 
normal). Thing is, re-running thunderbird, firejail'd or not, now has no 
effect. No warnings, no slowdown, no nothing. Doesn't seem to matter 
what else is open.

I know that isn't a lot of technical information, but it is contextual. 
I'm told every little bit helps.

Message #308 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Thu, 18 May 2017 11:51:20 +0545

Package: libpam-systemd
Version: 232-23
Followup-For: Bug #732209

I see the same problem show up on my GNOME box. In my case, it is
tracker that is complaining, which could be a reason why I haven't
directly witnessed any loss of functionality in my laptop usage.



May 18 11:44:52 learner dbus-daemon[5176]: Reloaded configuration
May 18 11:45:32 learner tracker-extract[5459]: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
May 18 11:45:39 learner fdm[29614]: researchut: 17 messages processed (0 kept) in 37.985 seconds (average 2.234)
May 18 11:45:57 learner chromium.desktop[6365]: [6365:6365:0518/114557.763909:ERROR:browser_main_loop.cc(279)] Gdk: gdk_window_set_user_time called on non-toplevel
May 18 11:45:58 learner chromium.desktop[6365]: [6365:6365:0518/114558.138419:ERROR:browser_main_loop.cc(279)] Gdk: gdk_window_set_user_time called on non-toplevel
May 18 11:46:10 learner tracker-extract[5459]: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.13+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus            1.10.18-1
ii  libc6           2.24-10
ii  libpam-runtime  1.1.8-3.5
ii  libpam0g        1.1.8-3.5
ii  libselinux1     2.6-3+b1
ii  systemd         232-23
ii  systemd-sysv    232-23

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

Message #313 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Ritesh Raj Sarraf <rrs@debian.org>, 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Fri, 19 May 2017 22:51:26 +0200

[Message part 1 (text/plain, inline)]

Am 18.05.2017 um 08:06 schrieb Ritesh Raj Sarraf:
> Package: libpam-systemd
> Version: 232-23
> Followup-For: Bug #732209
> 
> I see the same problem show up on my GNOME box. In my case, it is
> tracker that is complaining, which could be a reason why I haven't
> directly witnessed any loss of functionality in my laptop usage.


> May 18 11:46:10 learner tracker-extract[5459]: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

That's most certainly a different issue.
tracker uses uses a seccomp sandbox for its extractors nowadays.
The error you get is most likely a result of that.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #318 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Ritesh Raj Sarraf <rrs@debian.org>

To: Michael Biebl <biebl@debian.org>, 732209@bugs.debian.org

Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Sat, 20 May 2017 10:48:07 +0545

[Message part 1 (text/plain, inline)]

On Fri, 2017-05-19 at 22:51 +0200, Michael Biebl wrote:
> > May 18 11:46:10 learner tracker-extract[5459]: unable to create file
> '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
> 
> That's most certainly a different issue.
> tracker uses uses a seccomp sandbox for its extractors nowadays.
> The error you get is most likely a result of that.

Thanks Michael. I just checked upstream and this issue is reported and fixed
already (Probably in version 1.12).

https://bugzilla.gnome.org/show_bug.cgi?id=779342

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

[signature.asc (application/pgp-signature, inline)]

Message #323 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Anthony Donegan <tony@fisica.ufc.br>

To: 732209@bugs.debian.org

Subject: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Thu, 29 Jun 2017 21:47:25 -0300

[Message part 1 (text/plain, inline)]

I had the same problem when upgrading from jessie to stretch (systemd 
232-25) with a Cinnamon desktop.

Opening a root terminal using "gksu /usr/bin/x-terminal-emulator" (as in 
the menu) causes lots of dconf-CRITICAL error messages.

These vanish if I edit the menu item to "gksudo 
/usr/bin/x-terminal-emulator" and add the original user u to the sudo 
group vi "usermod -a -G sudo u".

This also seemed to fix a less critical but similar error with fuse 
complaining about a "bad mount point /run/user/1000/gvfs Permission denied".

[Message part 2 (text/html, inline)]

Message #328 received at 732209@bugs.debian.org (full text, mbox, reply):

From: Miklos Quartus <inbox@miklos.info>

To: Debian Bug Tracking System <732209@bugs.debian.org>

Subject: Re: unable to create file '/run/user/1000/dconf/user': Permission denied

Date: Mon, 03 Jul 2017 20:57:31 +0200

Package: libpam-systemd
Version: 232-25
Followup-For: Bug #732209

Hello 

I am also using Debian Stretch on Cinnamon desktop and the problem
seems to be gone.  I am no longer getting strange messages in syslog
neither the annoying X desktop lock-up.  Interestingly, when I do "gksu
/usr/bin/x-terminal-emulator", I get a segfault (you read it right,
on Debian stable!):

"
2017-07-03T20:16:24.930235+02:00 qmitoshiba kernel: [14358.860790] gnome-terminal-[4335]: segfault at 8 ip 0000560f0872ccb7 sp 00007ffca2a0f540 error 4 in gnome-terminal-server[560f08718000+4c000]
"

Still, I am able to spin-up a new gnome terminal nonetheless. The bug
displayed above is less of an issue, as it is not a blocker to your
daily routine having to restart your X desktop session like it used to.
So, thankfully, the original issue looks like to be gone. Just
in case anyone did not notice, the x-terminal-emulator is a
gnome-terminal.wrapper Perl script (which in turn runs gnome-terminal)
by default:

"
root@qmitoshiba:~# update-alternatives --display x-terminal-emulator
x-terminal-emulator - auto mode
  link best version is /usr/bin/gnome-terminal.wrapper
  link currently points to /usr/bin/gnome-terminal.wrapper
  link x-terminal-emulator is /usr/bin/x-terminal-emulator
  slave x-terminal-emulator.1.gz is /usr/share/man/man1/x-terminal-emulator.1.gz
/usr/bin/gnome-terminal.wrapper - priority 40
  slave x-terminal-emulator.1.gz: /usr/share/man/man1/gnome-terminal.1.gz
root@qmitoshiba:~# ls -l /usr/bin/gnome-terminal.wrapper 
-rwxr-xr-x 1 root root 1394 Jun 16  2011 /usr/bin/gnome-terminal.wrapper
root@qmitoshiba:~# dpkg -S !$
dpkg -S /usr/bin/gnome-terminal.wrapper
gnome-terminal: /usr/bin/gnome-terminal.wrapper
root@qmitoshiba:~# file /usr/bin/gnome-terminal.wrapper 
/usr/bin/gnome-terminal.wrapper: Perl script text executable
root@qmitoshiba:~# 
"

After others confirm the same behaviour including on sid, we can close
this bug and open a new one against the gnome-terminal.


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus            1.10.18-1
ii  libc6           2.24-11+deb9u1
ii  libpam-runtime  1.1.8-3.6
ii  libpam0g        1.1.8-3.6
ii  libselinux1     2.6-3+b1
ii  systemd         232-25
ii  systemd-sysv    232-25

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

--
Miklos Quartus 
inbox@miklos.info
WWW: http://www.miklos.info
GPG: 3C4B 1364 A379 7366 7FED  260A 2208 F2CE 3FCE A0D3

Send a report that this bug log contains spam.