Got working gdm 3.8.4-3 for me. The issue was the enabled autologin.
/etc/gdm3/daemon.conf:
[daemon]
# AutomaticLoginEnable = false
# AutomaticLogin =
Which seams to use su in background and run into the runtime_path bug.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
w
Same issue for me after upgrading to gdm 3.8.4-3. A black screen after
starting gdm, except if I chmod 777 /run/user/0.
/var/log/gdm3/:0-slave.log:
gdm-simple-slave[5325]: Failed to give slave programs access to the
display. Trying to proceed.
gdm-launch-environment][5358]: pam_env(gdm-launch-
Created a bug report for systemd.
https://bugs.freedesktop.org/show_bug.cgi?id=70810.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 23.10.2013 16:18, Simon McVittie wrote:
Making /run/user/${UID} writable by users other than ${UID} is probably
a security vulnerability, so I would advise not doing that.
If course not. This is only a workaround to get X working again. But
login direct as user avoid this workaround anyway.
What's your $XDG_RUNTIME_DIR environment variable?
My $XDG_RUNTIME_DIR as user gabriel (uid=1000) is "/run/user/0" and
should in my opinion be "/run/user/1000".
If it's /run/user/0, then GLib is behaving as expected, and the bug is
in some other component (which should either not set this va
Dear all
This must be a bug in the function g_get_user_runtime_dir () relating
Glib. I have wrote a small piece of code:
user@machine:~/Work$ cat run.c
#include
void main()
{
g_printf("%s\n", g_get_user_runtime_dir ());
}
user@machine:~/Work$ gcc `pkg-config --cflags --libs glib-2.0
6 matches
Mail list logo
