This is happening for me with autologin enabled for oneiric. I had to
switch from lightdm to gdm because lightdm causes another bug that makes
my system run at 100% CPU, but autologin with gdm has this problem.
gdm-simple-slave[1220]: CRITICAL: gdm_session_direct_get_username:
assertion `session
GDM has a bugfix by Robert Ancell:
Description: Don't autologin if using ecryptfs - if you do then the home
directory is empty as you need the password entered via PAM to decrypt it.
This is not a perfect solution as the home directory may not be mounted yet.
Author: Robert Ancell
This also affects me, in oneiric -- in my logs, I get the following with
autologin enabled:
gdm-simple-slave[1382]: CRITICAL: gdm_session_direct_get_username: assertion
`session != NULL' failed
gdm-binary[1106]: WARNING: GdmDisplay: display lasted 1.024504 seconds
When I disable it, it works
I am having problems with gdm in oneiric - I get the following text in
/var/log/gdm/:0-slave.log
gdm-simple-slave[1605]: CRITICAL: gdm_session_direct_get_username:
assertion `session != NULL' failed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I just set Auto login to on for my account and Oneiric did not start. My
PC stopped on the Checking Battery State screen and gdm did not load.
I searched and searched until I finally looked in syslog and saw the
gdm_session_direct_get_username text. Through google I stumbled onto
this thread.
I
** Changed in: gdm (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/803992
Title:
Natty update introduced crasher in xorg
To manage
Closing this bug as I cannot reproduce it in Oneiric.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Opinion
** Changed in: xorg-server (Ubuntu)
Status: Opinion = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I add this problem with gnome shell. To boot again properly, I had to
log in with ALT+F1, and with apt-get, remove gdm and reinstall lightdm,
which did not cause any problem at the next reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hey rogz,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the new
Does anyone have any updates on this? I'm also affected by this.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/803992
Title:
Natty update introduced crasher in xorg
To manage
** Changed in: gdm (Ubuntu)
Status: New = Confirmed
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/803992
I've just been told on irc that my responses above are are only partially or
not applicable here.
The original bug is on gnome3; my problem and fix was with gnome 2.32
apologies for any confusion.
Frans
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
The tip did not work for me, as I never used autologin and still have
the same symptoms. I tried to enable autologin, and then Xorg failed to
come up (startx from the vt1 worked fine). After autologin was disabled,
gdm comes up, I can log in, but problem is still there.
--
You received this bug
no source code analysis.
Otherwise I would have probably come up with a fix.
At some point I suspected that my session type was wrong, but since I used
autologon I could not change it to test it.
Therefore I turned autologon off and noticed that things started to work.
Sometimes it is just that
I had the very same problem (CRITICAL: gdm_session_direct_get_username:
assertion `session != NULL' failed) in syslog, startx works), only the
line number in the message was different.
I found that my problem was caused by using autologin.
As a workaround I went to administration/user accounts
I tried the solution provided by Frans above and can confirm that the
workaround solves the problem. In my case, I'm not sure if I ever
changed the autologin option for my user or why the problem suddenly
appeared in the first place.
If you need any additional information regarding the problem, I
Hi Frans,
Thanks for the tip - worked for me as well. How did you find out?
Source-code analysis?
Chris
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/803992
Title:
Natty update
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/803992
Title:
Natty update introduced crasher in xorg
To
18 matches
Mail list logo
