Thank you for posting this bug.
Is this an issue in Maverick?
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can't reproduce it anymore (10.04), seems it has gone away in Karmic.
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
check this bug out:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/370541
the solution:
sudo update-rc.d -f gdm remove
sudo update-rc.d gdm defaults
helps. at least in my case :)
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you
same here. my system is a fresh xubuntu jaunty installation. i'm pretty
sure it happened after an update of the package xserver-video-intel.
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I have the same behavior -- blink on bootup, showing the last messages
from /etc/init.d/scripts, and then the login window with autologin not
working.
This is on an EeePC 900 with an Intel 915GM/GMS/910GML running Intrepid.
Alan
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
I still have the problem with recent Jaunty build (23rd March). Booting
with i915 video card gives me 4 blinks and the autologin doesn't work.
After switching to nVidia (and reconfiguring X), autologin works. I can
provide more information, logs, whatever on request.
--
autologin didn't work
This seems to be caused by the xorg intel video driver. I experience the
bug on a laptop with two video cards: one is an Intel i915 and the other
is nVidia 6600GT. If I start the laptop with nVidia switched on, the
autologin works as expected. If I boot it with the internal i915, the
autologin
I do have the problem in freshly installed Intrepid. Autologin used to
work for me in Hardy and Gutsy on this machine.
Autologin does not work after boot. GDM acts as if no autologin was configured
- it asks for a username and password.
If I restart gdm using the initscript, the autologin
Not for me anymore (on gutsy and hardy).
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
could you try if that's still an issue in hardy or intrepid?
** Changed in: gdm (Ubuntu)
Status: Confirmed = Incomplete
--
autologin didn't work
https://bugs.launchpad.net/bugs/45107
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
For me autologin or timed login doesn't work after boot up. But if i log
in as any user and log out timed login works. I have switched on
debugging but nothing remarkable is registered. The configuration is
registered and autologin and timed login is registered. The user that
shall be logged in
I'm having the same problem - autologin doesn't work on a rather freshly
installed (beginning of august) and up2date dapper.
I used to have:
AutomaticLoginEnable=true
AutomaticLogin=jan
in /etc/gdm/gdm.conf - not having read the comments about gdm.conf-custom ;)
But then I reverted this to
João, your issue is not the same, it's probably bug #49940
--
autologin didn't work
https://launchpad.net/bugs/45107
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
13 matches
Mail list logo
