[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to the login screen with no
indication of what went wrong.
== Session "dead" ==
- chmod 444 ~/.cache
- chmod 000 ~/.config
- chmod 444 ~
- chmod 000 ~
In this scenario, the system just freezes: the cursor is unresponsive
and users will be reaching for the power button.
= Observation =
These scenarios would all be caused by human error.
However, clearly it is possible for the system to detect such issues and
either alert the user to the problem or simply just fix the problem.
This does not happen in Ubuntu 18.04 LTS though.
= Idea =
Have the display manager call a utility prior to executing the users
preferred session. This utility -- which could be a simple shell script
I think ("friendly-session-fixer" maybe? :) -- would do one or both of
the following:
- Perform checks for the issues outlined above warn the user graphically
if any are found.
- Fix any issues found to allow the user to login.
However they are treated, all issues should also be logged in the
journal (could be the user journal, but the system journal may be best
to allow admins to spot such issues being detected more easily?)
= Rationale =
1) All the problems above, although user-generated, are:
- trivially fixable.
- potentially very hard / impossible for a naeve user to debug and resolve.
2) By handling such errors, users won't have a bad experience of Linux
if they inadvertently perturb a critical file.
3) Users will not need to resort to a re-install (which I can imagine
some may have to given the current behaviour).
= Ideas for further checks =
- Check to ensure key files exist and if not, copy them in from /etc/skel/,
etc.
- Check to ensure users home directory is owned by them and not root, etc.
- If the home partition / disk is 100% full, the script could logrotate and
compress the contents of ~/.cache/ ?
= Notes =
- You could argue that the session managers themselves should deal with
- these issues. In some cases that may be a fair comment. However, by
- having a single central check/fix script, the problems can be handled
- centrally without the issue whereby some session managers tolerate
- certain scenarios whereas others don't.
+ You could argue that the session managers themselves should deal with these
issues. In some cases that may be a fair comment. However, by having a single
central check/fix script, the problems can be handled centrally without the
issue whereby some session managers tolerate certain scenarios whereas others
don't.
+ ---
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-10-29 (0 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: gdm3 3.28.0-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags: bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206695/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
apport info added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800277] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
I can do that if really required, but this is not a bug with my system - it's just the way the system works right now, so I'm suggesting an idea for how we can make it better :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800277] [NEW] "chmod u-w ~/.ICEauthority" breaks login
Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to the login screen with no
indication of what went wrong.
== Session "dead" ==
- chmod 444 ~/.cache
- chmod 000 ~/.config
- chmod 444 ~
- chmod 000 ~
In this scenario, the system just freezes: the cursor is unresponsive
and users will be reaching for the power button.
= Observation =
These scenarios would all be caused by human error.
However, clearly it is possible for the system to detect such issues and
either alert the user to the problem or simply just fix the problem.
This does not happen in Ubuntu 18.04 LTS though.
= Idea =
Have the display manager call a utility prior to executing the users
preferred session. This utility -- which could be a simple shell script
I think ("friendly-session-fixer" maybe? :) -- would do one or both of
the following:
- Perform checks for the issues outlined above warn the user graphically
if any are found.
- Fix any issues found to allow the user to login.
However they are treated, all issues should also be logged in the
journal (could be the user journal, but the system journal may be best
to allow admins to spot such issues being detected more easily?)
= Rationale =
1) All the problems above, although user-generated, are:
- trivially fixable.
- potentially very hard / impossible for a naeve user to debug and resolve.
2) By handling such errors, users won't have a bad experience of Linux
if they inadvertently perturb a critical file.
3) Users will not need to resort to a re-install (which I can imagine
some may have to given the current behaviour).
= Ideas for further checks =
- Check to ensure key files exist and if not, copy them in from /etc/skel/, etc.
- Check to ensure users home directory is owned by them and not root, etc.
- If the home partition / disk is 100% full, the script could logrotate and
compress the contents of ~/.cache/ ?
= Notes =
You could argue that the session managers themselves should deal with
these issues. In some cases that may be a fair comment. However, by
having a single central check/fix script, the problems can be handled
centrally without the issue whereby some session managers tolerate
certain scenarios whereas others don't.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340106] Re: provide option to display list of available image revisions
Yep - that was handled with lp:~jamesodhunt/goget-ubuntu-touch/add-list- images-option. ** Changed in: goget-ubuntu-touch (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340106 Title: provide option to display list of available image revisions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1340106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** 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
[Bug 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: [SRU] segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot loops
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot loops
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
\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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: upstart (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368798] Re: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368798 Title: [Greeter] horizonal rule on pin unlock screen too thin (looks like a scratch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
i386+amd64 are packaged here: https://launchpad.net/~jamesodhunt/+archive/ubuntu/bug-1447756/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438650] Re: Fix description in snappy-system.txt
This issue was resolved on MP https://code.launchpad.net/~jamesodhunt/snappy/add-transactional- updates-doc/+merge/255719. ** Changed in: golang-phablet-tools-ubuntu-device-flash (Ubuntu) Status: Confirmed = Invalid ** Changed in: snappy-ubuntu Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438650 Title: Fix description in snappy-system.txt To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1438650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441197] [NEW] devices created as files
Public bug reported: The s-i archives that u-d-f unpacks specify the contents of /dev. However, running the following on a snappy system gives unexpected results: ubuntu@localhost:~$ ls -l /dev|grep ^-|wc -l 0 ubuntu@localhost:~$ ls -l /dev|egrep ^(b|c)|wc -l 181 ubuntu@localhost:~$ sudo mount -obind / /mnt ubuntu@localhost:~$ ls -l /mnt/dev/|grep ^-|wc -l 80 ubuntu@localhost:~$ ls -l /mnt/dev/|egrep ^(b|c)|wc -l 0 The real files in /dev underneath the devtmpfs mount are files, not char and block devices as they should be. ** Affects: goget-ubuntu-touch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441197 Title: devices created as files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1441197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438650] Re: Fix description in snappy-system.txt
The inconsistency seems to originate in udf's diskimage/core_uboot.go. ** Also affects: golang-phablet-tools-ubuntu-device-flash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438650 Title: Fix description in snappy-system.txt To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1438650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file
LKML thread: https://lkml.org/lkml/2015/3/16/474 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV
** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1300235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at near of file
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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: [SRU] ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1300235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
** Also affects: upstart (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: [SRU] ubuntu-touch livefs builds kill upstart in host
** 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
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430403] Re: ubuntu-touch livefs builds kill upstart in host
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430403 Title: ubuntu-touch livefs builds kill upstart in host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1430403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
** Changed in: upstart (Ubuntu Vivid) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
The good news is that this test failure is a real bug: running 1024 job instances of what is effectively the failing tests shows... - 3.18 kernel: 0 job instances have incorrect size. - 3.19 kernel: 848 job instances have the **incorrect** size (!!) Figures are from a fully-updated amd64 vivid system booted to use Upstart and simply toggling the kernel being used. I've tried to recreate the failure using script(1) and dd(1), but so far this has proven unsuccessful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429756] Re: FTBFS: test_job_process fails in majority of cases
'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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429756 Title: FTBFS: test_job_process fails in majority of cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1429756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405795] Re: network config feature (please export /etc/network/interfaces.d to writable)
** Changed in: ubuntu-core-config (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) ** Changed in: ubuntu-core-config (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405795 Title: network config feature (please export /etc/network/interfaces.d to writable) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1405795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob
** Changed in: upstart (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425685 Title: Missing input sanitation in upstart logrotation cronjob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob
Fixed in upstart 1.13.2-0ubuntu9, currently in the proposed pocket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425685 Title: Missing input sanitation in upstart logrotation cronjob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425685 Title: Missing input sanitation in upstart logrotation cronjob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425685] Re: Missing input sanitation in upstart logrotation cronjob
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425685 Title: Missing input sanitation in upstart logrotation cronjob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1425685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425265] Re: x86 kvm image generated with ubuntu-device-flash using --device generic_i386 on amd64 host results in image with fs corruption
As another data point, using udf 0.3+14.10.20140807-0ubuntu1 and having created an image using... $ sudo ubuntu-device-flash -v --revision 220 core --size 3 -o i386-r220.img --channel ubuntu-core/devel-proposed --developer-mode --device generic_i386 ... I'm able to boot successfully on real hardware (Intel Atom N450) and don't see the errors above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425265 Title: x86 kvm image generated with ubuntu-device-flash using --device generic_i386 on amd64 host results in image with fs corruption To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1425265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413922] Re: lxc unprivileged containers broken
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413922] Re: lxc unprivileged containers broken
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413922] [NEW] lxc unprivileged containers broken
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1413922] [NEW] lxc unprivileged containers broken
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413922] Re: lxc unprivileged containers broken
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413922] Re: lxc unprivileged containers broken
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 Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1413922 Title: lxc unprivileged containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1413922/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1300235] Re: init crashed with SIGSEGV
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1300235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399710] Re: no audible warning of high volume level
Another use-case for this is if you start playing music, lock the screen and put the phone in your pocket. Realising the volume is too low, you raise it without removing the phone from your pocket. Again, we should warn the user that they are about to cross the threshold somehow as they are not currently looking at the screen (which is off anyway). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399687] [NEW] Provide version_detail for latest revision on server
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399687 Title: Provide version_detail for latest revision on server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1399687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1399710] [NEW] no audible warning of high volume level
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396497] [NEW] 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot
Public bug reported: qemu-img _may_ be working as designed, but it feels like this could be a bug. I'd certainly prefer to only allow unique snapshot names (unless maybe something like a --force-non-unique-snapshot-names was also specified). If this really is correct behaviour, it should be documented as qemu- img(1) currently specifies no details whatsoever regarding expected behaviour or valid snapshot names. $ qemu-img snapshot -l image.cow $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow $ Note also how snapshot deletion works in reverse order - the oldest snapshot with a given name is deleted first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 2.1+dfsg-4ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 26 08:28:16 2014 InstallationDate: Installed on 2014-04-11 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 719 2 0.0 [kvm-irqfd-clean] MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to vivid on 2014-05-08 (201 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: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1396497 Title: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1396497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1396497] [NEW] 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot
Public bug reported: qemu-img _may_ be working as designed, but it feels like this could be a bug. I'd certainly prefer to only allow unique snapshot names (unless maybe something like a --force-non-unique-snapshot-names was also specified). If this really is correct behaviour, it should be documented as qemu- img(1) currently specifies no details whatsoever regarding expected behaviour or valid snapshot names. $ qemu-img snapshot -l image.cow $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 $ qemu-img snapshot -c foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 1 foo 0 2014-11-26 08:30:53 00:00:00.000 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 2 foo 0 2014-11-26 08:30:58 00:00:00.000 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow Snapshot list: IDTAG VM SIZEDATE VM CLOCK 3 foo 0 2014-11-26 08:31:00 00:00:00.000 $ qemu-img snapshot -d foo image.cow $ qemu-img snapshot -l image.cow $ Note also how snapshot deletion works in reverse order - the oldest snapshot with a given name is deleted first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qemu-utils 2.1+dfsg-4ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 26 08:28:16 2014 InstallationDate: Installed on 2014-04-11 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S 0 0 719 2 0.0 [kvm-irqfd-clean] MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to vivid on 2014-05-08 (201 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: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396497 Title: 'qemu-img snapshot' allows new snapshot to be created with the name of an existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1396497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394250] Re: system-settings consuming 100% CPU
Problem still occuring. phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build 169 phablet@ubuntu-phablet:~$ cat /etc/device-build 20141119-db417fa phablet@ubuntu-phablet:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394250 Title: system-settings consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1394250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281061] Re: initctl eating cpu on mako #181
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281061 Title: initctl eating cpu on mako #181 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1281061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394250] [NEW] system-settings consuming 100% CPU
Public bug reported: krillin: phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build 161 phablet@ubuntu-phablet:~$ cat /etc/device-build 20141106-572f18d phablet@ubuntu-phablet:~$ 'strace -p $pid -s 1024 -Ffv' attached. ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Attachment added: system-settings.strace.gz https://bugs.launchpad.net/bugs/1394250/+attachment/4263834/+files/system-settings.strace.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394250 Title: system-settings consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1394250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394250] Re: system-settings consuming 100% CPU
I think this could be related to bug 1393427 since I am still unable to install updates (there are more now). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394250 Title: system-settings consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1394250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383433] Re: please package the cloud-init ci-tool
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1383433 Title: please package the cloud-init ci-tool To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1383433/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1383433] Re: please package the cloud-init ci-tool
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383433 Title: please package the cloud-init ci-tool To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1383433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381075 Title: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385444 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385444 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385464] Re: logrotate fails to run, if status file is corrupt (logrotate running during reboot?)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385464 Title: logrotate fails to run, if status file is corrupt (logrotate running during reboot?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381075 Title: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380674] Re: [needs-packaging] Add new package ubuntu-core-upgrader
Discussed with slangasek who is happy with having this package in the archive (universe). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380674 Title: [needs-packaging] Add new package ubuntu-core-upgrader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1380674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381075 Title: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383085] Re: background in app carousel view does not show background image
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383085 Title: background in app carousel view does not show background image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383086] [NEW] rebooting defeats the screen lock timeout
*** This bug is a security vulnerability *** Public security bug reported: If you enable pin unlock, then repeatedly enter the incorrect pin, eventually you'll get a message stating that the phone cannot be unlocked for 5 minutes. However, this restriction can be trivially bypassed by simply rebooting the phone (which takes less than 5 minutes :-) krillin, r117. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383086 Title: rebooting defeats the screen lock timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383085] [NEW] background in app carousel view does not show background image
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383085 Title: background in app carousel view does not show background image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380674] Re: [needs-packaging] Add new package ubuntu-core-upgrader
@dholbach: Thanks for reviewing! Package updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380674 Title: [needs-packaging] Add new package ubuntu-core-upgrader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1380674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380674] Re: [needs-packaging] Add new package ubuntu-core-upgrader
LGTM! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380674 Title: [needs-packaging] Add new package ubuntu-core-upgrader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1380674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381075 Title: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381075 Title: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1381075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380674] [NEW] Add new package ubuntu-core-upgrader
Public bug reported: Please add package lp:~ubuntu-foundations-team/+junk/ubuntu-core- upgrader to the archive. This package is required for the Ubuntu Core project. ** Affects: ubuntu Importance: Undecided Assignee: James Hunt (jamesodhunt) Status: In Progress ** Tags: needs-packaging ** Tags added: needs-packaging ** Changed in: ubuntu Assignee: (unassigned) = James Hunt (jamesodhunt) ** Changed in: ubuntu Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380674 Title: Add new package ubuntu-core-upgrader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1380674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379021] Re: after utopic upgrade: boot delays for 2 minutes
@Dylan - which packages did you purge? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379021 Title: after utopic upgrade: boot delays for 2 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1379021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
