[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Released Status in debconf package in Ubuntu: New Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783 -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736 ** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1 -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Changed in: mir Status: Fix Committed => Fix Released -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1 --- mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium * New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0) - ABI summary: . mirclient ABI unchanged at 9 . mirserver ABI bumped to 42 . mircommon ABI bumped to 7 . mirplatform ABI bumped to 14 . mirprotobuf ABI unchanged at 3 . mirplatformgraphics ABI bumped to 11 . mirclientplatform ABI unchanged at 5 . mirinputplatform ABI bumped to 6 . mircore ABI added, at version 1 - Enhancements: . Added pointer confinement support . Identify Raspberry Pi output types correctly . Added dead key and compose key support . Added gamma support for KMS hardware . Added yakkety and zesty gcc-6 support . Added surface passthrough support for fullscreen clients of nested servers . Introduced a new library `libmircore' . Began migrating from Protobuf to Cap'n Proto starting with events . Began support for VirtualBox (servers now start instead of crashing but full support for GL clients is still missing) . Began support for high precision frame timing, implemented for the KMS, Android and X11 backends so far . Added --display-report support for the X11 backend . Improved reliability of `mirvanity' latency test tool . Moved to using the CSS cursor naming scheme internally, although the old symbolic indentifiers remain unchanged and still work . Added refresh rate to MirSurfaceOutputEvent . Many improvements to automated test quality and coverage . Smoother desktop zoom using mir_proving_server (Super + two fingers) - Bugs fixed: . FTBFS On Zesty: invalid use of 'struct native_handle' (LP: #1638774) . libmirclient-debug-extension-dev install debug/surface.h twice (LP: #1639153) . Mir crashes on virtual box drmModeCrtcSetGamma Function not implemented (LP: #1638220) . Flickering in mir_demo_client_multistream (LP: #1635273) . Camera apps (camera & vanity) never exit (LP: #1635010) . Clients cannot connect when MIR_SOCKET="" (LP: #1634508) . mirtest-dev packaging fails to sepcify boost depends (LP: #1633537) . cursor.h is unclear about mir_diagonal_resize_* (LP: #1626924) . Inconsistent underscores in cursor names (LP: #1632617) . [regression] Accidental libmircommon.so.6 break (LP: #1617865) . [regression] mir demo server fails to start with mx4 (LP: #1615703) . [regression] Trust prompt now shown when starting camera (LP: #1612256) . [regression] make abi-check fails to build (LP: #1626866) . Nested servers prevent overlays or fullscreen bypass (LP: #1262116) . Failed to get PRIME fd from gbm bo (LP: #1607812) . Mir-on-X is difficult to use on 1366x768 laptop (LP: #1590959) . Remove useless message 'Surface 0 DPI' in demos (LP: #1559831) . Mir fails to cross-build with newer sbuild (LP: #1628507) . Infinite loop in AbstractShell::focus_next_session (LP: #1625401) . Destroying a presentation chain doesn't trigger ownership notification to client (LP: #1626503) . Keyboard layout not applied on the shell (LP: #1626435) . Warning, No syntax specified for the proto file (LP: #1624971) . display-report=log reports vsync on non-existent output number (LP: #1621352) . libmirserver-dev missing uuid-dev depends (LP: #1617435) . debian/control missing epoxy (LP: #1617256) . Downstreams need to disable clang diagnostic "-Wreturn-type-clinkage" to build against public headers (LP: #1615587) . mirtest-dev: mock_display_configuration.h uses mg namespace without using it (LP: #1614983) . FTBFS using clang (LP: #1609612) . mesa-kms doesn't fall back to using software cursor if hardware cursor is unavailable (LP: #1610054) . StubGraphicsPlatform::create_display() leaves a dubious state (LP: #1611337) . Mir build/tests fail with gcc-6 and LTO (LP: #1610215) . Cross compiling on xenial fails (LP: #1609329) . Building with -DMIR_PLATFORM=anroid fails (LP: #1609916) . unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" (LP: #1584894) . mir_connection_create_spec_for_tooltip doesn't meet requirements (LP: #1603922) . Updating surface size/location needs to update the pointer confinement (LP: #1604673) . ServerConfigurationOption is not ptest safe (LP: #1607351) . HWC's vsync_signal_on is never called when using HWC 1.0 (LP: #1613373) . mir_connection_create_spec_for_tooltip does not set aux_rect (LP: #1632335) . VMware virtual connector recognized by Mir as "unknown" (LP: #1248072) . Fix code to match the
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2209 -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2180 -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.25.0 ** Changed in: mir Status: In Progress => Fix Committed -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Lukáš Tinkl (lukas-kde) ** Changed in: unity8 (Ubuntu) Assignee: Lukáš Tinkl (lukas-kde) => William Hua (attente) ** Changed in: unity8 (Ubuntu) Status: New => In Progress -- 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/1634508 Title: Clients cannot connect when MIR_SOCKET="" Status in Mir: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_client_egltriangle. The client will refuse to connect. Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
