touch-packages team mailing list archive

[Robie Basak <1436691@xxxxxxxxxxxxxxxxxx>]

** Tags added: systemd-boot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1436691

Title:
  Essential files are missing

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.04 dev and upstart 1.13.2-0ubuntu10 doesn't contain files like /sbin/init anymore. This caused that after upgrading to this package I wasn't able to reboot/shutdown my system and to fully boot it after a hard reboot.
  --- 
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  NonfreeKernelModules: nvidia
  Package: upstart 1.13.2-0ubuntu9 [origin: unknown]
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Tags: third-party-packages vivid
  Uname: Linux 3.19.0-10-generic x86_64
  UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Unable to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Unable to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  modified.conffile..etc.init.acpid.conf: [modified]
  modified.conffile..etc.init.cgmanager.conf: [modified]
  modified.conffile..etc.init.d.acpid: [modified]
  mtime.conffile..etc.init.acpid.conf: 2014-02-19T20:08:15.825697
  mtime.conffile..etc.init.cgmanager.conf: 2015-02-25T20:58:42.596226
  mtime.conffile..etc.init.control.alt.delete.conf: 2014-08-16T13:50:31.422130
  mtime.conffile..etc.init.d.acpid: 2014-05-30T01:07:43.027750
  mtime.conffile..etc.init.tty2.conf: 2014-08-16T13:50:31.430130
  mtime.conffile..etc.init.tty3.conf: 2014-08-16T13:50:31.434130
  mtime.conffile..etc.init.tty4.conf: 2014-08-16T13:50:31.438130
  mtime.conffile..etc.init.tty5.conf: 2014-08-16T13:50:31.442130
  mtime.conffile..etc.init.tty6.conf: 2014-08-16T13:50:31.446130

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1436691/+subscriptions