new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method

Sorry for being impatient but when can I expect the fixed package to be available?

The packages are currently building.

Then I'll test it on Monday.

Thanks for fixing it so quickly. ;-)
Wish you a nice weekend.

This bug was fixed in the package upstart - 1.12.1-0ubuntu4

---------------
upstart (1.12.1-0ubuntu4) trusty; urgency=medium

  [ Adam Conrad ]
  * Disable chroot sessions by default, add an option to enable chroot
    sessions. (LP: #1277594)
 -- Dimitri John Ledkov <email address hidden> Fri, 11 Apr 2014 22:31:21 +0100

I've tested the new packages and I'm hitting a new issue:

$ sudo initctl reload dbus ; echo "exit code: $?"
initctl: Not running
exit code: 1

misch-9:
"initct: Not running" is a different error messages, it means dbus is not running / there is no main daemon process.

I've run 12.04 live cd, installed upstart from trusty and verified this bug report like so:

$ sudo -i
# initctl version
init (upstart 1.5)
// pid1 is precise upstart
# inictl --version
initctl (upstart 1.12.1)
// initctl is from trusty
# initctl status dbus
dbus start/running, process 1221
// dbus _is_ running
# initctl reload dbus
# echo $?
0
// reload is successful

Thank you Dimitri for the commands. I'll check what's going on in my VM...

And here are the details from my VM:

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.4 LTS"

# dpkg -l | egrep -v '^rc|^ii'
<no output; all packages are healthy>

# dpkg -l | grep upstart
ii upstart 1.5-0ubuntu7.2 event-based init daemon

# initctl version
init (upstart 1.5)

# initctl --version
initctl (upstart 1.5)

# initctl status dbus
dbus start/running, process 699

# ps ax | grep dbus-daemon | grep system
  699 ? Ss 0:00 dbus-daemon --system --fork --activation=upstart

# initctl reload dbus ; echo "exit code: $?"
exit code: 0

>>> apt-get dist-upgrade; apt-get install -f; ...

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS"

# dpkg -l | egrep -v '^rc|^ii'
iF bluez 4.101-0ubuntu13 amd64 Bluetooth tools and daemons
iU gnome-bluetooth 3.8.2.1-0ubuntu4 amd64 GNOME Bluetooth tools
iU gnome-user-share 3.0.4-0ubuntu1 amd64 User level public file sharing via WebDAV or ObexFTP
iU indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2 amd64 System bluetooth indicator.

# dpkg -l | grep upstart
ii libupstart1:amd64 1.12.1-0ubuntu4 amd64 Upstart Client Library
ii upstart 1.12.1-0ubuntu4 amd64 event-based init daemon

# initctl version
init (upstart 1.5)

# initctl --version
initctl (upstart 1.12.1)

# initctl status dbus
dbus start/running

# ps ax | grep dbus-daemon | grep system
  699 ? Ss 0:01 dbus-daemon --system --fork --activation=upstart

# initctl reload dbus ; echo "exit code: $?"
initctl: Not running
exit code: 1

>>> The dist-upgrade/dpkg output doesn't show any irregularities regarding dbus though:
Setting up dbus (1.6.18-0ubuntu4) ...
Installing new version of config file /etc/init/dbus.conf ...
dbus start/running

Dimitri, to me it looks like as if Upstart lost track of the dbus process during the dist-upgrade.
What do you think?

Friendly ping to Dimitri.
Dimitri, should I open a new bug for the new issue I've reported in comment #5 and #8?

Dimitri, I've found the issue! The installation of the libselinux1 package during the dist-upgrade from Precise to Trusty causes this issue!

Here are the details from a freshly installed Ubuntu 12.04.4 amd64 VM:
$ sudo apt-get update -qq && sudo apt-get dist-upgrade -qqy
<no output; no updates>

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.4 LTS"

$ initctl --version
initctl (upstart 1.5)

$ initctl version
init (upstart 1.5)

$ initctl list
avahi-daemon start/running, process 765
...

$ sudo sed -i 's/precise/trusty/g' /etc/apt/sources.list

$ sudo apt-get update -qq
<no ouput; no errors>

$ sudo apt-get install libselinux1 -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  libselinux1
1 upgraded, 0 newly installed, 0 to remove and 1250 not upgraded.
Need to get 58.0 kB of archives.
After this operation, 2,048 B of additional disk space will be used.
Get:1 http://de.archive.ubuntu.com/ubuntu/ trusty/main libselinux1 amd64 2.2.2-1 [58.0 kB]
Fetched 58.0 kB in 0s (330 kB/s)
(Reading database ... 174854 files and directories currently installed.)
Preparing to replace libselinux1 2.1.0-4.1ubuntu1 (using .../libselinux1_2.2.2-1_amd64.deb) ...
Unpacking replacement libselinux1 ...
Setting up libselinux1 (2.2.2-1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

New dmesg lines:
[ 256.032898] init: Re-executing /sbin/init

New syslog lines:
Apr 23 14:51:40 test upstart-socket-bridge[1090]: Disconnected from Upstart
Apr 23 14:51:40 test upstart-udev-bridge[595]: Disconnected from Upstart

$ initctl list
avahi-daemon stop/waiting
...

Workaround:
Before doing the dist-upgrade update the upstart package. Trusty's upstart package has no issues with Trusty's libselinux1 package.

As I've haven't heard back from Dimitri I've opened a bug against libselinux1 to add at least a Breaks to its debian/control file:
https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1313712

Very sorry for the delay in response here, it got lost in piles of my bug mail. I've responded on the libselinux bug report. It is valid, and I will get that SRUed into trusty as soon as possible.

Dimitri, no worries. I guess everybody at Canonical is swamped with work so close to a release date. ;-)
Thank you for taking care of the other bug, too.