jockey-kde's desktop file got no autostart setting

Bug #369733 reported by Harald Sitter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

KDE's autostart sequence looks like this:
   Window manager startup
   Autostart phase 1
   Session restoration
   Autostart phase 2

In order to influence when an application gets started there are various settings that can be added to the desktop file, one of them being X-KDE-autostart-phase.

Quoting the documentation:
   X-KDE-autostart-phase = phase

         phase = 1 or 2

      Starts the application in the autostart phase specified by 'phase'.
      If this entry is missing or 'phase' < 1, 'phase' defaults to 1. If
      'phase' > 2 the application will not be autostarted since the specified
      autostart phase will never be reached.

So unless phase is set to 2 it will default to phase 1, in order to archive a smoother login experience it is however desirable to have ti start in phase 2 along with other non-essential components.

Revision history for this message
Harald Sitter (apachelogger) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Thanks! Committed to upstream trunk r551.

Changed in jockey (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jockey - 0.5.2-0ubuntu1

---------------
jockey (0.5.2-0ubuntu1) karmic; urgency=low

  * New upstream release 0.5.1:
    - Add yum detection to packaging_system.
    - Implement package installation/removal with PackageKit. (Not used in
      Ubuntu right now).
    - Fully functional on Fedora Core 10.
  * New upstream release 0.5.2:
    - Convert build system to DistUtilsExtra.auto.
    - kde/jockey-kde.desktop.in: Move autostart to phase 2, for smoother
      login. (LP: #369733)
    - ui.py: Make proprietary driver warning less scary. (LP: #381805)
    - jockey-gtk: port from glade to GtkBuilder.
  * debian/control: Bump python-distutils-extra build dependency to ensure
    availability of DistUtilsExtra.auto.
  * debian/control: Drop obsolete python-glade2 dependency.
  * debian/jockey-gtk.install: Install *.ui file instead of *.glade.
  * jockey/oslib.py, ui_help(): Update yelp location for help, thanks Matthew
    East! (LP: #274845)
  * data/handlers/broadcom_wl.py: Require package bcmwl-kernel-source. Drop
    our handling of the module blacklisting, bcmwl-kernel-source now does that
    by itself. (LP: #381678)
  * Move jockey.kdeui Python modules from jockey-common to jockey-kde.
  * debian/control: Drop obsolete restricted-manager-* conflicts/replaces.
  * debian/rules: Drop call to dh_icons, cdbs has done that for us for a long
    time.
  * debian/control: Bump Standards-Version to 3.8.2 (no changes necessary).
  * debian/control: Recommend bcmwl-modaliases, so that the driver is detected
    by default. (LP: #381683)

 -- Martin Pitt <email address hidden> Mon, 29 Jun 2009 16:21:37 +0200

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.