[Bug 1415514] Re: No /dev/uinput and Upstart cannot be contacted

2015-01-29 Thread Martin Pitt
Fixed in http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=a2016a2e and http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=a1a157b . ** Changed in: autopkgtest (Ubuntu) Importance: Undecided = Medium ** Changed in: autopkgtest (Ubuntu) Status: New

[Bug 1415514] Re: No /dev/uinput and Upstart cannot be contacted

2015-01-29 Thread Martin Pitt
It seems the main problem here is that this command in the setup script fails now in current vivid: echo DBUS_SESSION_BUS_ADDRESS=\$(initctl --user get-env DBUS_SESSION_BUS_ADDRESS) gives initctl: Unknown job: rc It seems something in upstart changed recently that now causes a new env

[Bug 1415514] Re: No /dev/uinput and Upstart cannot be contacted

2015-01-29 Thread Launchpad Bug Tracker
** Branch linked: lp:debian/autopkgtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415514 Title: No /dev/uinput and Upstart cannot be contacted To manage notifications about this bug go to:

[Bug 1415514] Re: No /dev/uinput and Upstart cannot be contacted

2015-01-29 Thread Launchpad Bug Tracker
This bug was fixed in the package autopkgtest - 3.9.4 --- autopkgtest (3.9.4) unstable; urgency=medium * Recognize modern Package-Type: control field in addition to XC-Package-Type. * ssh-setup/adb: Guard adb wait-for-device with a 5 min timeout. (LP: #1414939) *

[Bug 1415514] Re: No /dev/uinput and Upstart cannot be contacted

2015-01-29 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/autopkgtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415514 Title: No /dev/uinput and Upstart cannot be contacted To manage notifications about