As part of the big bug review for 16.04 LTS, I think this is a feature request rather than a bug.
** Changed in: unity (Ubuntu) Status: Confirmed => Opinion ** Changed in: libunity (Ubuntu) Status: Confirmed => Opinion ** Changed in: libunity Status: Confirmed => Opinion ** Changed in: unity-2d Status: Confirmed => Opinion ** Changed in: unity Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/811826 Title: Not possible for other docks to use Unity LauncherAPI Status in libunity: Opinion Status in Unity: Opinion Status in unity-2d: Opinion Status in libunity package in Ubuntu: Opinion Status in unity package in Ubuntu: Opinion Bug description: When the launcher API was reported people questioned why unity wouldn't use DockManager. The answer that was given was that unity launcher API was better. It's easier for developers use unity launcher api within their own applications. As a dock developer I agreed and welcomed unity launcher api, it sounded like a good idea and something I would like to implement in my dock. When I started looking in to it the disappointment hit me: libunity requires Unity to be running (or more exactly it requires the unique d-bus address com.canonical.Unity to be in use) otherwise it doesn't send out any signals over dbus. I can hack my way around this by letting my dock register the com.canonical.Unity address but that's not an ideal solution. What will happen then if the user tries to start unity while my dock is running? To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/811826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp