[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
This bug was fixed in the package mir - 0.1.9+14.10.20140430.1-0ubuntu1 --- mir (0.1.9+14.10.20140430.1-0ubuntu1) utopic; urgency=medium [ Daniel van Vugt ] * New upstream release 0.1.9 (https://launchpad.net/mir/+milestone/0.1.9) - mirclient ABI unchanged, still at 7. Clients do not need rebuilding. - mirserver ABI bumped to 19. Shells need rebuilding. - More libmirserver class changes and reorganization, including; . Moving things from shell:: to scene:: . Rewriting/refactoring surface factories. - Added an id() to Renderable. - Scene/Renderer interfaces: . Scene is no longer responsible for its own iteration (no for_each any more). Instead you should iterate over the list returned by Scene::generate_renderable_list(). - Bugs fixed: . Stale socket issue. (LP: #1285215) . Qt render gets blocked on EGLSwapBuffers. (LP: #1292306) . Lock order violated found in helgrind (potential deadlock). (LP: #1296544) . [regression] SwitchingBundle in framedropping mode can hang. (LP: #1306464) . [DPMS] Display backlight turns back on almost immediately after being turned off. (LP: #1231857) . Wrong frame is seen on wake up/resume/unlock. (LP: #1233564) . Nested platform is not testable (LP: #1299101) . [regression] mir_demo_server_shell crashes on display resume. (LP: #1308941) . Multi-threaded composition is actually mostly serialized by SurfaceStack::guard. (LP: #1234018) . Mirscreencast slows down compositing and makes it very jerky. (LP: #1280938) . Mirscreencast can cause clients to render faster than the screen refresh rate. (LP: #1294361) . Screen turns on when a new session/surface appears. (LP: #1297876) . mir-doc package is >56MB in size, expands to >100MB of files. (LP: #1304998) . [regression] Clang: 'mir::test::doubles::MockSurface::visible' hides overloaded virtual function [-Woverloaded-virtual]. (LP: #1301135) . [regression] GLRenderer* unit tests have recently become noisy. (LP: #1308905) . FocusController::set_focus_to() no longer seems to raise a session to the top. (LP: #1302689) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily releaseWed, 30 Apr 2014 13:26:58 + ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Branch linked: lp:~albaguirre/mir/alternate-fix-1285215 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Changed in: mir Assignee: (unassigned) => Alberto Aguirre (albaguirre) ** Changed in: mir Milestone: None => 0.1.9 ** Changed in: mir Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Branch linked: lp:~albaguirre/mir/fix-1285215 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
This bug was fixed in the package unity8 - 7.84+14.04.20140228-0ubuntu1 --- unity8 (7.84+14.04.20140228-0ubuntu1) trusty; urgency=low [ Michał Sawicz ] * Fix CardHeader title font weight. * Delete stale sockets. (LP: #1285215) [ Dmitrijs Ledkovs ] * Ship python3 autopilot modules. [ Albert Astals ] * Cleanup DashContent Remove unused signals and properties [ Michał Karnicki ] * Take it easy on the logging. * Fix CardHeader title font weight. [ Nick Dedekind ] * Added ability to change indicator profile in shell (env UNITY_INDICATOR_PROFILE) [ Andrea Cimitan ] * Rename PreviewRating to PreviewRatingInput * Adds PreviewRatingDisplay [ Daniel d'Andrada ] * DirectionalDragArea: Reset status if disabled while dragging (LP: #1276122) [ Dimitri John Ledkov ] * Ship python3 autopilot modules. -- Ubuntu daily releaseFri, 28 Feb 2014 10:48:06 + ** Changed in: unity8 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Branch linked: lp:ubuntu/trusty-proposed/unity8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
yes, separate to this there is a unity8/qt crash occuring. however, this is kind of a recurring theme so we could alleviate some heart burn by providing some sort of mechanism to detect/dispatch stale sockets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
In theory this could only occur if the first server has crashed or lost power (forced off). Was there a crash preceding this we need to fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
from ubuntu-phone mailer xnox said "File socket should not be used at all, as they are known to be racy and can easily end up stale, instead an abstract unix domain socket should be used throughout. This is not the first time, where stale, and not properly cleared file sockets in mir are causing severe breakage on touch. With an abstract socket, there is no file on a filesystem, and thus when a process is gone the socket is also gone. You can see examples of abstract sockets in: upstart, dbus-daemon, and plenty of other system level daemons on ubuntu." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
** Branch linked: lp:~saviq/unity8/drop-stale-socket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
making critical, as we just need to clean this one up. per mterry suggestion "fuser $MIR_SOCKET" and if no one else is using it, delete it no matter what we need some mechanism to take care of stale/orphaned sockets ** Changed in: mir Importance: Medium => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use]
In that case making the unity8 task invalid. ** Changed in: unity8 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1285215] Re: Unity fails to start sometimes in CI resulting in screen unlock failure [ what(): bind: Address already in use]
I think this happens when you have a lingering socket file from the previous server: /tmp/mir_socket or wherever it is. Mir (server) doesn't contain any smarts to test the validity of existing socket files. I'm assuming the old server is dead. In that case we'd need a way to probe if a socket file is presently opened by any other (server) process. If not then delete it and try again. ** Summary changed: - Unity fails to start sometimes in CI resulting in screen unlock failure + Unity fails to start sometimes in CI resulting in screen unlock failure [ what(): bind: Address already in use] ** Changed in: mir (Ubuntu) Status: New => Triaged ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Summary changed: - Unity fails to start sometimes in CI resulting in screen unlock failure [ what(): bind: Address already in use] + Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] ** Changed in: mir Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1285215 Title: Unity fails to start sometimes in CI resulting in screen unlock failure [what(): bind: Address already in use] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1285215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
