I think it's imortant to note that https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=756247#58 warns on the workaround on the grounds that it involves the installation of sytemd. systemd is an alternative to the current default upstart manager (see https://wiki.ubuntu.com/systemd#systemd_-_An_alternative_boot_manager).
Putting aside the controversy ( https://en.wikipedia.org/wiki/Systemd) for the moment, the current Ubuntu implementation of systemd may not be without it's problems and I for one don't know how to roll back to upstart once this particular bug is resolved. My particular problem is that I can't use an ASUS Eeepc until the problem is resolved. I will also not proceed with an upgrade to Utopic on my main machine until resolution. Consequently I would support the elevation of the importance of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
