[Bug 1281036] Re: Why is kdm still depending on consolekit?

[Launchpad Bug Tracker]

This bug was fixed in the package kde-workspace - 4:4.11.6-0ubuntu4

---------------
kde-workspace (4:4.11.6-0ubuntu4) trusty; urgency=medium

  [ Rohan Garg ]
  * Add Dep 3 headers to various kubuntu patches
    - Drop kubuntu_kde-workspace-kwin-touch-mouseevents-translation.diff,
      not required for PA 4
    - Drop upstream_Use-cascaded-configs-for-other-modules-as-well.patch,
      was not being used
  * Switch to new package name in startkde when copying GTK2/3 settings
    (LP: #1232156)

  [ Harald Sitter ]
  * Drop KDM ConsoleKit support. We are using logind everywhere else
    and upstream actually prefers logind in all workspace software, however
    since KDM is semi-unmaintained and feature frozen there won't be logind
    support. ConsoleKit in KDM will not do anything on its own because all
    the applications of the workspace will want to talk to logind when
    present (which is pretty much always due to upstart).
    + Remove consolekit runtime dependency from kdm package.
    + Remove libck-connector-dev build dependency to build without CK.
    + This approach was discussed on the kde-core-devel mailing list
      and is the overwhelmingly accepted thing to do.
    LP: #1281036

  [ Philip Muškovac ]
  * kubuntu_plasma_netbook_for_small_screens.diff:
    - fix detection of optical drives so plasma-netbook doesn't appear in
      low-res virtual machines
 -- Rohan Garg <rohangarg at kubuntu.org>   Fri, 21 Mar 2014 16:58:59 +0100

** Changed in: kde-workspace (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1281036

Title:
  Why is kdm still depending on consolekit?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1281036/+subscriptions