[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Description changed:

+ = Summary =
+ 
+ The version of Upstart in vivid is affected by a coule of bugs relating
+ to the flushing data from early-boot jobs to disk which can both result
+ in a crash:
+ 
+ == Problem 1 ==
+ 
+ An internal list is mishandled meaning a crash could occur randomly.
+ 
+ == Problem 2 ==
+ 
+ Jobs which spawn processes in the background then themselves exit can
+ cause a crash due.
+ 
+ = Explanation of how Upstart flushes early job output =
+ 
+ If an Upstart job starts *and ends* early in the boot sequence (before
+ the log partition is mounted and writable) and produces output to its
+ stdout/stderr, Upstart will cache the output for later flushing by
+ adding the 'Log' object associated with the 'Job' to a list.
+ 
+ When the log partition is mounted writable, the
+ /etc/init/flush-early-job-log.conf job is run which calls initctl
+ notify-disk-writeable. This is a signal to Upstart to flush its cache
+ of early-boot job output which takes the form of iterating the
+ 'log_unflushed_files' list and flushing all the 'Log' entries to disk.
+ 
+ = Code Specifics =
+ 
+ There are 2 issues (note that the numbers used below match those used in
+ the Summary).
+ 
+ == Problem 1 detail ==
+ 
+ Due to a bug in the way the 'log_unflushed_files' list is handled (the
+ 'Log' cannot be added to the list directly, so is added via an
+ intermediary ('NihListElem') node), a crash can result when iterating
+ the list since the 'Log' is freed, but NOT the intermediary node. The
+ implication is that it is possible for the intermediary node to be
+ attempt to dereference already-freed data, resulting in a crash.
+ 
+ == Problem 2 detail ==
+ 
+ If a job spawns a process in the background, then itself exits, that
+ jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
+ if the background process produces output and then exits before Upstart
+ attempts to flush the original jobs data to disk, the 'NihIo'
+ corresponding to the log will be serviced automatically and the data
+ flushed to disk. The problem comes when Upstart receives the
+ notification to flush the 'log_unflushed_files' list, since that list
+ now contains an entry which has already been freed (since all its data
+ has already been flushed). The result is an assertion failure.
+ 
+ = Fix =
+ 
+ == Problem 1 fix ==
+ 
+ Correct the 'log_unflushed_files' list handling by freeing the
+ 'NihListElem' (which will automatically free the 'Log' object), not by
+ simply freeing the 'Log' object itself.
+ 
+ * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
+ * New Upstart test added to avoid regression?: Yes.
+ 
+ == Problem 2 fix ==
+ 
+ Correct the assumption that the only entries in the
+ 'log_unflushed_files' list will always have data to flush by checking if
+ there is in fact any data to flush; if not, remove the entry from the
+ 'log_unflushed_files' list since it has already been handled
+ automatically by the 'NihIo'.
+ 
+ * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
+ * New Upstart test added to avoid regression?: Yes.
+ 
+ = Workarounds =
+ 
+ If a system is affected by this bug, it will be manifested by a crash
+ early in the boot sequence.
+ 
+ To overcome the issue, either:
+ 
+ a) Boot by adding --no-log to the kernel command-line.
+ 
+ b) Disable the flush-early-job-log job (assuming the machine is
+ bootable) by running the following:
+ 
+$ echo manual | sudo tee -a /etc/init/flush-early-job-log.override
+ 
+ = Impact =
+ 
+ The issue has been present in Upstart since logging was introduced but
+ no known instances of crashes relating to these problems have been
+ reported prior to this bug being reported (which relates the the issue
+ being seen on a very small subset of specific Ubuntu Touch phone
+ hardware where Upstart is used as the system init daemon).
+ 
+ Note that vivid still uses Upstart for managing the graphical session,
+ but now uses systemd by default for the system init daemon. Since the session 
(Upstart) init does not even require 
+ a flush-early-job-log, the exposure to both the bug and the updated fix 
codepath is extremely limited.
+ 
+ = Test Case =
+ 
+ This bug is extremely hard to surface so the approach is simply to check
+ that the internal list can be iterated correctly by:
+ 
+ 1) Booting the system with upstart
+(select the Upstart option from the grub menu or add init=/sbin/upstart 
to the kernel command-line).
+ 
+ 2) Running the following on a system booted with Upstart:
+ 
+$ for i in $(seq 17); do sudo start flush-early-job-log; done
+ 
+ = Regression Potential =
+ 
+ None expected:
+ 
+ - As noted in Impact, the problems fixed by this version of Upstart have not 
been observed on server/desktop systems before.
+ - The fix is already in wily and no problems have been reported.
+ - See Impact.
+ 
+ = Original Description =
+ 
  We recently started getting reprots from phone users that their devices
  go into a reboot loop after 

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Changed in: upstart (Ubuntu Vivid)
   Status: New = In Progress

** Changed in: upstart (Ubuntu Vivid)
 Assignee: (unassigned) = James Hunt (jamesodhunt)

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  In Progress
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops

[James Hunt]

Hi Steve - ah, sorry - hadn't registered that you'd already copied the
package into the queue (we now have 2 :-) Could mine be deleted please?

-- 
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/1447756

Title:
  [SRU] segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  In Progress
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  = Summary =

  The version of Upstart in vivid is affected by a coule of bugs relating
  to the flushing data from early-boot jobs to disk which can both result
  in a crash:

  == Problem 1 ==

  An internal list is mishandled meaning a crash could occur randomly.

  == Problem 2 ==

  Jobs which spawn processes in the background then themselves exit can
  cause a crash due.

  = Explanation of how Upstart flushes early job output =

  If an Upstart job starts *and ends* early in the boot sequence (before
  the log partition is mounted and writable) and produces output to its
  stdout/stderr, Upstart will cache the output for later flushing by
  adding the 'Log' object associated with the 'Job' to a list.

  When the log partition is mounted writable, the
  /etc/init/flush-early-job-log.conf job is run which calls initctl
  notify-disk-writeable. This is a signal to Upstart to flush its cache
  of early-boot job output which takes the form of iterating the
  'log_unflushed_files' list and flushing all the 'Log' entries to disk.

  = Code Specifics =

  There are 2 issues (note that the numbers used below match those used in
  the Summary).

  == Problem 1 detail ==

  Due to a bug in the way the 'log_unflushed_files' list is handled (the
  'Log' cannot be added to the list directly, so is added via an
  intermediary ('NihListElem') node), a crash can result when iterating
  the list since the 'Log' is freed, but NOT the intermediary node. The
  implication is that it is possible for the intermediary node to be
  attempt to dereference already-freed data, resulting in a crash.

  == Problem 2 detail ==

  If a job spawns a process in the background, then itself exits, that
  jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
  if the background process produces output and then exits before Upstart
  attempts to flush the original jobs data to disk, the 'NihIo'
  corresponding to the log will be serviced automatically and the data
  flushed to disk. The problem comes when Upstart receives the
  notification to flush the 'log_unflushed_files' list, since that list
  now contains an entry which has already been freed (since all its data
  has already been flushed). The result is an assertion failure.

  = Fix =

  == Problem 1 fix ==

  Correct the 'log_unflushed_files' list handling by freeing the
  'NihListElem' (which will automatically free the 'Log' object), not by
  simply freeing the 'Log' object itself.

  * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
  * New Upstart test added to avoid regression?: Yes.

  == Problem 2 fix ==

  Correct the assumption that the only entries in the
  'log_unflushed_files' list will always have data to flush by checking if
  there is in fact any data to flush; if not, remove the entry from the
  'log_unflushed_files' list since it has already been handled
  automatically by the 'NihIo'.

  * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
  * New Upstart test added to avoid regression?: Yes.

  = Workarounds =

  If a system is affected by this bug, it will be manifested by a crash
  early in the boot sequence.

  To overcome the issue, either:

  a) Boot by adding --no-log to the kernel command-line.

  b) Disable the flush-early-job-log job (assuming the machine is
  bootable) by running the following:

 $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override

  = Impact =

  The issue has been present in Upstart since logging was introduced but
  no known instances of crashes relating to these problems have been
  reported prior to this bug being reported (which relates the the issue
  being seen on a very small subset of specific Ubuntu Touch phone
  hardware where Upstart is used as the system init daemon).

  Note that vivid still uses Upstart for managing the graphical session,
  but now uses systemd by default for the system init daemon. Since the session 
(Upstart) init does not even require 
  a flush-early-job-log, the exposure to both the bug and the updated fix 
codepath is extremely limited.

  = Test Case =

  This bug is extremely hard to surface so the approach is simply to
  check that the internal list can be iterated 

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Unfortunately, ondra no longer has the failing phones so we may need to
take a decision to just land this if QA are happy the change has not
regressed the behaviour for non-failing phones.

I've tried to raise QA but they are sprinting in the US this week so no
direct response.

I believe that sil2100 is doing what he can atm, but it's unclear
whether this fix will make it into the next OTA at this stage.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  New
Status in upstart source package in Vivid:
  New
Status in upstart source package in Wily:
  Fix Released

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Thanks for nudging -proposed Steve.

I've silo 021 now includes  upstart version 1.13.2-0ubuntu13.1 (which
sil2100 synced from wily).

Basic test plan is here: https://wiki.ubuntu.com/Process/TestPlans
/upstart-bug-1447756

I've tested this as follows:

$ wget http://people.canonical.com/~jhm/barajas/recovery.img
$ ubuntu-device-flash --verbose touch --bootstrap 
--channel=ubuntu-touch/rc-proposed/bq-aquaris.en --device krillin 
--recovery-image ./recovery.img
$ citrain device-upgrade 021

I then reflashed the boot.img using one from ondra which drops the
current '--no-log' option from /proc/cmdline and rebooted.

As far as I'm concerned, the fix is good. All that now remains is for
ondra or one of the folk in London who have the failing krillin
devices to test the above.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  New
Status in upstart source package in Vivid:
  New
Status in upstart source package in Wily:
  Fix Released

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file

[James Hunt]

Hi Andy - any progress on this? Although the buildd's are running older
kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and
is thus causing upstart tests to fail. For example:

https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-
upstart/ARCH=amd64,label=adt/lastBuild/

If it will take a while to resolve this, I guess we'll have to consider
disabling the test for now. However, doing so is going to change the
behaviour of the upstart logger.

-- 
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/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Looks like kernel bug 1429756 could block 1.13.2-0ubuntu14 landing for
wily (being a pre-req to getting this fix into vivid and utopic):

https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-
adt-upstart/ARCH=amd64,label=adt/9/

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  In Progress
Status in upstart source package in Utopic:
  New
Status in upstart source package in Vivid:
  New
Status in upstart source package in Wily:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Changed in: upstart
   Status: In Progress = Fix Committed

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Also affects: upstart (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: upstart (Ubuntu Wily)
   Importance: Critical
 Assignee: James Hunt (jamesodhunt)
   Status: In Progress

** Also affects: upstart (Ubuntu Vivid)
   Importance: Undecided
   Status: New

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  Fix Committed
Status in upstart package in Ubuntu:
  In Progress
Status in upstart source package in Utopic:
  New
Status in upstart source package in Vivid:
  New
Status in upstart source package in Wily:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Applying the top 2 commits (r1665 and r1666) from
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix [1] to
https://bugs.launchpad.net/ubuntu-
rtm/+source/upstart/1.13.2-0ubuntu1rtm1 is now working for me.

I've tested this by building on the device itself and also by building
in a ARCH=armhf utopic chroot [2].

__

[1] - Equivalent to the attached patch.
[2] - Interestingly, building in an vivid ARCH=armhf chroot generates a binary 
that fails at runtime.

** Patch added: bug-1447756-both-fixes.diff
   
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1447756/+attachment/4396882/+files/bug-1447756-both-fixes.diff

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  In Progress
Status in upstart package in Ubuntu:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

MP raised on lp:upstart to start the trickle-down to the rtm package.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  In Progress
Status in Upstart:
  In Progress
Status in upstart package in Ubuntu:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix contains the fix and
a new test (which correctly fails with the current lp:upstart but passes
with the fix in that branch).

The code has been tested on a failing device and a server system. I am
currently testing on a non-failing krillin device. I understand Ondra is
going to test on a couple of other devices that exhibit this bug to
further sanity check the code.

Once all these tests pass I'll raise an MP for the branch above to get
it merged to lp:upstart.

We'll then need to cherry pick the fix into both vivid and wily.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  In Progress
Status in upstart package in Ubuntu:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Ondrej - aha! with the debug, this is making more sense now. Yes, since
the ureadahead-touch job spawns a process in the background (ureadahead)
and then the job itself exits, the log associated with the main job
process gets added to the unflushed list. ureadahead then writes output
and the NihIo is automatically serviced to flush the log to disk and set
log-unflushed-len to zero. Later, 'initctl notify-disk-writable' gets
called and the assert fires as all the output from both /etc/init
/ureadahead-touch.conf and from the ureadahead daemon itself has already
been logged.

Could you try the following which should be a minimal fix:
http://paste.ubuntu.com/11095313/

Another point - the fact that ureadahead-touch is triggering the problem
does point to an issue with that job - as can be seen, even when the
script section ends (and that associated shell dies), 'ureadahead
--daemon' continues and if it produces output, that gets logged. A
simple work-around is to remove --daemon so that the job process and the
log never become detached.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Hi Ondrej,

Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'initctl notify-disk-writeable' gets called, if you look at
log_handle_unflushed()...

 743 log_handle_unflushed (void *parent, Log *log)
 744 {
 745 NihListEntry  *elem;
 746 
 747 nih_assert (log);
 748 nih_assert (log-detached == 0);
 749 
 750 log_read_watch (log);
 751 
 752 if (! log-unflushed-len)
 753 return 1;

So, if the write is successful and log-unflushed-len becomes zero, the
function returns 1 (meaning log does not need to be added to the
unflushed list) and crucially the log is not added to the unflushed
list.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Hi Ondrej,

Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before 'initctl notify-disk-writeable' gets called, if you look at
log_handle_unflushed()...

 743 log_handle_unflushed (void *parent, Log *log)
 744 {
 745 NihListEntry  *elem;
 746 
 747 nih_assert (log);
 748 nih_assert (log-detached == 0);
 749 
 750 log_read_watch (log);
 751 
 752 if (! log-unflushed-len)
 753 return 1;

So, if the write is successful and log-unflushed-len becomes zero, the
function returns 1 (meaning log does not need to be added to the
unflushed list) and crucially the log is not added to the unflushed
list.

Regarding #16, there shouldn't be a problem in that scenario since when
the log gets added to the unflushed list, it is totally detached from
its parent job. Hence, the job can be destroyed but the log lives on as
an element of the unflushed list. If that job gets recreated, it will
get a new set of log objects associated with it.

Did you manage to get the full log_clear_unflushed() debug output in the
end?

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

\o/. Yes, Upstart uses asserts extremely agressively. It's unfortunate
that we've never hit this issue in testing but I'm currently working on
new tests for this slightly unusual scenario.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Changed in: upstart (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: upstart
   Status: New = In Progress

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  In Progress
Status in upstart package in Ubuntu:
  In Progress

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

ondra and I have been hammering away at this, but progress is painfully
slow given that:

a) the problem is not seen on every boot.
b) we can only view the end of kmsg log.
c) rebuild times are relatively slow.

From what ondra says he's seen today, it sounds as though we might be
hitting a stack corruption issue - the debug I've given him is not being
displayed as expected. Even with the initial fix I created based on code
inspection alone, ondra is still seeing exactly the same assertion
failure which we thought would have been fixed by the initial fix for
this bug.

I've tried various ways to recreate the issue (both on a device and on a
normal system, code review / code analysis tools, runtime checkers), but
have so far been unsuccessful.

Current work-arounds:

1) Keep using '--no-log' in the kernel command-line.
Pros: reliable.
   Cons: means that no system jobs get their output logged.

2) Disable the /etc/init/flush-early-job-log.conf job.
Pros: seems to be reliable (? but needs further testing).
Cons:  means early job output is not logged (however, on the device in 
question the only output seems to be from /etc/init/container-detect.conf (and 
that output is not even required).

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

I've rebuild the fix in a clean environment and the init binary below
now boots fine for me on a bq aquaris E4.5:

http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Hi ondra/ogra - Can you comment on my suggestions in #6 and #7? My
device is still bricked so if you have any suggestions on how to perform
a full reset, that'd be great as udf is unable to recover it.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) = James Hunt (jamesodhunt)

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

I think I understand what's happening now - it's not the log that isn't
being freed, it's the list entry the log is attached to that is not
freed. The effect is the same though - calling log_clear_unflushed()
multiple times could trigger this issue since the still-valid (but
incorectly so) list entry is now pointing at potentially garbage memory
where a Log used to be.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)

[James Hunt]

Screenshot showing the super-thin divider.

** Attachment added: scratch.jpg
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg

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

Title:
  [Greeter] horizonal rule on pin unlock screen too thin (looks like a
  scratch)

Status in Ubuntu UX bugs:
  In Progress
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The pin code entry screen has what appears to be a 1 pixel high line
  horizontal line that goes almost to the left and right borders of the
  screen, just above the unlock keypad.

  I can see the value of such a horizontal rule but it is _so_ thin that
  when I looked at it earlier I thought I'd either scratched the screen
  or damaged it somehow.

  Could we possibly make it slightly thicker (or dotted or something) to
  make it more obviously a ruler and less possibly a scratch/screen
  damage? :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Test binaries are available here:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

** Also affects: upstart
   Importance: Undecided
   Status: New

** Changed in: upstart
 Assignee: (unassigned) = James Hunt (jamesodhunt)

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

I've tried the fix on my bq device and it appears to be in a reboot loop
(like the one the fix was supposed to resolve).

As such, I'd recommend testing the binaries only for the session init
initially (/usr/bin/ubuntu-touch-session / /usr/share/lightdm/sessions
/ubuntu-touch.desktop).

Also, for both system and session scenarios, I'd recommend adding '--
debug' to get as much detail as possible.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[James Hunt]

Something else to try - disable /etc/init/flush-early-job-log.conf on
boot...

$ sudo mount -oremount,rw /
$ echo manual | sudo tee /etc/init/flush-early-job-log.override
$ sudo reboot

... and post-boot do the following:

$ for i in $(seq 17); do sudo initctl notify-disk-writeable; done

As Steve has mentioned, we do need to trace down why 'initctl notify-
disk-writeable' seems to be being called multiple times on boot though -
it should only really be called once when (in the case of Touch)
/var/log/ is writable.

-- 
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/1447756

Title:
  segfault in log.c code causes phone reboot loops

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log-unflushed-len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file

[James Hunt]

LKML thread: https://lkml.org/lkml/2015/3/16/474

-- 
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/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

[James Hunt]

** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu)

-- 
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/1300235

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: = 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:
   
  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1300235/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file

[James Hunt]

Running with a 3.19.0-8-generic kernel I see:

- The Upstart test_job_process test fail within a few seconds when run in a 
loop looking for the errror.
- My test program in #13 also finds the bug within ~30 seconds on my test 
system.

Using the kernel in #11, I have run both tests simultaneously for ~1
hour with no errors observed.

** Changed in: upstart (Ubuntu Vivid)
   Status: New = Invalid

** Summary changed:

- FTBFS: upstart test_job_process fails in majority of cases / Kernel returning 
unexpected EIO at near of file
+ FTBFS: upstart test_job_process fails in majority of cases / Kernel returning 
unexpected EIO at end of file

-- 
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/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file

[James Hunt]

I've written a basic program that surfaces this bug. To recreate:

$ cd /tmp
$ tar xvf bug-1429756.tgz
$ cd bug-1429756
$ make
$ ./bug-1429756.sh
loop 1
loop 2
ERROR: got failure scenario after 2 loops (got=16, count=17, 
log=/tmp/tmp.uwZHkHh0mc)
$ 

** Attachment added: bug-1429756.tgz
   
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+attachment/4343995/+files/bug-1429756.tgz

-- 
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/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at near of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  New
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

The crash seems to originate from the conf_delete_handler() where
although an error message gets logged, the actual error itself is not
cleared. Note that this bug is present in 1.5-0ubuntu7.2 (precise), but
is not present in trusty (1.12.1-0ubuntu4.2) or vivid (1.13.2-0ubuntu9).

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

[James Hunt]

Playing around with strings(1), I've found this:

$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep \init\
init
The SUID sandbox created a new PID namespace but Zygote is not the init 
process. Please, make sure the SUID binary is up to date.
Error creating an init process to reap zombies
Failed to init random generator!
Failed to init data channel.
SRTP reset to init state
Failed to init SRTP, err=
Image size must match encoder init configuration size
.init

--

The key terms here are:

- Error creating an init process to reap zombies
- SUID binary

See:
https://code.google.com/p/chromium/codesearch#chromium/src/content/zygote/zygote_main_linux.ccsq=package:chromium

It appears chromium creates PID namespaces, probably to run plugins/tabs
in an isolated environment. But each pid namespace needs a PID 1
process. So, one possibility is that chromium is inadvertently forking
and exec'ing init (ie /sbin/init) rather than its own init
implementation of an init daemon (/opt/google/chrome-unstable/chrome
--type=zygote?). And that init (be it upstart or systemd) is crashing
as it's being run in a very unusual environment.

-- 
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/1300235

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in upstart package in Ubuntu:
  Triaged

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: = 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:
   
  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

** Also affects: upstart (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Precise:
  New

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host

[James Hunt]

** Description changed:

  = Summary =
  
  The version of Upstart in precise is affected by a bug in the way that
  .override [1] file handling is performed.
  
  If a job has an override file (/etc/init/*.override) and that override
  file is deleted before the corresponding job configuration file
  (/etc/init/*.conf), there is a possibility of a crash.
  
  == Explanation ==
  
  When a /etc/init/*.override file is deleted, Upstart will
  automatically detect this and reload the corresponding
  /etc/init/*.conf file.
  
  However, if the .conf file (which the .override file corresponded
  to) is deleted at the same time Upstart attempts to read the .conf
  file, an assertion failure could result.
  
- 
  = Code Specifics =
  
  The erroneous function is conf_delete_handler() which is called
  whenever a file Upstart is watching gets deleted. The end of this
  function calls conf_reload_path() but although it logs an error message,
  it does not consume the error object that gets raised when
  conf_reload_path() fails.
- 
  
  = Affected Releases =
  
  This bug is only present in precise:
  
  - Upstart override handling was introduced in Upstart v1.3:
  - Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
  - Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
  - Trusty and Vivid use much newer versions of the Upstart which no
-   longer contain the problematic code.
- 
+   longer contain the problematic code.
  
  = Fix =
  
  The fix is simply to have conf_delete_handler() consume the error object
  (by freeing it) when conf_reload_path() fails.
- 
  
  = Test Case =
  
  A reliable test case is unfortunately not possible to create, since the 
problem comes down to Upstart racing with the deletion of the .conf
  file.
  
  However, the patch is small and it can be seen that every other failing
  call to conf_reload_path() free's the resulting error object.
  
+ = Workarounds =
+ 
+ The problem is only manifested if .conf and the .override file get
+ deleted one after another, with the .override file being deleted
+ first. This implies the following work-arounds to avoid the problem if
+ you wish to delete both files at the same time:
+ 
+ 1) Ensure the .conf file is deleted first.
+ 
+ 2) Delete the .override file first, and then wait for a small period
+ of time before deleting the corresponding .conf file.
+ 
+ 3) Delete the .override file first, then call sudo initctl reload-
+ configuration and then delete the corresponding .conf file.
  
  = Regression Potential =
  
  None expected. The problem is difficult to trigger anwyay and the patch
  can be seen to correct (what is now) an obvious coding error.
- 
  
  [1] - http://upstart.ubuntu.com/cookbook/#override-file
  
  = Original Description =
  
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the host
  dies shortly after launchpad-buildd starts trying to remove the build
  chroot.  The kernel log looks like this:
  
  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped
  
  This appears to be because a couple of functions call conf_reload_path,
  which may leave an nih_error in place if nih_file_read fails, but then
  do not dispose of the nih_error.  The pattern near the end of
  conf_file_visitor (in precise) is probably appropriate.
  
  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a chroot
  to crash the host's init.

** Description changed:

  = Summary =
  
  The version of Upstart in precise is affected by a bug in the way that
  .override [1] file handling is performed.
  
  If a job has an override file (/etc/init/*.override) and that override
  file is deleted before the corresponding job configuration file
  (/etc/init/*.conf), there is a possibility of a crash.
  
  == Explanation ==
  
  When a /etc/init/*.override file is deleted, Upstart will
  automatically detect this and reload the corresponding
  /etc/init/*.conf file.
  
  However, if the .conf file (which the .override file corresponded
  to) is deleted at the same time Upstart attempts to read the .conf
  file, an assertion failure could result.
  
  = Code Specifics =
  
  The erroneous function is conf_delete_handler() which 

[Touch-packages] [Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host

[James Hunt]

** Summary changed:

- ubuntu-touch livefs builds kill upstart in host
+ [SRU] ubuntu-touch livefs builds kill upstart in host

** Changed in: upstart (Ubuntu)
   Status: Confirmed = In Progress

-- 
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/1430403

Title:
  [SRU] ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  In Progress
Status in upstart source package in Precise:
  New

Bug description:
  = Summary =

  The version of Upstart in precise is affected by a bug in the way that
  .override [1] file handling is performed.

  If a job has an override file (/etc/init/*.override) and that
  override file is deleted before the corresponding job configuration
  file (/etc/init/*.conf), there is a possibility of a crash.

  == Explanation ==

  When a /etc/init/*.override file is deleted, Upstart will
  automatically detect this and reload the corresponding
  /etc/init/*.conf file.

  However, if the .conf file (which the .override file corresponded
  to) is deleted at the same time Upstart attempts to read the .conf
  file, an assertion failure could result.

  
  = Code Specifics =

  The erroneous function is conf_delete_handler() which is called
  whenever a file Upstart is watching gets deleted. The end of this
  function calls conf_reload_path() but although it logs an error
  message, it does not consume the error object that gets raised when
  conf_reload_path() fails.

  
  = Affected Releases =

  This bug is only present in precise:

  - Upstart override handling was introduced in Upstart v1.3:
  - Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
  - Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
  - Trusty and Vivid use much newer versions of the Upstart which no
longer contain the problematic code.

  
  = Fix =

  The fix is simply to have conf_delete_handler() consume the error
  object (by freeing it) when conf_reload_path() fails.

  
  = Test Case =

  A reliable test case is unfortunately not possible to create, since the 
problem comes down to Upstart racing with the deletion of the .conf
  file.

  However, the patch is small and it can be seen that every other
  failing call to conf_reload_path() free's the resulting error object.

  
  = Regression Potential =

  None expected. The problem is difficult to trigger anwyay and the
  patch can be seen to correct (what is now) an obvious coding error.

  
  [1] - http://upstart.ubuntu.com/cookbook/#override-file

  = Original Description =

  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

** Description changed:

+ = Summary =
+ 
+ The version of Upstart in precise is affected by a bug in the way that
+ .override [1] file handling is performed.
+ 
+ If a job has an override file (/etc/init/*.override) and that override
+ file is deleted before the corresponding job configuration file
+ (/etc/init/*.conf), there is a possibility of a crash.
+ 
+ == Explanation ==
+ 
+ When a /etc/init/*.override file is deleted, Upstart will
+ automatically detect this and reload the corresponding
+ /etc/init/*.conf file.
+ 
+ However, if the .conf file (which the .override file corresponded
+ to) is deleted at the same time Upstart attempts to read the .conf
+ file, an assertion failure could result.
+ 
+ 
+ = Code Specifics =
+ 
+ The erroneous function is conf_delete_handler() which is called
+ whenever a file Upstart is watching gets deleted. The end of this
+ function calls conf_reload_path() but although it logs an error message,
+ it does not consume the error object that gets raised when
+ conf_reload_path() fails.
+ 
+ 
+ = Affected Releases =
+ 
+ This bug is only present in precise:
+ 
+ - Upstart override handling was introduced in Upstart v1.3:
+ - Precise currently uses Upstart 1.5-0ubuntu7.2 (and hence is affected).
+ - Lucid currently uses Upstart 0.6.5-8 (hence, not affected).
+ - Trusty and Vivid use much newer versions of the Upstart which no
+   longer contain the problematic code.
+ 
+ 
+ = Fix =
+ 
+ The fix is simply to have conf_delete_handler() consume the error object
+ (by freeing it) when conf_reload_path() fails.
+ 
+ 
+ = Test Case =
+ 
+ A reliable test case is unfortunately not possible to create, since the 
problem comes down to Upstart racing with the deletion of the .conf
+ file.
+ 
+ However, the patch is small and it can be seen that every other failing
+ call to conf_reload_path() free's the resulting error object.
+ 
+ 
+ = Regression Potential =
+ 
+ None expected. The problem is difficult to trigger anwyay and the patch
+ can be seen to correct (what is now) an obvious coding error.
+ 
+ 
+ [1] - http://upstart.ubuntu.com/cookbook/#override-file
+ 
+ = Original Description =
+ 
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the host
  dies shortly after launchpad-buildd starts trying to remove the build
  chroot.  The kernel log looks like this:
  
  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped
  
  This appears to be because a couple of functions call conf_reload_path,
  which may leave an nih_error in place if nih_file_read fails, but then
  do not dispose of the nih_error.  The pattern near the end of
  conf_file_visitor (in precise) is probably appropriate.
  
  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a chroot
  to crash the host's init.

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Precise:
  New

Bug description:
  = Summary =

  The version of Upstart in precise is affected by a bug in the way that
  .override [1] file handling is performed.

  If a job has an override file (/etc/init/*.override) and that
  override file is deleted before the corresponding job configuration
  file (/etc/init/*.conf), there is a possibility of a crash.

  == Explanation ==

  When a /etc/init/*.override file is deleted, Upstart will
  automatically detect this and reload the corresponding
  /etc/init/*.conf file.

  However, if the .conf file (which the .override file corresponded
  to) is deleted at the same time Upstart attempts to read the .conf
  file, an assertion failure could result.

  
  = Code Specifics =

  The erroneous function is conf_delete_handler() which is called
  whenever a file Upstart is watching gets deleted. The end of this
  function calls conf_reload_path() but although it logs an error
  message, it does not consume the error object that gets raised when
  conf_reload_path() fails.

  
  = Affected Releases =

  This bug is only present in precise:

  

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

It is relatively simple to trigger the bug: run a script that loops
creating a .conf file and an .override file, then deletes the .conf file
before deleting the override file.

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

Attached is a minimal fix for the bug.

Note that since this issue does not affect newer releases, we cannot
follow the usual process of testing in the dev release. However, as can
be seen, the fix is small and quite clear. Note that the change to
main.c is required to make upstart build on precise (looks like there
was a bzr / source package disconnect somewhere).


** Patch added: upstart-bug-1430403.diff
   
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+attachment/4340271/+files/upstart-bug-1430403.diff

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

lp keeps timing out on me when I attempt to attach a file. Meantime...

I've managed to force a crash after ~150 iterations of bug-1430403.sh
using http://people.canonical.com/~jhunt/upstart/bug-1430403.tgz.

To recreate:

$ sudo tar xvfz bug-1430403.tgz
$ sudo bash bug-1430403.sh

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

Note that we cannot add new unit tests for this fix without making it a
much bigger change since the problematic function is static.

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

** Changed in: upstart (Ubuntu Vivid)
 Assignee: (unassigned) = James Hunt (jamesodhunt)

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host

[James Hunt]

conf_reload_path() calls nih_file_read(). Although the return value of
that call is checked, the code is wrong. It looks likely that this bug
crept in since, unfortunately, the documentation for nih_file_read() is
incorrect. It states:

Returns: newly allocated string or NULL if insufficient memory.

... whereas it *should* state:

Returns: newly allocated string or NULL on raised error.

As such, if the call to nih_file_read() fails, the error object should
be destroyed before continuing to avoid the crash seen above.

** Changed in: upstart (Ubuntu)
   Importance: Undecided = High

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) = James Hunt (jamesodhunt)

-- 
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/1430403

Title:
  ubuntu-touch livefs builds kill upstart in host

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-touch livefs builds have started killing upstart in the host
  system (in this case, precise, although a similar bug appears to be
  present in current versions).  The livefs build completes, but the
  host dies shortly after launchpad-buildd starts trying to remove the
  build chroot.  The kernel log looks like this:

  Mar 10 13:46:55 allspice kernel: [3743880.621603] init: 
/home/buildd/build-LIVEFSBUILD-22254/chroot-autobuild/build/chroot/etc/init/tty1.conf:
 Unable to reload configuration after override deletion
  Mar 10 13:46:55 allspice kernel: [3743880.642455] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.754281] init: Caught abort, core 
dumped
  Mar 10 13:46:55 allspice kernel: [3743880.754375] init: file.c:110: Unhandled 
error from nih_file_read: No such file or directory
  Mar 10 13:46:55 allspice kernel: [3743880.757830] init: Caught abort, core 
dumped

  This appears to be because a couple of functions call
  conf_reload_path, which may leave an nih_error in place if
  nih_file_read fails, but then do not dispose of the nih_error.  The
  pattern near the end of conf_file_visitor (in precise) is probably
  appropriate.

  We're working around this to some extent in livecd-rootfs by removing
  the .override files first, but it should never be possible for a
  chroot to crash the host's init.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

It does indeed seem to be related to the kernel. I've just run that
specific test 77 times on an amd64 system running a 3.18.0-11 kernel
with no failures. Once the broken deps issue is resolved, I'll retest on
the same system running the latest 3.19 kernel.

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

Updating the amd64 system, I see the failure on the 2nd test run.

The Upstart logging code doesn't seem to be the culprit fwics meaning
the most likely area is the pty-handling code (either in upstart or in
the kernel).

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

Some quick tests suggest that this issue only seems to affect long runs
of nul bytes (even if they are terminated by visible chars + a '\n').

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

mk-sbuild now fails with a different error:

Setting up udev (219-4ubuntu3) ...
A chroot environment has been detected, udev not started.
/var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst: 
update-initramfs: not found
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

But back to the test failure... this  test has been running successfully
on all platforms for a long time (3+ years). It's possible that the test
itself is racy and that a recent change in a different package has
exposed that. Do we know when this test first started failing (and
ideally what changes triggered it (kernel/libc))?

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases

[James Hunt]

'mk-sbuild vivid' currently gives an error:

You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 systemd-sysv : Conflicts: upstart but 1.13.2-0ubuntu9 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a 
solution).

-- 
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/1429756

Title:
  FTBFS: test_job_process fails in majority of cases

Status in upstart package in Ubuntu:
  New
Status in upstart source package in Vivid:
  New

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
wrong value for bytes, expected 3145728 got 3018027
at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob

[James Hunt]

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) = James Hunt (jamesodhunt)

** Changed in: upstart (Ubuntu)
   Importance: Undecided = High

-- 
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/1425685

Title:
  Missing input sanitation in upstart logrotation cronjob

Status in upstart package in Ubuntu:
  New

Bug description:
  Ubuntu Vivid 1504 (development branch) installs an insecure upstart
  logrotation script which will read user-supplied data from
  /run/user/[uid]/upstart/sessions and pass then unsanitized to an env
  command. As user run directory is user-writable, the user may inject
  arbitrary commands into the logrotation script, which will be executed
  during daily cron job execution around midnight with root privileges.

  Problematic part of /etc/cron.daily/upstart:

  for session in /run/user/*/upstart/sessions/*
  do
  env $(cat $session) /sbin/initctl emit rotate-logs /dev/null 21 || true
  done

  On a system with e.g. libpam-systemd installed, standard login on TTY
  or via SSH will create the directory /run/user/[uid] writable to the
  user. By preparing a suitable session file, user supplied code will be
  run during the daily cron-jobs.

  See [1] for more information.

  # lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  # apt-cache policy upstart-bin
  upstart-bin:
Installed: 1.13.2-0ubuntu7
Candidate: 1.13.2-0ubuntu7
Version table:
   *** 1.13.2-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status

  
  [1] 
http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob

[James Hunt]

** Changed in: upstart (Ubuntu)
   Status: New = Fix Committed

-- 
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/1425685

Title:
  Missing input sanitation in upstart logrotation cronjob

Status in upstart package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu Vivid 1504 (development branch) installs an insecure upstart
  logrotation script which will read user-supplied data from
  /run/user/[uid]/upstart/sessions and pass then unsanitized to an env
  command. As user run directory is user-writable, the user may inject
  arbitrary commands into the logrotation script, which will be executed
  during daily cron job execution around midnight with root privileges.

  Problematic part of /etc/cron.daily/upstart:

  for session in /run/user/*/upstart/sessions/*
  do
  env $(cat $session) /sbin/initctl emit rotate-logs /dev/null 21 || true
  done

  On a system with e.g. libpam-systemd installed, standard login on TTY
  or via SSH will create the directory /run/user/[uid] writable to the
  user. By preparing a suitable session file, user supplied code will be
  run during the daily cron-jobs.

  See [1] for more information.

  # lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  # apt-cache policy upstart-bin
  upstart-bin:
Installed: 1.13.2-0ubuntu7
Candidate: 1.13.2-0ubuntu7
Version table:
   *** 1.13.2-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status

  
  [1] 
http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob

[James Hunt]

Fixed in upstart 1.13.2-0ubuntu9, currently in the proposed pocket.

-- 
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/1425685

Title:
  Missing input sanitation in upstart logrotation cronjob

Status in upstart package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu Vivid 1504 (development branch) installs an insecure upstart
  logrotation script which will read user-supplied data from
  /run/user/[uid]/upstart/sessions and pass then unsanitized to an env
  command. As user run directory is user-writable, the user may inject
  arbitrary commands into the logrotation script, which will be executed
  during daily cron job execution around midnight with root privileges.

  Problematic part of /etc/cron.daily/upstart:

  for session in /run/user/*/upstart/sessions/*
  do
  env $(cat $session) /sbin/initctl emit rotate-logs /dev/null 21 || true
  done

  On a system with e.g. libpam-systemd installed, standard login on TTY
  or via SSH will create the directory /run/user/[uid] writable to the
  user. By preparing a suitable session file, user supplied code will be
  run during the daily cron-jobs.

  See [1] for more information.

  # lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  # apt-cache policy upstart-bin
  upstart-bin:
Installed: 1.13.2-0ubuntu7
Candidate: 1.13.2-0ubuntu7
Version table:
   *** 1.13.2-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status

  
  [1] 
http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob

[James Hunt]

Note - this problem only affects vivid fwics. Further, it does not
affect Touch (since that uses Upstart as PID 1).

-- 
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/1425685

Title:
  Missing input sanitation in upstart logrotation cronjob

Status in upstart package in Ubuntu:
  New

Bug description:
  Ubuntu Vivid 1504 (development branch) installs an insecure upstart
  logrotation script which will read user-supplied data from
  /run/user/[uid]/upstart/sessions and pass then unsanitized to an env
  command. As user run directory is user-writable, the user may inject
  arbitrary commands into the logrotation script, which will be executed
  during daily cron job execution around midnight with root privileges.

  Problematic part of /etc/cron.daily/upstart:

  for session in /run/user/*/upstart/sessions/*
  do
  env $(cat $session) /sbin/initctl emit rotate-logs /dev/null 21 || true
  done

  On a system with e.g. libpam-systemd installed, standard login on TTY
  or via SSH will create the directory /run/user/[uid] writable to the
  user. By preparing a suitable session file, user supplied code will be
  run during the daily cron-jobs.

  See [1] for more information.

  # lsb_release -rd
  Description:Ubuntu Vivid Vervet (development branch)
  Release:15.04

  # apt-cache policy upstart-bin
  upstart-bin:
Installed: 1.13.2-0ubuntu7
Candidate: 1.13.2-0ubuntu7
Version table:
   *** 1.13.2-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status

  
  [1] 
http://www.halfdog.net/Security/2015/UpstartLogrotationPrivilegeEscalation/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1424992] Re: files in /tmp not being cleared on boot

[James Hunt]

Thanks Martin!

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

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  My system has been booted for 2 1/2 hours and yet /tmp contains old
  files from 2015-02-19.

  $ sudo systemctl|grep tmpfiles
  systemd-tmpfiles-setup-dev.service
 loaded active exited
Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service
 loaded active exited
Create Volatile Files and Directories
  systemd-tmpfiles-clean.timer  
 loaded active waiting   
Daily Cleanup of Temporary Directories

  $ sudo journalctl -a|grep tmpfiles
  Feb 24 07:27:08 faire systemd-tmpfiles[701]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path /var/log, ignoring.
  Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path /var/log, ignoring.

  $ sudo du -sh /tmp
  481M/tmp
  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
  Reading config file /usr/lib/tmpfiles.d/tmp.conf.
  Running clean action for entry v /tmp
  Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  $ sudo du -sh /tmp
  481M/tmp
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-3ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 09:55:29 2015
  InstallationDate: Installed on 2014-04-11 (318 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1424992] [NEW] files in /tmp not being cleared on boot

[James Hunt]

Public bug reported:

My system has been booted for 2 1/2 hours and yet /tmp contains old
files from 2015-02-19.

$ sudo systemctl|grep tmpfiles
systemd-tmpfiles-setup-dev.service  
   loaded active exited
Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service  
   loaded active exited
Create Volatile Files and Directories
systemd-tmpfiles-clean.timer
   loaded active waiting   
Daily Cleanup of Temporary Directories

$ sudo journalctl -a|grep tmpfiles
Feb 24 07:27:08 faire systemd-tmpfiles[701]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path /var/log, ignoring.
Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path /var/log, ignoring.

$ sudo du -sh /tmp
481M/tmp
$ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
Reading config file /usr/lib/tmpfiles.d/tmp.conf.
Running clean action for entry v /tmp
Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
$ sudo du -sh /tmp
481M/tmp
$

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-3ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Feb 24 09:55:29 2015
InstallationDate: Installed on 2014-04-11 (318 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro init=/lib/systemd/systemd quiet splash 
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2014-05-08 (291 days ago)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug vivid

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

Title:
  files in /tmp not being cleared on boot

Status in systemd package in Ubuntu:
  New

Bug description:
  My system has been booted for 2 1/2 hours and yet /tmp contains old
  files from 2015-02-19.

  $ sudo systemctl|grep tmpfiles
  systemd-tmpfiles-setup-dev.service
 loaded active exited
Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service
 loaded active exited
Create Volatile Files and Directories
  systemd-tmpfiles-clean.timer  
 loaded active waiting   
Daily Cleanup of Temporary Directories

  $ sudo journalctl -a|grep tmpfiles
  Feb 24 07:27:08 faire systemd-tmpfiles[701]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path /var/log, ignoring.
  Feb 24 07:41:38 faire systemd-tmpfiles[31258]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path /var/log, ignoring.

  $ sudo du -sh /tmp
  481M/tmp
  $ sudo SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --clean 
/usr/lib/tmpfiles.d/tmp.conf
  Reading config file /usr/lib/tmpfiles.d/tmp.conf.
  Running clean action for entry v /tmp
  Running clean action for entry X 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  Running clean action for entry x 
/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry x 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*
  Running clean action for entry X 
/var/tmp/systemd-private-6c3da060cdc64ed0ae365cc462ff3d63-*/tmp
  $ sudo du -sh /tmp
  481M/tmp
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  

[Touch-packages] [Bug 1413922] Re: lxc unprivileged containers broken

[James Hunt]

Hi Serge,

Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james:
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope'
allowed me to start the non-priv container.

** Changed in: lxc (Ubuntu)
   Status: Incomplete = New

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

Title:
  lxc unprivileged containers broken

Status in lxc package in Ubuntu:
  New

Bug description:
  Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

  $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
  lxc-start: lxc_start.c: main: 345 The container failed to start.
  lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lxc.log attached.

  On a related note, it seems that the dep8 tests I originally wrote for
  lxc [1] have been replaced to call lxc's own test suite. However,
  whereas these new tests are somehow passing in jenkins [2], I belied
  the crude tests in [1] would have caught this issue as they actually
  call the command-line tools users run.

  Could we maybe bring back [1] and run both sets of tests to avoid such
  a regression in future?

  [1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
  [2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 23 09:15:29 2015
  InstallationDate: Installed on 2014-04-11 (286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1413922] [NEW] lxc unprivileged containers broken

[James Hunt]

Public bug reported:

Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

$ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
lxc-start: lxc_start.c: main: 345 The container failed to start.
lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

lxc.log attached.

On a related note, it seems that the dep8 tests I originally wrote for
lxc [1] have been replaced to call lxc's own test suite. However,
whereas these new tests are somehow passing in jenkins [2], I belied the
crude tests in [1] would have caught this issue as they actually call
the command-line tools users run.

Could we maybe bring back [1] and run both sets of tests to avoid such a
regression in future?

[1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
[2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.0~rc1-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 23 09:15:29 2015
InstallationDate: Installed on 2014-04-11 (286 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: lxc
UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug vivid

** Attachment added: lxc.log
   https://bugs.launchpad.net/bugs/1413922/+attachment/4304130/+files/lxc.log

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

Title:
  lxc unprivileged containers broken

Status in lxc package in Ubuntu:
  New

Bug description:
  Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

  $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
  lxc-start: lxc_start.c: main: 345 The container failed to start.
  lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lxc.log attached.

  On a related note, it seems that the dep8 tests I originally wrote for
  lxc [1] have been replaced to call lxc's own test suite. However,
  whereas these new tests are somehow passing in jenkins [2], I belied
  the crude tests in [1] would have caught this issue as they actually
  call the command-line tools users run.

  Could we maybe bring back [1] and run both sets of tests to avoid such
  a regression in future?

  [1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
  [2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 23 09:15:29 2015
  InstallationDate: Installed on 2014-04-11 (286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1413922] Re: lxc unprivileged containers broken

[James Hunt]

Ah - seems we'd actually need to add in a couple of loops in those
original dep-8 tests: run the tests as root, then run as a non-priv user
too! :)

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

Title:
  lxc unprivileged containers broken

Status in lxc package in Ubuntu:
  New

Bug description:
  Seems to be due to 1.1.0~rc1-0ubuntu1 landing?

  $ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
  lxc-start: lxc_start.c: main: 345 The container failed to start.
  lxc-start: lxc_start.c: main: 347 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 349 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  lxc.log attached.

  On a related note, it seems that the dep8 tests I originally wrote for
  lxc [1] have been replaced to call lxc's own test suite. However,
  whereas these new tests are somehow passing in jenkins [2], I belied
  the crude tests in [1] would have caught this issue as they actually
  call the command-line tools users run.

  Could we maybe bring back [1] and run both sets of tests to avoid such
  a regression in future?

  [1] - 
https://code.launchpad.net/~jamesodhunt/ubuntu/raring/lxc/dep-8-tests/+merge/157938
  [2] - 
https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-lxc/ARCH=amd64,label=adt/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 23 09:15:29 2015
  InstallationDate: Installed on 2014-04-11 (286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2014-05-08 (259 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300235] Re: init crashed with SIGSEGV

[James Hunt]

Hi Brian - does running synaptic-pkexec in a terminal trigger the crash?
If not, we really need a trace showing what happens in cbOpenHomepage,
specifically what the 'cmd' vector contains.

-- 
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/1300235

Title:
  init crashed with SIGSEGV

Status in upstart package in Ubuntu:
  Triaged

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: = 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:
   
  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1399687] [NEW] Provide version_detail for latest revision on server

[James Hunt]

Public bug reported:

Currently, the Information() D-Bus method provides the following
something like:

current_build_number=129
device_name=generic_amd64
target_build_number=131
version_detail=ubuntu=20141205.1,raw-device=20141205.1,version=129
channel_name=ubuntu-core/devel
last_update_date=2014-12-05 05:26:42
last_check_date=2014-12-05 15:41:43

Ideally, it would also provide version_detail for the latest revision
on the server, that is version_detail for target_build_number.

Even more ideally, it would break version_detail into chunks. Something
like:

current_ubuntu_version=ubuntu=20141205.1
current_raw_device_version=20141205.1

... and for the latest revision found on the server, something like:

target_ubuntu_version=ubuntu=20141205.9
target_raw_device_version=20141205.2

For bonus points, this information would also be available via 'system-
image-cli -i', maybe requiring an addition option like '--full' to avoid
breaking existing consumers of 'system-image-cli -i' output.

Note that the command-line accessibility is potentially more important
than the D-Bus interface due to the fact that system-image-cli -i
provides the '-C' option to point it at an alternative installation.

** Affects: system-image (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Provide version_detail for latest revision on server

Status in system-image package in Ubuntu:
  New

Bug description:
  Currently, the Information() D-Bus method provides the following
  something like:

  current_build_number=129
  device_name=generic_amd64
  target_build_number=131
  version_detail=ubuntu=20141205.1,raw-device=20141205.1,version=129
  channel_name=ubuntu-core/devel
  last_update_date=2014-12-05 05:26:42
  last_check_date=2014-12-05 15:41:43

  Ideally, it would also provide version_detail for the latest
  revision on the server, that is version_detail for
  target_build_number.

  Even more ideally, it would break version_detail into chunks.
  Something like:

  current_ubuntu_version=ubuntu=20141205.1
  current_raw_device_version=20141205.1

  ... and for the latest revision found on the server, something like:

  target_ubuntu_version=ubuntu=20141205.9
  target_raw_device_version=20141205.2

  For bonus points, this information would also be available via
  'system-image-cli -i', maybe requiring an addition option like '--
  full' to avoid breaking existing consumers of 'system-image-cli -i'
  output.

  Note that the command-line accessibility is potentially more important
  than the D-Bus interface due to the fact that system-image-cli -i
  provides the '-C' option to point it at an alternative installation.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1399710] [NEW] no audible warning of high volume level

[James Hunt]

Public bug reported:

Additional to the work done on bug 1373404, I think we need to consider
adding an audio warning when the volume crosses the threshold value.

The way android works is that the user is asked if they want to allow
higher volume levels (they must click ok). Our approach is to just
display a visual warning. That's fine (assuming it complies with all
legal regs), but it isn't helpful from an accessibility perspective.

Obviously folk can hear when levels become painful high, but how about
we insert an audible warning when the user crosses the threshold?

I'd suggest we do both of the following to indicate an audible warning:

1) Mute (or atleast lower) the currently playing audio streams.
2) Play two beeps in quick succession (at the original volume level prior to 
mute/lowering).

Once the beeps have been played, the volume level will be restored to
the appropriate (higher) level.

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  no audible warning of high volume level

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Additional to the work done on bug 1373404, I think we need to
  consider adding an audio warning when the volume crosses the threshold
  value.

  The way android works is that the user is asked if they want to allow
  higher volume levels (they must click ok). Our approach is to just
  display a visual warning. That's fine (assuming it complies with all
  legal regs), but it isn't helpful from an accessibility perspective.

  Obviously folk can hear when levels become painful high, but how about
  we insert an audible warning when the user crosses the threshold?

  I'd suggest we do both of the following to indicate an audible
  warning:

  1) Mute (or atleast lower) the currently playing audio streams.
  2) Play two beeps in quick succession (at the original volume level prior to 
mute/lowering).

  Once the beeps have been played, the volume level will be restored to
  the appropriate (higher) level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399710/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1281061] Re: initctl eating cpu on mako #181

[James Hunt]

Hi Fabian,

The problem you are having seem to be related to mtp-server respawning
continuously. This may not be the same issue as originally reported, so
please open a new bug against the mtp-server package.

-- 
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/1281061

Title:
  initctl eating cpu on mako #181

Status in “upstart” package in Ubuntu:
  Expired

Bug description:
  On Ubuntu image #181 on mako my phone is hot. I checked top and found
  initctl eating 96% of the cpu..

  This may be related to bug 1281057 as my phone refuses to lock.

  Unfortunately I couldn't get the bug report done on the phone because
  the battery died (unsurprisingly) mid way through reporting it.
  Managed to get this output from top though.

  top - 10:34:05 up 1 day, 20:23,  1 user,  load average: 4.19, 4.14, 3.82
  Tasks: 244 total,   2 running, 242 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 49.1 us,  5.4 sy,  0.0 ni, 45.1 id,  0.4 wa,  0.0 hi,  0.0 si,  0.0 
st
  KiB Mem:   1916236 total,  1855748 used,60488 free,18420 buffers
  KiB Swap:   524284 total,   115420 used,   408864 free.   196160 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1981 phablet   20   0  679256 665780   1160 S   0.3 34.7  33:23.31 init  
  
586 message+  20   0  280608 276924712 S   0.0 14.5  26:18.81 
dbus-daemon 
  1 root  20   0  210636 206636   1056 S   0.0 10.8  12:16.86 init  
  
   2211 phablet   20   0  553308 127668  77840 S  85.7  6.7  49:53.31 unity8
  
598 root  20   0   88792  86892584 R  96.1  4.5 433:39.94 initctl   
  
   2318 phablet   20   0  296952  40432  33060 S   0.0  2.1   0:26.02 
maliit-ser+ 
   1903 root  20   0  241404  27880  20500 S  13.0  1.5  10:27.68 
unity-syst+ 
   9631 phablet   20   0  216224  19924  14828 S   0.0  1.0   0:01.78 
telephony-+ 
   2350 phablet   20   0   55260  19540   2776 S   0.0  1.0   1:28.08 
indicator-+ 
   1052 root  20   0   52248  19244   2252 S   0.0  1.0  22:39.85 upowerd   
  
   2080 phablet   20   0   47300  12604   3396 S   0.0  0.7   1:43.27 
mission-co+ 
   9368 phablet   20   0   80832  11872   9988 S   0.0  0.6   0:00.61 
telephony-+ 
   1062 root  20   0   42916  11548   2544 S   0.0  0.6  84:53.39 polkitd   
  
   2205 phablet   20   0   96980  11464   9280 S   0.0  0.6   0:05.66 
hud-service 
   9360 phablet   20   0   52164   9592   8120 S   0.0  0.5   0:00.21 
telephony-+ 
   2234 phablet   20   0  134336   8716   5288 S   0.0  0.5   0:16.43 
address-bo+ 
   2093 phablet9 -11  203588   7304   4964 S   0.0  0.4   5:37.30 pulseaudio

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

[James Hunt]

Something like the attached can be put into /usr/share/upstart/sessions/
and it will detect when system-level and session-level jobs hit their
respawn limit.

We could then use whitelists to identify the desired behaviour (restart
job, reboot, etc) for particular services.


** Attachment added: respawn-watchdog.conf
   
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1381075/+attachment/4243843/+files/respawn-watchdog.conf

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

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around

[James Hunt]

The oldest of the two unity8 proceses (pid 2640) has been SIGSTOP'ed.
Since unity8 uses SIGSTOP to indicate to upstart that it is ready, this
suggests that when lightdm died, the session init was killed somehow
before unity8 was ready (either on first start or respawn).

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

Title:
  lightm/upstart crash leaves 2 unity8 processes around

Status in “lightdm” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  lightm/upstart crash leaves 2 unity8 processes around

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around

[James Hunt]

Daniel - please can you attach the existing /var/crash/_sbin_init* to
this bug. I appreciate they do not represent the current issue, but if
may have been a re-occurence of the problem which did generated the
crash files so I'd like to see those anyway.

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

Title:
  lightm/upstart crash leaves 2 unity8 processes around

Status in “lightdm” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  lightm/upstart crash leaves 2 unity8 processes around

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1385464] Re: logrotate fails to run, if status file is corrupt (logrotate running during reboot?)

[James Hunt]

To be clear, this issue was observed on Touch.

Interestingly, we already have a fix for this, but it hasn't landed in
the archive or on Tocuh; the upstart session init has a logrotate job
(/usr/share/upstart/sessions/logrotate.conf) which is used to rotate the
users session init log files. I'd noticed the corruption issue and put a
fix in the tip of lp:ubuntu/upstart. Essentially, the solution is to
remove the status file as it will be regenerated on next logrotate run.
However, if the status file is corrupt, logrotate will never rewrite it
and as such, no logrotation occurs leading to unlimited logfile growth.

Here's the fix from the upstart job:

__

# Sometimes the state file can become corrupt (probably caused by
# logrotate updating it on shutdown). In these cases the file ends in
# nul bytes which causes a subsequent logrotate run (even a forced run)
# to refuse to process it meaning no files get rotated.
#
# Hence, if nul bytes are detected, reset the state file to allow logrotate
# to work.
[ -e $statefile ]  egrep '[^[:print:]]' $statefile  rm $statefile

__

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

Title:
  logrotate fails to run, if status file is corrupt (logrotate running
  during reboot?)

Status in “logrotate” package in Ubuntu:
  New

Bug description:
  phablet@ubuntu-phablet:~$ du -h /var/log/syslog 
  654M  /var/log/syslog
  phablet@ubuntu-phablet:~$ sudo logrotate -f /etc/logrotate.conf 
  error: bad top line in state file /var/lib/logrotate/status
  phablet@ubuntu-phablet:~$ cat /var/lib/logrotate/status 
  
/opt/click.ubuntu.com/com.ubuntu.developer.webapps.webapp-gmail/1.0.25phablet@ubuntu-phablet:~$

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

[James Hunt]

I've added more info to the cookbook wrt respawn. Here's the simplest
method of detecting hitting the respawn limit:

http://upstart.ubuntu.com/cookbook/#detecting-a-job-hitting-its-respawn-
limit

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

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

[James Hunt]

brian has pointed out that changing /usr/share/apport/kernel_oops isn't
necessary; apport now has a generic pipe program in the form of
/data/bzr/apport/apport/data/recoverable_problem.

We will need to make minor changes to the recoverable_problem utility
since it currently requires a pid but in this scenario we don't have one
- the process that upstart has been respawning is no longer running (and
we don't want apport using the pid of upstart).

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

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1383085] Re: background in app carousel view does not show background image

[James Hunt]

Seems that the camera issue is not only just when the lens is covered.
The live preview feature has gone away, so if the camera is running, the
carousel will show an invisible black camera app every time.

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

Title:
  background in app carousel view does not show background image

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  A swipe from the right edge of the phone towards the center fans out
  all the apps, showing a carousel-like view.

  However, the background is always black, whereas I would have expected
  the background to be the selected background image.

  Black is problematic since if one of the open apps is the camera, and
  the camera is face-down on a table for example, it will be showing a
  black image meaning that the camera app is presented as a pure black
  preview on a black background.

  krillin, r117.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383085/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1383085] [NEW] background in app carousel view does not show background image

[James Hunt]

Public bug reported:

A swipe from the right edge of the phone towards the center fans out all
the apps, showing a carousel-like view.

However, the background is always black, whereas I would have expected
the background to be the selected background image.

Black is problematic since if one of the open apps is the camera, and
the camera is face-down on a table for example, it will be showing a
black image meaning that the camera app is presented as a pure black
preview on a black background.

krillin, r117.

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


** Tags: avengers

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

Title:
  background in app carousel view does not show background image

Status in “unity8” package in Ubuntu:
  New

Bug description:
  A swipe from the right edge of the phone towards the center fans out
  all the apps, showing a carousel-like view.

  However, the background is always black, whereas I would have expected
  the background to be the selected background image.

  Black is problematic since if one of the open apps is the camera, and
  the camera is face-down on a table for example, it will be showing a
  black image meaning that the camera app is presented as a pure black
  preview on a black background.

  krillin, r117.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

[James Hunt]

The most appropriate way to do this would probably be to use apport to
check for respawn limit messages in:

- the system log, and
- the users $HOME/.xsession-errors file.

Even at the default upstart log priority of 'message', when a job
reaches the respawn limit, upstart will log a message to one of the logs
above like this:

init: foo respawning too fast, stopped

So apport, or some such utility could watch for these messages using
inotify and raise an informational error that would be visible on
errors.u.c.



** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1381075

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

[James Hunt]

Note that the kerneloops packages communicates with apport using the
/usr/share/apport/kernel_oops pipe program so a script could be
written to make use of similar pipe specifically for respawn failures.
Ideally, that kernel_oops utility would be made generic, accepting args
to specify the name of the package to report the problem against, etc,
and the kerneloops package updated to handle the new interface.

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

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1379021] Re: after utopic upgrade: boot delays for 2 minutes

[James Hunt]

@Dylan - which packages did you purge?

-- 
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/1379021

Title:
  after utopic upgrade: boot delays for 2 minutes

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to utopic, my system waits 2 minutes for network at boot, the 
boots ok. This has happened in previous releases as well for other people and 
is an annoying issue which will alarm many people especially the non-techinical 
users. Also, many fixes described in older bug reports no longer apply as 
ubuntu does not need them yet the bug is still alive and kicking.
  --- 
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2011-11-11 (1062 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.17.0-rc7-custom 
root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  Tags:  utopic
  Uname: Linux 3.17.0-rc7-custom i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups: adm admin audio cdrom dialout fuse lp lpadmin netdev plugdev 
powerdev sambashare sbuild scanner vboxusers video
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: 
u'/etc/at.deny']
  modified.conffile..etc.bluetooth.audio.conf: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.default.jenkins: [modified]
  modified.conffile..etc.init.jenkins.conf: [modified]
  modified.conffile..etc.init.runsvdir.conf: [modified]
  modified.conffile..etc.vsftpd.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-08-07T17:00:01.738247
  mtime.conffile..etc.bluetooth.audio.conf: 2014-07-08T18:53:12.563803
  mtime.conffile..etc.default.cups: 2014-04-10T18:37:14.830556
  mtime.conffile..etc.default.jenkins: 2012-11-03T21:42:41.983374
  mtime.conffile..etc.init.jenkins.conf: 2013-09-13T16:17:44.852882
  mtime.conffile..etc.init.runsvdir.conf: 2011-03-17T16:02:21
  mtime.conffile..etc.vsftpd.conf: 2012-07-07T13:06:07.102856

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1372937] Re: no ssh host keys generated when booting with systemd

[James Hunt]

** Changed in: system-image (Ubuntu)
 Assignee: James Hunt (jamesodhunt) = Michael Vogt (mvo)

** Changed in: system-image (Ubuntu)
   Status: Triaged = Fix Committed

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

Title:
  no ssh host keys generated when booting with systemd

Status in “system-image” package in Ubuntu:
  Fix Committed

Bug description:
  When booting the system image, nothing generates ssh host keys.

  Normally I think these are created on installation, but for good reason 
they're not included in the image.
  In cloud imags, cloud-init does this.  In other systemd boot scenarios, 
they're generated by another ssh service that is then a dependency of ssh 
starting.

  The end result is that the user cannot ssh in until they run
ssh-keygen -t rsa -N '' -f /etc/ssh/ssh_host_rsa_key

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1379021] Re: after utopic upgrade: boot delays for 2 minutes

[James Hunt]

Hi Dylan,

Thanks for taking the time to report this issue. Please can you do the
following:

1) Run 'apport-collect 1379021' to attach required logs to this bug
report.

2) Attach /etc/network/interfaces (and any files you've created in
/etc/network/interfaces.d/).

3) Attach /etc/fstab

4) Add '--debug' to the boot command line in the grub menu, boot your
system and then attach file /var/log/upstart/mountall.log.

-- 
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/1379021

Title:
  after utopic upgrade: boot delays for 2 minutes

Status in “upstart” package in Ubuntu:
  New

Bug description:
  After upgrading to utopic, my system waits 2 minutes for network at
  boot, the boots ok. This has happened in previous releases as well for
  other people and is an annoying issue which will alarm many people
  especially the non-techinical users. Also, many fixes described in
  older bug reports no longer apply as ubuntu does not need them yet the
  bug is still alive and kicking.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1379245] [NEW] cannot search within a page

[James Hunt]

Public bug reported:

The menu doesn't offer a find/search option to look for text on a web
page.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  cannot search within a page

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  The menu doesn't offer a find/search option to look for text on a web
  page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1379245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1379021] Re: after utopic upgrade: boot delays for 2 minutes

[James Hunt]

 Where do I add --debug? The Linux command line?
Yes:

1) Hold down control key at power-on to enter grub menu.
2) Press 'e' to edit the top (default) kernel command-line.
3) Use the cursor keys to move down the the line that begins with
   linux.
4) Press the END key (or use cursors again).
5) Add --debug (make sure there is a space between --debug and the
   option before it).
6) Press CTRL-x or F10 to 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/1379021

Title:
  after utopic upgrade: boot delays for 2 minutes

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to utopic, my system waits 2 minutes for network at boot, the 
boots ok. This has happened in previous releases as well for other people and 
is an annoying issue which will alarm many people especially the non-techinical 
users. Also, many fixes described in older bug reports no longer apply as 
ubuntu does not need them yet the bug is still alive and kicking.
  --- 
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2011-11-11 (1062 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  Package: upstart 1.13.2-0ubuntu2
  PackageArchitecture: i386
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.17.0-rc7-custom 
root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  Tags:  utopic
  Uname: Linux 3.17.0-rc7-custom i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups: adm admin audio cdrom dialout fuse lp lpadmin netdev plugdev 
powerdev sambashare sbuild scanner vboxusers video
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: 
u'/etc/at.deny']
  modified.conffile..etc.bluetooth.audio.conf: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.default.jenkins: [modified]
  modified.conffile..etc.init.jenkins.conf: [modified]
  modified.conffile..etc.init.runsvdir.conf: [modified]
  modified.conffile..etc.vsftpd.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-08-07T17:00:01.738247
  mtime.conffile..etc.bluetooth.audio.conf: 2014-07-08T18:53:12.563803
  mtime.conffile..etc.default.cups: 2014-04-10T18:37:14.830556
  mtime.conffile..etc.default.jenkins: 2012-11-03T21:42:41.983374
  mtime.conffile..etc.init.jenkins.conf: 2013-09-13T16:17:44.852882
  mtime.conffile..etc.init.runsvdir.conf: 2011-03-17T16:02:21
  mtime.conffile..etc.vsftpd.conf: 2012-07-07T13:06:07.102856

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1312260] Re: [browser] There is no search in page option in webbrowser-app (like ctrl+F)

[James Hunt]

Giorgio - the spec doesn't appear to specify the colour that should be
used for the highlights. If the highlight colour is fixed as say yellow,
it would have no effect if the background colour of the page was the
same colour. What if the background colour is white but the text is
yellow?

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

Title:
  [browser] There is no search in page option in webbrowser-app (like
  ctrl+F)

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  Triaged
Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  Users will be able to find text in page (partialexact match)
  - Function will be available in the Action Drawer

  UX Spec here
  
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g187f4edfe_50

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1312260/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1377956] [NEW] modify semantics of bootme attribute to support delayed reboot

[James Hunt]

Public bug reported:

system-image currently supports a 'bootme' option that may be present in
the JSON and instructs Touch to reboot _after it has finished
downloading the current file_.

However, Core has a slightly different requirement. It attempts to
minimise reboots, but when certain packages (like the kernel) have been
updated, a reboot will be required. Crucially though, this reboot should
not occur until the the system image has been fully downloaded *and*
fully unpacked.

After a discussion with barry+mvo, we think the best approach is to
modify the bootme flag to be able to specify a 'deferred' value meaning
reboot at end of download+unpack.

** Affects: ubuntu-system-image
 Importance: High
 Status: Triaged


** Tags: client

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

Title:
  modify semantics of bootme attribute to support delayed reboot

Status in Ubuntu system image (server/client/updater):
  Triaged

Bug description:
  system-image currently supports a 'bootme' option that may be present
  in the JSON and instructs Touch to reboot _after it has finished
  downloading the current file_.

  However, Core has a slightly different requirement. It attempts to
  minimise reboots, but when certain packages (like the kernel) have
  been updated, a reboot will be required. Crucially though, this reboot
  should not occur until the the system image has been fully downloaded
  *and* fully unpacked.

  After a discussion with barry+mvo, we think the best approach is to
  modify the bootme flag to be able to specify a 'deferred' value
  meaning reboot at end of download+unpack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1377956/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1377146] [NEW] shutdown menu should show icons

[James Hunt]

Public bug reported:

Holding the physical power button displays the shutdown menu with
options to shutdown, restart or cancel. These buttons are colour-coded
but for added clarity I think we should add icons to represent the
operations.

Note that if this menu is changed, there are other parts of the system
that also offer similar shutdown/restart menus (see bug 1377145) so
ideally they would also be modified (or even better they would make use
of the one true shutdown menu to avoid inconsistency).

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


** Tags: avengers

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

Title:
  shutdown menu should show icons

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Holding the physical power button displays the shutdown menu with
  options to shutdown, restart or cancel. These buttons are colour-coded
  but for added clarity I think we should add icons to represent the
  operations.

  Note that if this menu is changed, there are other parts of the system
  that also offer similar shutdown/restart menus (see bug 1377145) so
  ideally they would also be modified (or even better they would make
  use of the one true shutdown menu to avoid inconsistency).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1377146] Re: shutdown menu should show icons

[James Hunt]

Rationale for adding icons:

1) The standard shutdown (power) icon, and the restart (circular arrow)
are almost universally recognised (to the extent that you wonder if we
could actually remove the text).

2) Colours only work if you can discriminate between then. Red and green
are alas an unfortunate combination
(http://en.wikipedia.org/wiki/Color_blindness#Red.E2.80.93green_color_blindness)

3) if you inadvertently change your language to a language you don't
actually understand, you have a hope of selecting the correct option if
you can recognise the icon :-)

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

Title:
  shutdown menu should show icons

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Holding the physical power button displays the shutdown menu with
  options to shutdown, restart or cancel. These buttons are colour-coded
  but for added clarity I think we should add icons to represent the
  operations.

  Note that if this menu is changed, there are other parts of the system
  that also offer similar shutdown/restart menus (see bug 1377145) so
  ideally they would also be modified (or even better they would make
  use of the one true shutdown menu to avoid inconsistency).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1351423] Re: dash icon significantly different to that on other platforms

[James Hunt]

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  dash icon significantly different to that on other platforms

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Opinion

Bug description:
  The dash icon is shown as an orange square (with very hard straight
  edges btw) with the Ubuntu logo within.

  This seems odd since it is so markedly different to the dash icon on
  desktop systems (the swirl).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1351423/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1351423] Re: dash icon significantly different to that on other platforms

[James Hunt]

I still don't understand why the current icon:

a) is hard-edged - every other icon (in fact every other widget?) has
rounded corners.

Is this simply to discriminate it from everything else? If so, is there any 
other way we can do this that is more in keeping with
the softer-edged appearance of the rest of the interface?

b) has a very flat profile; the other icons on the phone have seem to
have very subtle (and attractive) highlights on the top edge.

c) is basically so different to the stylish swirl logo we have on
desktop.

Should the desktop inherit the phone icon? Or should the phone
inherit the desktop version? (why are they different?)

Since this is arguably the most important icon on the launcher, it would
be great if it had a little more presence (above and beyond that of the
other icons).

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

Title:
  dash icon significantly different to that on other platforms

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Opinion

Bug description:
  The dash icon is shown as an orange square (with very hard straight
  edges btw) with the Ubuntu logo within.

  This seems odd since it is so markedly different to the dash icon on
  desktop systems (the swirl).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1351423/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1377184] [NEW] move archive_master file out of /etc to avoid it being treated as a conffile

[James Hunt]

Public bug reported:

Currently client.ini specifies:

[gpg]
archive_master: /etc/system-image/archive-master.tar.xz

The problem is that file in /etc are automatically marked as conffiles
by debhelper and as such don't get moved into place until the dpkg
configure step.

This caused an issue for the initramfs-tools-ubuntu-core package since that 
Depends on system-image-common (which provides 
etc/system-image/archive-master.tar.xz), but when the  
initramfs-tools-ubuntu-core package was unpacked, this triggered 
update-initramfs which failed since it needs access to 
/etc/system-image/archive-master.tar.xz, but that file had not yet been moved 
into place.

** Affects: system-image (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  move archive_master file out of /etc to avoid it being treated as a
  conffile

Status in “system-image” package in Ubuntu:
  New

Bug description:
  Currently client.ini specifies:

  [gpg]
  archive_master: /etc/system-image/archive-master.tar.xz

  The problem is that file in /etc are automatically marked as conffiles
  by debhelper and as such don't get moved into place until the dpkg
  configure step.

  This caused an issue for the initramfs-tools-ubuntu-core package since that 
Depends on system-image-common (which provides 
  etc/system-image/archive-master.tar.xz), but when the  
initramfs-tools-ubuntu-core package was unpacked, this triggered 
update-initramfs which failed since it needs access to 
/etc/system-image/archive-master.tar.xz, but that file had not yet been moved 
into place.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1198180] Re: possible leak in upstart 1.5

[James Hunt]

@uj__:

 The init process is certainly leaking memory.
How have you proved that init is leaking memory? Can you say that PID 1 is not 
just still busy processing the flurry of events that would result from starting 
all these docker containers? Please provide further details.

 I've looked at the code and it seems like there may be some leaks.
Where?

 The upstart tests are are also leaking memory. Some of that memory is leaked 
 in the tests themselves (allocated and never freed)
The tests may well leak memory as they are not designed to be long-running like 
upstart.

 and some others seem to be leaking in libnih itself.
Again, where? Please provide logs. Note that libnih goes to some lengths to 
avoid leaks by doing automatic garbage collection. If you can produce a test 
program demonstrating a leak, please attach to this bug so we can investigate 
further.

-- 
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/1198180

Title:
  possible leak in upstart 1.5

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 12.04.2 LTS
  Release:12.04
  Package:1.5-0ubuntu7.2
  Kernel:  Linux XXX 3.8.0-23-generic #34~precise1-Ubuntu SMP Wed May 29 
21:12:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  We're starting lxc containers on demand, so there's lots and lots of
  network interfaces going up and down. Udev emits signal, that goes to
  upstart-udev-bridge, and next to the upstart itself. After about 40K
  containers created/destroyed, upstart takes about 250MB or RAM, and it
  grows with every event received/send. Not only RAM is beeing used, but
  also init spends more time for every new event on the socket.

  What happens:
  init uses more RAM and more CPU during lifetime, when lots of network 
interfaces are beeing created/destroyed

  What is expected:
  init work should not change depending on number of events served

  technical detail:
  # pmap -x 1
  7f446f865000   0  237036  237036 rw---[ anon ]
  7fffc694d000   0  24  24 rw---[ stack ]
  7fffc69fe000   0   4   0 r-x--[ anon ]
  ff60   0   0   0 r-x--[ anon ]

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1376283] Re: Process of init --user gradually eats all RAM then the system starts using swap and hangs.

[James Hunt]

Please can you run 'apport-collect 1376283' (ideally when your system is
experiencing the issue).

Also, assuming you have not created any jobs yourself that might contain
confidential information (?), it would be extremely useful if you could
run the following when experiencing the problem and attach
upstart.state.gz to this report:

$ wget http://people.canonical.com/~jhunt/upstart/scripts/get_state.sh
$ sh ./get_state.sh | json_pp | json_pp | gzip -9  /tmp/upstart.state.gz

Thanks!

-- 
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/1376283

Title:
  Process of init --user gradually eats all RAM then the system starts
  using swap and hangs.

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Process of init --user gradually eats all RAM then the system starts
  using swap and hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  Date: Wed Oct  1 18:06:48 2014
  InstallationDate: Installed on 2013-11-09 (325 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release i386 (20131016)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (72 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1376717] [NEW] install failure under systemd

[James Hunt]

Public bug reported:

Setting up lxc (1.1.0~alpha1-0ubuntu5) ...
Failed to issue method call: Unit lxc.service failed to load: No such file or 
directory.
invoke-rc.d: initscript lxc, action start failed.
dpkg: error processing package lxc (--configure):
 subprocess installed post-installation script returned error exit status 6
dpkg: dependency problems prevent configuration of lxc-templates:
 lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however:
  Package lxc is not configured yet.

dpkg: error processing package lxc-templates (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 lxc
 lxc-templates
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  install failure under systemd

Status in “lxc” package in Ubuntu:
  New

Bug description:
  Setting up lxc (1.1.0~alpha1-0ubuntu5) ...
  Failed to issue method call: Unit lxc.service failed to load: No such file or 
directory.
  invoke-rc.d: initscript lxc, action start failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 6
  dpkg: dependency problems prevent configuration of lxc-templates:
   lxc-templates depends on lxc (= 0.8.0~rc1-4ubuntu43); however:
Package lxc is not configured yet.

  dpkg: error processing package lxc-templates (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   lxc
   lxc-templates
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1376758] [NEW] Ability to specify script to call at end of download rather than rebooting

[James Hunt]

Public bug reported:

Currently, after downloading the latest image, system-image-cli reboots
the system.

It would be extremely useful if rather than hard-coding this, system-
image-cli could conditionally call a hook script when it has finished.
Ideally, it would be possible to specify this in /etc/system-
image/client.ini

Since the desired behaviour could well be device/environment specific,
maybe the reboot ability should also be pulled out of
systemimage/reboot.py so that by default, /etc/system-
image/hooks/default - /etc/system-image/hooks/reboot.sh gets run, but
that could be overriden via client.ini.

** Affects: ubuntu-system-image
 Importance: High
 Status: Triaged


** Tags: client

** Summary changed:

- Ability to specify script to call at end of download
+ Ability to specify script to call at end of download rather than rebooting

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

Title:
  Ability to specify script to call at end of download rather than
  rebooting

Status in Ubuntu system image (server/client/updater):
  Triaged

Bug description:
  Currently, after downloading the latest image, system-image-cli
  reboots the system.

  It would be extremely useful if rather than hard-coding this, system-
  image-cli could conditionally call a hook script when it has finished.
  Ideally, it would be possible to specify this in /etc/system-
  image/client.ini

  Since the desired behaviour could well be device/environment specific,
  maybe the reboot ability should also be pulled out of
  systemimage/reboot.py so that by default, /etc/system-
  image/hooks/default - /etc/system-image/hooks/reboot.sh gets run, but
  that could be overriden via client.ini.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1376758/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop

[James Hunt]

Just got this running hud 14.10+14.10.20140924-0ubuntu1. Just typing in
a console and my CPU chewing script popped up a window to alert me to
the fact.

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

Title:
  hud-service is eating up 100% of one of my CPUs in a poll loop

Status in Unity HUD:
  Confirmed
Status in “hud” package in Ubuntu:
  In Progress

Bug description:
  hud-service is polling like crazy:

  Context Switches:
PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
2295 hud-service  46084.6342.94 46127.58 (very high)
2325 hud-service  0.09 0.00 0.09 (very low)
2329 hud-service  0.07 0.00 0.07 (very low)
2340 hud-service  0.05 0.00 0.05 (very low)
   Total  46084.8442.94 46127.78

  File I/O operations:
   No file I/O operations detected.

  System calls traced:
PID  Process  Syscall   CountRate/Sec
2295 hud-service  poll 83   23124.8503
2295 hud-service  write10   0.2313
2295 hud-service  sendmsg   4   0.0925
2325 hud-service  restart_syscall   1   0.0231
2329 hud-service  restart_syscall   1   0.0231
2340 hud-service  restart_syscall   1   0.0231
   Total  100   23125.2435

  (gdb) where
  #0  0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #2  0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #3  0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #4  0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #5  0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #6  0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #7  0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #8  0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2
  #9  0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int) ()
  #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() ()
  #17 0x00441e43 in hud::service::WindowImpl::activate() ()
  #18 0x00439f6a in 
hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) ()
  #19 0x0043a672 in hud::service::QueryImpl::refresh() ()
  #20 0x0044b115 in ?? ()
  #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0045662a in 
hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString 
const, unsigned int) ()
  #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #24 0x00467361 in 
ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, 
QString const, unsigned int) ()
  #25 0x004678bd in ?? ()
  #26 0x00467c63 in 
ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, 
void**) ()
  #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #28 0x7fda8435e22e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #33 

[Touch-packages] [Bug 1281061] Re: initctl eating cpu on mako #181

[James Hunt]

@Fabian - thanks for reporting but we need a lot more detail before we
can get to the bottom of this (ps output, strace [you need to install it
in dev mode], etc).

-- 
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/1281061

Title:
  initctl eating cpu on mako #181

Status in “upstart” package in Ubuntu:
  Expired

Bug description:
  On Ubuntu image #181 on mako my phone is hot. I checked top and found
  initctl eating 96% of the cpu..

  This may be related to bug 1281057 as my phone refuses to lock.

  Unfortunately I couldn't get the bug report done on the phone because
  the battery died (unsurprisingly) mid way through reporting it.
  Managed to get this output from top though.

  top - 10:34:05 up 1 day, 20:23,  1 user,  load average: 4.19, 4.14, 3.82
  Tasks: 244 total,   2 running, 242 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 49.1 us,  5.4 sy,  0.0 ni, 45.1 id,  0.4 wa,  0.0 hi,  0.0 si,  0.0 
st
  KiB Mem:   1916236 total,  1855748 used,60488 free,18420 buffers
  KiB Swap:   524284 total,   115420 used,   408864 free.   196160 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   1981 phablet   20   0  679256 665780   1160 S   0.3 34.7  33:23.31 init  
  
586 message+  20   0  280608 276924712 S   0.0 14.5  26:18.81 
dbus-daemon 
  1 root  20   0  210636 206636   1056 S   0.0 10.8  12:16.86 init  
  
   2211 phablet   20   0  553308 127668  77840 S  85.7  6.7  49:53.31 unity8
  
598 root  20   0   88792  86892584 R  96.1  4.5 433:39.94 initctl   
  
   2318 phablet   20   0  296952  40432  33060 S   0.0  2.1   0:26.02 
maliit-ser+ 
   1903 root  20   0  241404  27880  20500 S  13.0  1.5  10:27.68 
unity-syst+ 
   9631 phablet   20   0  216224  19924  14828 S   0.0  1.0   0:01.78 
telephony-+ 
   2350 phablet   20   0   55260  19540   2776 S   0.0  1.0   1:28.08 
indicator-+ 
   1052 root  20   0   52248  19244   2252 S   0.0  1.0  22:39.85 upowerd   
  
   2080 phablet   20   0   47300  12604   3396 S   0.0  0.7   1:43.27 
mission-co+ 
   9368 phablet   20   0   80832  11872   9988 S   0.0  0.6   0:00.61 
telephony-+ 
   1062 root  20   0   42916  11548   2544 S   0.0  0.6  84:53.39 polkitd   
  
   2205 phablet   20   0   96980  11464   9280 S   0.0  0.6   0:05.66 
hud-service 
   9360 phablet   20   0   52164   9592   8120 S   0.0  0.5   0:00.21 
telephony-+ 
   2234 phablet   20   0  134336   8716   5288 S   0.0  0.5   0:16.43 
address-bo+ 
   2093 phablet9 -11  203588   7304   4964 S   0.0  0.4   5:37.30 pulseaudio

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1348784] Re: thermald prevents unmounting /dev/sda1 in recovery mode

[James Hunt]

It sounds like you may have modified files below /etc/initramfs-tools/
and/or /usr/share/initramfs-tools/, or created additional scripts that
are somehow modifying the boot path. Further, I think you need to
understand why single is being specified on the boot command-line as
that is non-standard.

I would try installing a fresh 14.10 system (maybe in a VM) and
comparing those directories in your fresh environment with your main
system environment.

-- 
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/1348784

Title:
  thermald prevents unmounting /dev/sda1 in recovery mode

Status in “thermald” package in Ubuntu:
  In Progress
Status in “upstart” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is started 
in the recovery mode it is not possible to unmount /dev/sda1 because thermald 
is running. Interestingly lsof hasn't even showed that something has a file 
descriptor on /dev/sda1 open but executing stop thermald has worked as a 
workaround.
  --- 
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  NonfreeKernelModules: fglrx
  Package: upstart 1.13.2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic 
root=UUID=af27feae-4c9e-4b5f-a1e1-900c0e71c5cb ro elevator=cfq
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Tags:  utopic
  Uname: Linux 3.16.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.lxdm.lxdm.conf: [modified]
  mtime.conffile..etc.init.control.alt.delete.conf: 2012-05-05T17:10:11.434470
  mtime.conffile..etc.init.tty2.conf: 2014-05-29T05:14:16.791093
  mtime.conffile..etc.init.tty3.conf: 2012-05-05T17:10:49.238469
  mtime.conffile..etc.init.tty4.conf: 2012-05-05T17:10:58.066468
  mtime.conffile..etc.init.tty5.conf: 2012-05-05T17:11:02.938468
  mtime.conffile..etc.init.tty6.conf: 2012-05-05T17:11:09.442468
  mtime.conffile..etc.lxdm.lxdm.conf: 2012-12-23T19:04:26.948844

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

[James Hunt]

@elfy - is plymouth is still crashing for you?

$ sudo grep SEGV /var/log/syslog

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

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  Fix Released

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1348784] Re: thermald prevents unmounting /dev/sda1 in recovery mode

[James Hunt]

 UPSTART_EVENTS=runlevel
 UPSTART_INSTANCE=
 UPSTART_JOB=rcS
This is the cause of your problem - you are not actually in recovery mode. What 
is your /proc/cmdline? Have you modified /etc/default/grub or any of the 
initramfs configuration?

-- 
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/1348784

Title:
  thermald prevents unmounting /dev/sda1 in recovery mode

Status in “thermald” package in Ubuntu:
  In Progress
Status in “upstart” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is started 
in the recovery mode it is not possible to unmount /dev/sda1 because thermald 
is running. Interestingly lsof hasn't even showed that something has a file 
descriptor on /dev/sda1 open but executing stop thermald has worked as a 
workaround.
  --- 
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  NonfreeKernelModules: fglrx
  Package: upstart 1.13.2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic 
root=UUID=af27feae-4c9e-4b5f-a1e1-900c0e71c5cb ro elevator=cfq
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Tags:  utopic
  Uname: Linux 3.16.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.lxdm.lxdm.conf: [modified]
  mtime.conffile..etc.init.control.alt.delete.conf: 2012-05-05T17:10:11.434470
  mtime.conffile..etc.init.tty2.conf: 2014-05-29T05:14:16.791093
  mtime.conffile..etc.init.tty3.conf: 2012-05-05T17:10:49.238469
  mtime.conffile..etc.init.tty4.conf: 2012-05-05T17:10:58.066468
  mtime.conffile..etc.init.tty5.conf: 2012-05-05T17:11:02.938468
  mtime.conffile..etc.init.tty6.conf: 2012-05-05T17:11:09.442468
  mtime.conffile..etc.lxdm.lxdm.conf: 2012-12-23T19:04:26.948844

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1375874] Re: upstart leaks memory in init and upstart-udev-bridge

[James Hunt]

*** This bug is a duplicate of bug 1198180 ***
https://bugs.launchpad.net/bugs/1198180

** This bug has been marked a duplicate of bug 1198180
   possible leak in upstart 1.5

-- 
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/1375874

Title:
  upstart leaks memory in init and upstart-udev-bridge

Status in “upstart” package in Ubuntu:
  New

Bug description:
  init and upstart-udev-bridge leak a lot of memory after starting a lot
  of containers.

  init's memory usage grows steadily and ends up using about 80% CPU
  when it's using ~250 MB of RAM. upstart-udev-bridge uses about 1 GB of
  RAM.

  The Ubuntu version is 12.04 with the lts trusty kernel. The system is
  fully updated as of today.

  expected behaviour:
  init's memory usage should remain stable, not grow over time
  upstart-udev-bridge should use less than 40 MB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upstart 1.5-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-36.63~precise1-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  Date: Tue Sep 30 18:50:18 2014
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
amd64 (20140204)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1198180] Re: possible leak in upstart 1.5

[James Hunt]

This almost sounds like bug 1235649, but unlikely given that the
upstart-udev-bridge uses the correct NIH D-Bus calls.

I suspect the reason for the memory growth is that the events that are
being created cannot be destroyed until some other job has finished with
them. Once that happens, memory will be reclaimed automatically by
Upstart.

Please could those affected attach the output of 'initctl list'
(compressed if necessary).

-- 
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/1198180

Title:
  possible leak in upstart 1.5

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 12.04.2 LTS
  Release:12.04
  Package:1.5-0ubuntu7.2
  Kernel:  Linux XXX 3.8.0-23-generic #34~precise1-Ubuntu SMP Wed May 29 
21:12:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  We're starting lxc containers on demand, so there's lots and lots of
  network interfaces going up and down. Udev emits signal, that goes to
  upstart-udev-bridge, and next to the upstart itself. After about 40K
  containers created/destroyed, upstart takes about 250MB or RAM, and it
  grows with every event received/send. Not only RAM is beeing used, but
  also init spends more time for every new event on the socket.

  What happens:
  init uses more RAM and more CPU during lifetime, when lots of network 
interfaces are beeing created/destroyed

  What is expected:
  init work should not change depending on number of events served

  technical detail:
  # pmap -x 1
  7f446f865000   0  237036  237036 rw---[ anon ]
  7fffc694d000   0  24  24 rw---[ stack ]
  7fffc69fe000   0   4   0 r-x--[ anon ]
  ff60   0   0   0 r-x--[ anon ]

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1374610] Re: telinit u makes upstart's /sbin/init lose all information on running processes (PIDs)

[James Hunt]

Upstart only gained the ability to re-exec statefully in Raring. The man
page for telinit on Lucid explains that state is not preserved and also
warns that running this command is not recommended.

Note that upstart has to re-exec itself on Lucid if certain key packages
are upgraded to ensure a clean filesystem unmount. However, to minimise
issues, the re-exec only occurs at shutdown after all jobs have stopped.

In summary: do not run 'telinit u' manually as the man page warns.

** Changed in: upstart (Ubuntu)
   Status: New = Won't Fix

-- 
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/1374610

Title:
  telinit u makes upstart's /sbin/init lose all information on running
  processes (PIDs)

Status in “upstart” package in Ubuntu:
  Won't Fix

Bug description:
  running telinit u causes init to re-exec itself. 
  It loses all process state information in the process, so that services can 
no longer be stopped/restarted, and restart or start will either start a daemon 
twice or fail to start it as a consequence.

  There needs to be a way that either:
  - init, telinit, initctl and possibly other manual pages warn of this loss of 
information;
  or 
  - this feature gets removed,
  or
  - init remembers the process IDs across a restart unless told otherwise.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: upstart 0.6.5-8
  ProcVersionSignature: Ubuntu 2.6.32-65.131-generic-pae 2.6.32.63+drm33.26
  Uname: Linux 2.6.32-65-generic-pae i686
  Architecture: i386
  Date: Fri Sep 26 21:35:01 2014
  SourcePackage: upstart

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1374521] Re: ifup should specify '-allow=auto' not '-allow=hotplug'

[James Hunt]

$ systemctl status networking

networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
   `-50-insserv.conf-$network.conf
   Active: active (exited) since Mon 2014-09-29 09:22:44 UTC; 1min 51s ago
  Process: 332 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)

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

Title:
  ifup should specify '-allow=auto' not '-allow=hotplug'

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  /lib/systemd/system/ifup@.service specifies:

    ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

    ExecStart=/sbin/ifup --allow=auto %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1348784] Re: thermald prevents unmounting /dev/sda1 in recovery mode

[James Hunt]

I too am unable to recreate this problem - dbus should certainly not be
running in recovery mode because dbus is 'start on local-filesystems',
but that event will not have been emitted since mountall is not run in
recovery mode.

Can you confirm you are entering recovery mode from the grub menu
(Advanced options - recovery)?

Can you also check the following:

1) Enter recovery mode.
2) Select the root shell option.
3) Run set|grep UPSTART.

What you should see is:

UPSTART_EVENTS=recovery
UPSTART_INSTANCE=
UPSTART_JOB=friendly-recovery

Can you also check that you don't have an /etc/init/dbus.override and
that your /etc/init/dbus.conf is unmodified - running 'apport-collect -p
upstart 1348784' will do this for you.

Attaching the output of 'ps -efwww' and 'initctl list' from recovery
mode could also be useful.

-- 
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/1348784

Title:
  thermald prevents unmounting /dev/sda1 in recovery mode

Status in “thermald” package in Ubuntu:
  In Progress
Status in “upstart” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is
  started in the recovery mode it is not possible to unmount /dev/sda1
  because thermald is running. Interestingly lsof hasn't even showed
  that something has a file descriptor on /dev/sda1 open but executing
  stop thermald has worked as a workaround.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1374521] [NEW] ifup should specify '-allow=auto' not '-allow=hotplug'

[James Hunt]

Public bug reported:

/lib/systemd/system/ifup@.service specifies:

  ExecStart=/sbin/ifup --allow=hotplug %I

This really needs to be:

  ExecStart=/sbin/ifup --allow=hotplug %I

Since otherwise, for systems that don't use network-manager, the service
will only bring up interfaces which have specified allow-hotplug $if
in /etc/network/interfaces*.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
Uname: Linux 3.16.0-17-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 26 16:54:12 2014
InstallationDate: Installed on 2014-04-11 (167 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: systemd
UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Martin Pitt (pitti)
 Status: New


** Tags: amd64 apport-bug utopic

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  ifup should specify '-allow=auto' not '-allow=hotplug'

Status in “systemd” package in Ubuntu:
  New

Bug description:
  /lib/systemd/system/ifup@.service specifies:

ExecStart=/sbin/ifup --allow=hotplug %I

  This really needs to be:

ExecStart=/sbin/ifup --allow=hotplug %I

  Since otherwise, for systems that don't use network-manager, the
  service will only bring up interfaces which have specified allow-
  hotplug $if in /etc/network/interfaces*.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 16:54:12 2014
  InstallationDate: Installed on 2014-04-11 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (141 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1373588] Re: Starting/Stopping services causes init: Error while reading from descriptor: Bad file descriptor

[James Hunt]

That should be ubuntu-bug 1373588 of course :-)

-- 
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/1373588

Title:
  Starting/Stopping services causes init: Error while reading from
  descriptor: Bad file descriptor

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Starting and stopping services via upstart causes errors in the form of
  init: Error while reading from descriptor: Bad file descriptor

  with a lot of services and on multiple machines featuring different
  hardware configurations.

  The services start without errors if launched with the same parameters
  from the command line.

  A result of this is the inability to launch lightdm.
  The system becomes near unuseable.


  Ubuntu version is 14.04.01
  upstart package is up to date.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1373588] Re: Starting/Stopping services causes init: Error while reading from descriptor: Bad file descriptor

[James Hunt]

Thanks for reporting. Please run ubuntu-bug 373588 which will attach
required logs to this bug.

-- 
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/1373588

Title:
  Starting/Stopping services causes init: Error while reading from
  descriptor: Bad file descriptor

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Starting and stopping services via upstart causes errors in the form of
  init: Error while reading from descriptor: Bad file descriptor

  with a lot of services and on multiple machines featuring different
  hardware configurations.

  The services start without errors if launched with the same parameters
  from the command line.

  A result of this is the inability to launch lightdm.
  The system becomes near unuseable.


  Ubuntu version is 14.04.01
  upstart package is up to date.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp