[Bug 1197789] Re: Upstart upgrades are creating problematic processes

[Steve Langasek]

So the processes are almost certainly tied to the mountall-shell job.
Does the problem happen after every reboot?  When it does occur, you can
confirm that it's the mountall-shell job by running 'sudo service
mountall-shell status', which probably shows that the service is
start/running.

There's nothing in mountall that would trigger this behavior because of
a plymouth failure; anything that caused mountall to fail should also
have printed a line out in the upstart log.  So this looks like mountall
is instead dying with a signal from outside.  Any idea what could be
causing such a thing on your system?

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

Title:
  Upstart upgrades are creating problematic processes

Status in “mountall” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 13.10 dev with upstart 1.9-0ubuntu2. I have noticed that the last few upgrades from Upstart are creating the process "/bin/sh -e /proc/self/fd/9" with the child process "/sbin/sulogin". These processes doesn't disappear until the system is rebooted. Trying to manually close these processes will result in an immediate reboot.
  --- 
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: upstart 1.9.1-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-4-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Tags:  saucy
  Uname: Linux 3.10.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UserGroups:
   
  modified.conffile..etc.acpi.powerbtn.sh: [modified]
  modified.conffile..etc.init.acpid.conf: [modified]
  modified.conffile..etc.lxdm.lxdm.conf: [modified]
  mtime.conffile..etc.acpi.powerbtn.sh: 2012-12-28T03:54:47.777320
  mtime.conffile..etc.init.acpid.conf: 2012-12-28T03:54:47.825320
  mtime.conffile..etc.init.control.alt.delete.conf: 2012-12-28T03:55:27.305318
  mtime.conffile..etc.init.tty2.conf: 2012-12-28T03:55:27.321318
  mtime.conffile..etc.init.tty3.conf: 2012-12-28T03:55:27.329319
  mtime.conffile..etc.init.tty4.conf: 2012-12-28T03:55:27.337318
  mtime.conffile..etc.init.tty5.conf: 2012-12-28T03:55:27.349319
  mtime.conffile..etc.init.tty6.conf: 2012-12-28T03:55:27.357318
  mtime.conffile..etc.lxdm.lxdm.conf: 2013-05-18T10:27:48.229151

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