Re: [Bug 1007221] Re: Removing /etc/hostname results in failed first login attempt
On 05/06/12 06:42, Mathieu Trudel-Lapierre wrote: Indeed, ubiquity doesn't bother with checking the DHCP host name. Perhaps it should -- that would be a bug in ubiquity. This is possibly why you can't replicate the issue on virtual machines, in this case are you using the alternate installer? No, all installations have been done from scratch using the standard installer, except for one which was an upgrade from 10.04. Regardless, it's not really supported to remove /etc/hostname. The file should instead be modified if the hostname for the system changes, along with /etc/hosts (since it contains a pointer to 127.0.1.1 for that name). At the same time, if lightdm fails to find the hostname (which is normal if it's just looking for it in /etc/hostname), it's behaving correctly in showing localhost. Yeah I'm aware removing /etc/hostname isn't a good move. The story of how I ended up down this path is that in 10.04 you could set /etc/hostname to the magic string (none) and the DHCP supplied hostname would be honored. On my desktop the upgrade to 12.04 removed /etc/hostname (it had the magic string), and so I figured that was no longer supported. However the DHCP supplied hostname was still honored, though I had this login bug. There didn't seem to be another way to have the DHCP hostname honored. Having the DHCP hostname honored is convenient for us as it simplifies image deployment. Blat the image onto the desktop, stick it on the network, it picks up its hostname from DHCP and off we go, minimal intervention required. It's not a huge hassle to change /etc/hostname post image deployment, but it's something we didn't used to have to do. That may or may not have been interesting/useful to you. What *is* broken is that the desktop doesn't continue to load cleanly and instead falls back to the greeter. There needs to be some more investigation at the lightdm level for this; for the reasons listed by Sebastien. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007221] Re: Removing /etc/hostname results in failed first login attempt
Mathieu, In this case yes, installation was done on the same network so the same DHCP server and lease info was used/received. Doing a standard install from a live disk Ubuntu doesn't seem to use the DHCP supplied hostname: the live disk hostname is ubuntu, and the gui installer auto-generates a hostname from the user information + hardware info (like model string from BIOS). The installer won't let you have a blank hostname. At no point during installation do I see or get the option to use the DHCP supplied hostname. As an update re: virtual machines I can't replicate this at all on a VBox VM, but have no trouble reproducing it on bare metal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Just an update that I still get this very infrequently - maybe once a week across many reboots of several machines - post applying the 'DEVPATH=*card0' fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007221] [NEW] Removing /etc/hostname results in failed first login attempt
Public bug reported: We assign hostnames to machines using dhcp. For this to work in 12.04 you seem to have to remove /etc/hostname (or have it empty, the behaviour is the same). However doing this results in the first attempted graphical login after boot failing. I have reproduced this behaviour across several machines, from upgrades and clean installations, and can turn it on and off by removing /etc/hostname, or making it non-empty. The symptoms are: - At the greeter prompt the hostname at screen top left is set to localhost - If I switch to a console prompt the hostname displays correctly (i.e. not localhost) - After successfully entering a uname/pwd you briefly get a desktop for one second or so, then it drops to the console for half a sec or so, then the greeter re-appears. - Once the greeter re-appears the hostname will be set correctly at screen top left, and subsequents logins successfully proceed to the desktop .x-session-errors has some lines about xrdb being unable to open display:0, other logs in /var/log/lightdm/ seem ok, but I'll include them too. I've run strace -ff -p lightdm but am not familiar enough with the graphical login process to make much headway there, and I've yet to turn up an obvious - to me - error, though paging through strace output tends to make ones eyes glaze over :) Curiously I can't replicate this in a VBox VM. Fresh install, exact same configuration but it displays the hostname properly at screen top left and the first login proceeds normally. I will make the VM name and dhcp hostname different and see if this reveals the bug. Regards ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007221] Re: Removing /etc/hostname results in failed first login attempt
** Attachment added: .xsession-errors failed login https://bugs.launchpad.net/bugs/1007221/+attachment/3171002/+files/xsession-errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007221] Re: Removing /etc/hostname results in failed first login attempt
** Attachment added: x-0-greeter.log https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+attachment/3171004/+files/x-0-greeter.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007221] Re: Removing /etc/hostname results in failed first login attempt
** Attachment added: lightdm.log https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+attachment/3171003/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007221 Title: Removing /etc/hostname results in failed first login attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1007221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970234] Re: Selecting spice and qxl mode results in blank screen
+1 for WinXP guest blank screen and 100% cpu when trying to boot with spice+qxl. My install is an amd64 upgrade from 11.10. Happy to provide more details/testing if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970234 Title: Selecting spice and qxl mode results in blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm-spice/+bug/970234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Changing 'card0' to 'DEVPATH=*card0' seems to have fixed the problem for me, at least across a half dozen reboots. Udev log attached. ** Attachment added: udev log https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/969489/+attachment/3160255/+files/udev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
I'm getting the same symptom - more often than not getting dropped to the low-graphics alert during startup - and the change to /etc/init/lightdm.conf listed above has *not* made a difference. This behaviour is consistent across several different machines. From googling around this bug seems fairly prevalent, and is graphics vendor/chipset agnostic which supports your reasoning above. However as noted the prooposed change hasn't helped me. Looking through logs in /var/log/lightdm the only thing that stands out is in the greeter logs e.g. for a failed start: No protocol specified No protocol specified ... (unity-greeter:2340): Gtk-WARNING **: cannot open display: :0 No protocol specified ... I'm happy to try out other ideas for fixes as this is a show stopper for a desktop environemnt refresh under way at work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
