Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
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 560f0872ccb7 sp 7ffca2a0f540 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 dbus1.10.18-1 ii libc6 2.24-11+deb9u1 ii libpam-runtime 1.1.8-3.6 ii libpam0g1.1.8-3.6 ii libselinux1 2.6-3+b1 ii systemd 232-25 ii systemd-sysv232-25 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information -- Miklos Quartus in...@miklos.info WWW: http://www.miklos.info GPG: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Fwd: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
Hi Debian systemd-maintainers, Because of bug #732209, I am trying to build systemd from source. I obtained the source by 'apt-get source libpam-systemd' on Jessie. One patch was suggested that might be a fix to the problem, see the bug report. Now, I applied the patch and compiled the source successfully, however, when I get to building the package from the source, I find in the README.source the following: Building from source Install “git-buildpackage” and run the following steps: gbp-clone git+ssh://git.debian.org/git/pkg-systemd/systemd.git cd systemd git-buildpackage We recommend you use pbuilder to make sure you build in a clean environment: git-buildpackage --git-pbuilder I am stuck at gbp-clone, cannot build the package as I don't have access to the git.debian.org (not being a DD), getting some SSH connection error. Could you please help me to build package libpam-systemd or give me a hint how to proceed? (https://wiki.debian.org/Alioth/Git seem to suggest that I need to request access). Thanks, best regards, Miklos -- Forwarded message -- From: Vlad Orlov mon...@inbox.ru Date: 1 June 2015 at 06:17 Subject: Re: Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied To: Miklos Quartus in...@miklos.info Cc: Tycho Lürsen tycholur...@gmail.com Hi, I never tried git-related debian tools for building packages. I always use debuild or dpkg-buildpackage tools. Here's a couple of good tutorials about rebuilding the packages: http://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/ http://raphaelhertzog.com/2011/07/04/how-to-prepare-patches-for-debian-packages/ You'll probably need the second tutorial for this case (see section 2.2.1. Import a patch there). -- Miklos ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
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-pci:00-:00:02.0-backlight-acpi_video0.device loaded active plugged /sys/devices/pci:00/:00:02.0/backlight/acpi_video0 sys-devices-pci:00-:00:02.0-drm-card0-card0\x2dLVDS\x2d1-intel_backlight.device loaded active plugged /sys/devices/pci:00/: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 libcap21: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 systemd215-8 ii systemd-sysv 215-8 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: (no subject)
Content-Type: multipart/mixed; boundary1764408977== MIME-Version: 1.0 From: Miklos Quartus in...@miklos.info To: Debian Bug Tracking System 732...@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 libcap21: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 systemd215-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==-- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: libpam-systemd: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
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 libcap21: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 systemd215-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- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
