Why is kdm still depending on consolekit?

Bug #1281036 reported by Simon Rettberg on 2014-02-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Undecided
Unassigned

Bug Description

As suggested, I'm crossposting this from the questions section:
With 13.10, Ubuntu finally got rid of ConsolieKit by integrating systemd's logind with lightdm, Unity etc. However, kdm still pulls in ConsoleKit (and in 14.04 this will still be the case, according to http://packages.ubuntu.com/trusty/kdm), as it's built with ck support enabled. So the obvious question is: Why? Is it just not really being maintained, since Ubuntu prefers the kde-greeter for lightdm? Other distros have long removed the ck dependency from their kdm packages.

Harald Sitter (apachelogger) wrote :

It uses consolekit, so why would it not pull in consolekit?

Changed in kde-workspace (Ubuntu):
status: New → Incomplete
Simon Rettberg (simon-rettberg) wrote :

Sure it's compiled with consolekit support enabled and thus depends on it, but the question would be why. CK development has long been stopped in favour of systemd's logind. Other distros have ditched CK long ago. Ubuntu was holding on to CK for a while as they didn't want to switch to systemd, but finally included logind in Ubuntu in 13.10 and got rid of CK for their Unity session, also lightdm doesn't depend on CK anymore. Nothing in the default Ubuntu setup needs CK anymore.
Now if I simply want to switch to kdm instead of lightdm, keeping everything else as it is, suddenly I have consolekit running on my system, serving absolutely no purpose. Except for kdm insisting to talk to it when I login in. Which might make kdm happy, but doesn't do anything besides that.
So why isn't CK support disabled in kdm?

Harald Sitter (apachelogger) wrote :

I am consulting with KDE on what they want us to do.

Changed in kde-workspace (Ubuntu):
status: Incomplete → New
Changed in kde-workspace (Ubuntu):
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Fri, 21 Mar 2014 16:58:59 +0100

Changed in kde-workspace (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions