[Bug 1585087] [NEW] *.override files do not work for session jobs

[Martin Pitt]

Public bug reported:

bamfdaemon ships a session job
/usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5) it
should be possible to disable that with an override:

  $ cat /usr/share/upstart/sessions/bamfdaemon.override
  manual

but this doesn't work, bamfdaemon is still started. I also tried to put
"start on disabled" into the *.override file, no effect either.

(Background: I'm trying to migrate jobs to systemd units one by one,
thus for every systemd user unit that I add I need to disable the
corresponding upstart job).

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: upstart 1.13.2-0ubuntu23
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 24 09:23:36 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522)
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: Session
UpstartRunningSessionCount: 1
UpstartRunningSessionVersion: upstart 1.13.2
UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist
upstart.upstart-event-bridge.log:
 upstart-event-bridge stop/pre-start, process 2537
 upstart-event-bridge stop/pre-start, process 3444
 upstart-event-bridge stop/pre-start, process 4582

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1585087

Title:
  *.override files do not work for session jobs

Status in upstart package in Ubuntu:
  New

Bug description:
  bamfdaemon ships a session job
  /usr/share/upstart/sessions/bamfdaemon.conf. According to upstart(5)
  it should be possible to disable that with an override:

    $ cat /usr/share/upstart/sessions/bamfdaemon.override
    manual

  but this doesn't work, bamfdaemon is still started. I also tried to
  put "start on disabled" into the *.override file, no effect either.

  (Background: I'm trying to migrate jobs to systemd units one by one,
  thus for every systemd user unit that I add I need to disable the
  corresponding upstart job).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: upstart 1.13.2-0ubuntu23
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 24 09:23:36 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160522)
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist
  upstart.upstart-event-bridge.log:
   upstart-event-bridge stop/pre-start, process 2537
   upstart-event-bridge stop/pre-start, process 3444
   upstart-event-bridge stop/pre-start, process 4582

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1585087/+subscriptions