Your message dated Mon, 23 Dec 2013 17:05:09 +0100
with message-id <52b85f35.1050...@googlemail.com>
and subject line Bug#724731: gdm3 may be still buggy, but Bug#724731 is resolved
has caused the Debian Bug report #724731,
regarding [gdm3] gdm does not start properly, cannot login via gdm
reopen 724731
severity 724731 serious
found 724731 3.8.4-6
thanks
This is the third box showing the same problem: After logging in the
window system does not work, e.g. iconizing iceweasel freezes showing
only the images towards the icon.
On the console (tty6) the following is written:
login [154
I also had the problem of loging in via gdm3 and getting a blank screen
(with the exception of the debian logo at the bottom). I started having
this problem after upgrading a jessie machine on Friday, November 22 in
the morning (America/New_York). In the evening of the same day I fixed
the problem
Hi,
On 14/11/13 13:57, Simon McVittie wrote:
> libpam-systemd derives the XDG_RUNTIME_PATH from the "loginuid", which
> was originally part of the audit framework. The loginuid was originally
> intended to answer questions like "yes, I know this process is root, but
> who is it really?" to provide
On 14/11/13 01:10, Leo Antunes wrote:
> I'm consistently getting the
> issue described by Gabriel Mainberger, namely that gdm gets the wrong
> XDG_RUNTIME_PATH and fails to start. But interestingly it only happens
> if I restart gdm.
libpam-systemd derives the XDG_RUNTIME_PATH from the "loginuid",
[cc'ing systemd maintainers for their input]
Hi all,
On a fresh qemu install dist-upgraded to sid (wheezy install;
dist-upgrade and lastly gnome install) I'm consistently getting the
issue described by Gabriel Mainberger, namely that gdm gets the wrong
XDG_RUNTIME_PATH and fails to start. But int
Your message dated Wed, 13 Nov 2013 21:51:00 +0100
with message-id <5283e634.9050...@debian.org>
and subject line Re: [gdm3] Bug#724731: dependency problem (libpam-systemd) not
solved
has caused the Debian Bug report #724731,
regarding [gdm3] gdm does not start properly, cannot login via
Hi,
Well, not trying to install libpam-systemd was really dumb of my part, I'm
sorry, I can confirm that it works now.
I'm very gratefull for your fast reply, considering that my feedback wasn't
very explanatory.
Best regards
2013/11/13 Andreas Cadhalpun
> Control: found -1 3.8.4-4
>
> Hi,
>
Processing control commands:
> found -1 3.8.4-4
Bug #724731 {Done: Emilio Pozuelo Monfort } [gdm3] [gdm3] gdm
does not start properly, cannot login via gdm
Marked as found in versions gdm3/3.8.4-4; no longer marked as fixed in versions
gdm3/3.8.4-4 and reopened.
--
724731: h
Control: found -1 3.8.4-4
Hi,
thanks for the fixed autologin. I can confirm that autologin works now.
But the main problem, that anybody will be confronted with, when
upgrading gdm3 to 3.8, is still not solved: libpam-systemd is still no
dependency of gdm3 and is thus not installed when upgra
Hello,
Please reopen. The bug ist not fixed.
The screen still stays blank after login. Only the mouse pointer is seen.
Here is the last part of greeter.log:
gnome-session[7105]: DEBUG(+): GsmManager: starting app
'/org/gnome/SessionManager/App1'
gnome-session[7105]: DEBUG(+): Starting app: /org/
Hi, I was very excited about testing the Gnome 3.8 that I decided upgrade
some packages from the SID, the packages I upgraded were:
gdm3
gnome-control-center
gnome-disk-utility
gnome-session
gnome-settings-daemon
gnome-shell
gnome-shell-extensions
gsettings-desktop-schemas
mutter
nautilus
seed
gnom
Your message dated Tue, 12 Nov 2013 19:48:39 +
with message-id
and subject line Bug#724731: fixed in gdm3 3.8.4-4
has caused the Debian Bug report #724731,
regarding [gdm3] gdm does not start properly, cannot login via gdm
to be marked as done.
This means that you claim that the problem has
Hello,
The blank screen after login problem looks like as if gdm does not "leave"
output so that the graphical desktop is not shown.
Because in the processlist, all gnome apps start running.
I also managed to wait a very long time, and was able to see screen garbage
and rendering problems, if I mo
Package: gdm3
Version: 3.8.4-3
Followup-For: Bug #724731
I managed to solve by removing and reinstalling the following packages,
as suggested in commment 71:
gnome-core gnome-shell gdm3 gnome-session
When I reinstalled, I see more packages than those removed. Maybe it's
a hint to fin
Installing libpam-systemd worked on another laptop of mine, but it doesn't
work in a laptop which has the same debian version.
I've tried all the workarounds suggested here, but none works.
Please note that the same problem occurs if I use lightdm. I can login,
then the screen remains empty (only
Hi,
Lucas Nussbaum wrote (29 Oct 2013 06:26:59 GMT) :
> I ran into one issue where gdm3 would start but the screen would stay
> blank.
Same here.
> It seems that it was caused by some custom /etc/pam.d/ config on my
> system, which prevented libpam-systemd to update the config file
> properly.
Hi,
I can confirm that the following line fixed this for me :
$ sudo pam-auth-update --force
Thanks,
Alex
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: gdm3
Version: 3.8.4-3
Followup-For: Bug #724731
Hi,
I solved the blank screen issue (3.8.4-3) installing systemd-ui package.
I tested using both sysvinit and systemd, working like a charm.
Victor
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy
Hi,
I ran into one issue where gdm3 would start but the screen would stay
blank.
It seems that it was caused by some custom /etc/pam.d/ config on my
system, which prevented libpam-systemd to update the config file
properly.
After running 'sudo pam-auth-update --force', the config files were
upd
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-
It seems to be solved for me after upgrading to 3.8.4-3.
Here are the information regarding each packages that seems involved in
this bug report :
===
gdm3 :
===
-- System Informat
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.
On 23/10/13 14:17, Gabriel Mainberger wrote:
>> * if in X11, which display manager (gdm3, lightdm, xdm, kdm, etc.),
>> or did you use startx or something from a text virtual console?
>
> Currently I get with gdm3 only a black screen. So my only possibility is
> to chmod my /run/user/0 directory.
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
y and as
Simon suspects, some other component simply sets XDG_RUNTIME_DIR to an
incorrect value.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724731
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
On 23/10/13 08:07, Gabriel Mainberger wrote:
> user@machine:~/Work$ gcc `pkg-config --cflags --libs glib-2.0` -o run run.c
>
> user@machine:~/Work$ ./run
> /run/user/0
What's your $XDG_RUNTIME_DIR environment variable?
If it's /run/user/0, then GLib is behaving as expected, and the bug is
in som
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
Confirmed fixed in 3.8.4-2 or with current sid dependencies as of 23
October 2013.
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
To another bug whilst the problem existed only on experimental, I already
had posted the problems regarding the XDG_SESSION_ID detection.
Actually, after being merged into unstable, the nature of the problem
changed:
Doing an
"mkdir -p /run/user/0"
"chmod 777 /run/user/0"
before gdm script
Dear Maintainer,
gdm3 3.8.4 in Debian sid appears to be broken. The login screen will
start and present a list of users. Clicking on a user will show the
password entry field and you can type a password into it. However
subsequently clicking the Sign In button or pressing Return simply
causes the
Package: gdm3
Followup-For: Bug #724731
Same here, libpam-systemd did NOT solve the issue.
When using gdm3, I get a splash screen saying that something went wrong
( "Oops! A problem has occured! .. ") with the only option too log out.
No greeter, username field or password field.
Hi,
Installing libpam-systemd only was not a workaround for me. I had to
switch to lightdm as a greeter. Here is the details of my packages :
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architectur
Thanks Eugen!
Installing libpam-systemd worked also for me
Hi folks,
I'm also concerned by this problem.
What I have noticed during investigations is that all gnome services
attempting to use gnome-settings-daemon complain about dconf with
messages like
(gnome-settings-daemon:7139): dconf-CRITICAL **: unable to create
directory '/run/user/0/dconf':
Hi,
I can confirm, that the login is shown, if libpam-systemd is installed.
But autologin still does not work. See the attached logs.
I hope these logs help to solve the problem soon.
Best regards,
Andreas
openConnection: connect: Datei oder Verzeichnis nicht gefunden
cannot connect to brltty
[cross-posting to #724731 - didn't want to take the liberty of merging
them, though they do look awfully similar]
I think I might have made some progress:
In libgjs0c's version in sid, at /usr/share/gjs-1.0/overrides/GLib.js,
line 199, there is the following snippet:
// g_variant_get_string has l
I've been analyzing the list of packages that are having problems and
comparing with my packages.
And what draws the most attention is the libglib2.0-0, which is the package
that I have more updated and it's dependence on GDM3.
Compared with a live version of UbuntuGnome 13.10 which uses GDM 3.8
Just to say that I had the same problem: gdm3 did not start, a black
screen with 2 lines of error were shown. startx showed a black screen
with mouse movement only working. Bizarre, startx worked when removing
and reinstalling right afterwards gnome-shell gnome-session gdm3
gnome-core; I have
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
Now that 3.8.4 has entered unstable I've run into this issue too.
Changing init systems is a drastic work around, I was able to continue
logging in to gnome classic by:
* renaming the .configs directory in my home dir
* using kdm
Followup-For: Bug #724731
Package: gdm3
Version: 3.8.4-2
Hi,
In my case, I use like the systemd to replace sysvinit.
Greetings.
Valdinilson.
PS: I do not use autologin.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable&#x
FYI: I've disabled autologin, so your theory could be right. I'll
investigate it tomorrow.
--
Jascha Geerds
j...@ekby.de
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
Disabling autologin (along with having libpam-systemd installed) seems
to fix the problem, at least for initial startup. I've observed some
reliability issues when restarting gdm3, but initial startup seems to
work.
So: broken wi
Did you only installed "libpam-systemd" or did you also boot with
systemd (instead of SysVinit) ?
You can temporary boot using systemd by editing the GRUB kernel command
line (press "e" inside GRUB) and append "init=/lib/systemd/systemd" to
it. For further information see https://wiki.debian.org/s
Package: gdm3
Version: 3.8.4-2
Followup-For: Bug #724731
I'm observing this issue as well, and installing libpam-systemd (with a
reboot to restart all services including gdm) did not fix it for me. I
still get a black screen from gdm, but I can startx from a terminal.
- Josh Triplett
-- S
Hi,
I've been with this problem for a long time. And after seeing the review of
Jascha Geerds, I decided to install libpam-systemd.
# apt-get install libpam-systemd
Problem solved.
Valdinilson.
GDM 3.8 just migrated to unstable and I am also hit by this bug.
A workaround for logging in is to use an alternate logging manager for
now. LightDM did the job well and does not pull a lot of additional
dependencies.
I can't really add anything more to this bug report at this point,
although if
I have also tested GDM 3.8. Unfortunately, all I see is a blank screen.
I heard that Gnome 3.6 and higher requires systemd to work. So I
installed the sytsemd packages (without its recommended packages) but
the screen remains blank. Then I figured out that I need to install the
"libpam-systemd" pac
Package: gdm3
Version: 3.8.4-1
Followup-For: Bug #724731
Hi,
Here, gdm3 also stopped working.
My workaround was installing lightdm (has a lot less dependencies
than kdm).
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable&#x
Hi,
I'm also affected by that, and still haven't found a solution, despite
upgrading dbus packages to their experimental version.
A workaround is to login using e.g. kdm. Everything seems to work
normally after that.
#724731 and #722930 should probably be merged (and reopened).
Lucas
--
To U
The problem disappeared after further upgrading some gnome packages,
removing some old cruft from the system and rebooting. Sorry that I
can't be any more specific.
Cheers,
Bastian
--
Bastian Venthur http://venthur.de
Debian Developer
Package: gdm3
Version: 3.8.4-1
Severity: grave
Hi,
I updated to 3.8 today, and after restarting the gdm3, I cannot login
anymore. Gdm3 somehow starts (graphics are visible) but the login field
is missing.
:0-slave.log says:
--
** (gdm-simple-slave:19770): WARNING **: Couldn't co
54 matches
Mail list logo
