Interesting! Soon maybe I will try KMS, when I am working on a system
that supports it.
For now, on the system with the Nvidia, I removed the proprietary driver
again, so now autologin seems to work fine. I did try the earlier,
version 96 drivers, but found the same problem. Also I no longer
su
P.S. I do not have any encrypted volume.
--
GDM autologin not working on Karmic ONLY AFTER using Jaunty (or probably also
older ubuntu versions) and rebooting into Karmic
https://bugs.launchpad.net/bugs/462201
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I put the nvidia driver back (version 173.14.20; the card is a GeForce
FX 5500). Right away on the first restart, I was required to log in.
In six restarts since putting the driver back, three have gone through
automatically; the other three required me to log in.
If I set TimedLoginEnable=true,
Five more successful autologins; that makes 10 in a row. Before I
removed the nvidia driver, I was getting stopped by the login screen
around half the time. Now I wlll try putting the nvidia driver back, to
verify that it triggers the bug. Also I may try an earlier version of
the driver.
--
GD
Could it be related to a proprietary display driver? I had been using
an Nvidia driver, but I just removed it, and succeeded in logging in
automatically five times in a row, so far. I will try some more
tomorrow, and let you know what happens.
--
GDM autologin not working on Karmic ONLY AFTER u
P.S. Here is my /etc/gdm/custom.conf
It shows timed login disabled, but the bug seems to be the same, whether timed
login is enabled or disabled.
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=garrett
TimedLoginEnable=false
TimedLogin=garrett
TimedLoginDelay=1
--
GDM autologin not workin
Jigoita wrote on 2009-10-27:
> I did several reboots, and I could get autologin working for two times. But
> now it is not working again. It seems to happen randomly.
That sounds like the problem I, too, am having (but in my case, I think
it does not matter what I booted previously; it can happe
This may be the same as 267324
( https://bugs.launchpad.net/ubuntu/+source/evince/+bug/267324 )
supposed to be fixed upstream in libpoppler.
Garrett
--
evince crashed with SIGFPE, trying to seek in KXTGA930.PDF
https://bugs.launchpad.net/bugs/277294
You received this bug notification because you
Pedro,
How do I obtain a backtrace in Intrepid?
The page
http://wiki.ubuntu.com/DebuggingProgramCrash
does not mention Intrepid. Nevertheless, I tried using:
deb http://ddebs.ubuntu.com intrepid main universe
deb http://ddebs.ubuntu.com intrepid-updates main universe
deb http://ddebs.ubuntu.