[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor

** Branch linked: lp:ubuntu/utopic-proposed/unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1346819 Title: Unity8 non-upstart tests fight for hardware with

[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor

This bug was fixed in the package unity8 - 7.90+14.10.20140724.1-0ubuntu1 --- unity8 (7.90+14.10.20140724.1-0ubuntu1) utopic; urgency=low [ Michael Zanetti ] * properly parent launcher items (LP: #1347902) [ Michał Sawicz ] * Move the PyDev project files to the root,

[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor

Related Mir bug: bug #1347053 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1346819 Title: Unity8 non-upstart tests fight for hardware with unity-system- compositor

[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor

The upstart tests in unity8 don't actually use upstart, meaning that unity8 and u-s-c fight for hardware. ** Summary changed: - Running unity8 autopilot tests gets aborted with 'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async

[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor

** Tags added: qa-broken-test qa-daily-testing qa-landing-email -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1346819 Title: Unity8 non-upstart tests fight for hardware