Hi Steve - ah, sorry - hadn't registered that you'd already copied the
package into the queue (we now have 2 :-) Could mine be deleted please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.lau
** 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.
** Changed in: upstart (Ubuntu Vivid)
Status: New => In Progress
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upst
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 sil2
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/baraj
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/l
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 ar
** 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
** Changed in: upstart
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot
MP raised on lp:upstart to start the trickle-down to the rtm package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reb
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 utopi
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
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
** Changed in: upstart
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bu
\o/. Yes, Upstart uses asserts extremely agressively. It's unfortunate
that we've never hit this issue in testing but I'm currently working on
new tests for this slightly unusual scenario.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
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
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 'i
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 'i
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
I've rebuild the fix in a clean environment and the init binary below
now boots fine for me on a bq aquaris E4.5:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hi ondra/ogra - Can you comment on my suggestions in #6 and #7? My
device is still bricked so if you have any suggestions on how to perform
a full reset, that'd be great as udf is unable to recover it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
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
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 b
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
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfau
Test binaries are available here:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
ht
Screenshot showing the super-thin divider.
** Attachment added: "scratch.jpg"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
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 ent
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in lo
LKML thread: https://lkml.org/lkml/2015/3/16/474
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: upstart test_job_process fails in majority of cases /
** Package changed: upstart (Ubuntu) => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init (chromium-browser) crashed with SIGSEG
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
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
Playing around with strings(1), I've found this:
$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep "\"
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
F
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
** Summary changed:
- ubuntu-touch livefs builds kill upstart in host
+ [SRU] ubuntu-touch livefs builds kill upstart in host
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** 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
** 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
** Also affects: upstart (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
ubuntu-touch livefs bui
Note that we cannot add new unit tests for this fix without making it a
much bigger change since the problematic function is static.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net
It is relatively simple to trigger the bug: run a script that loops
creating a .conf file and an .override file, then deletes the .conf file
before deleting the override file.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to up
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
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
igh
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
ubuntu-touch
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FT
Some quick tests suggest that this issue only seems to affect long runs
of nul bytes (even if they are terminated by visible chars + a '\n').
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.laun
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
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
Tou
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 b
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):
subproce
'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 sp
Fixed in upstart 1.13.2-0ubuntu9, currently in the proposed pocket.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Title:
Missing input sanitation in upstart logro
** Changed in: upstart (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Title:
Missing input sanitation in upstart logro
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in
Note - this problem only affects vivid fwics. Further, it does not
affect Touch (since that uses Upstart as PID 1).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Ti
Thanks Martin!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1424992
Title:
files in /tmp not being cleared on boot
Status in systemd package in Ubuntu:
Fix Committed
Public bug reported:
My system has been booted for 2 1/2 hours and yet /tmp contains old
files from 2015-02-19.
$ sudo systemctl|grep tmpfiles
systemd-tmpfiles-setup-dev.service
loaded active exited
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 be
Ah - seems we'd actually need to add in a couple of loops in those
original dep-8 tests: run the tests as root, then run as a non-priv user
too! :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.la
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-s
Hi Brian - does running synaptic-pkexec in a terminal trigger the crash?
If not, we really need a trace showing what happens in cbOpenHomepage,
specifically what the 'cmd' vector contains.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
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 cur
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 j
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_up
Hi Fabian,
The problem you are having seem to be related to mtp-server respawning
continuously. This may not be the same issue as originally reported, so
please open a new bug against the mtp-server package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
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 not
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 becau
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 n
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: "r
I've added more info to the cookbook wrt respawn. Here's the simplest
method of detecting hitting the respawn limit:
http://upstart.ubuntu.com/cookbook/#detecting-a-job-hitting-its-respawn-
limit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
Seems that the camera issue is not only just when the lens is covered.
The live preview feature has gone away, so if the camera is running, the
carousel will show an "invisible" black camera app every time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
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 t
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 th
*** 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 rebo
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 o
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
@Dylan - which packages did you purge?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1379021
Title:
after utopic upgrade: boot delays for 2 minutes
Status in “upstart” p
** Changed in: system-image (Ubuntu)
Assignee: James Hunt (jamesodhunt) => Michael Vogt (mvo)
** Changed in: system-image (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Giorgio - the spec doesn't appear to specify the colour that should be
used for the highlights. If the highlight colour is fixed as say yellow,
it would have no effect if the background colour of the page was the
same colour. What if the background colour is white but the text is
yellow?
--
You r
> Where do I add --debug? The Linux command line?
Yes:
1) Hold down control key at power-on to enter grub menu.
2) Press 'e' to edit the top (default) kernel command-line.
3) Use the cursor keys to move down the the line that begins with
"linux".
4) Press the END key (or use cursors again).
5)
Public bug reported:
The menu doesn't offer a find/search option to look for text on a web
page.
** Affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Hi Dylan,
Thanks for taking the time to report this issue. Please can you do the
following:
1) Run 'apport-collect 1379021' to attach required logs to this bug
report.
2) Attach /etc/network/interfaces (and any files you've created in
/etc/network/interfaces.d/).
3) Attach /etc/fstab
4) Add '-
Public bug reported:
system-image currently supports a 'bootme' option that may be present in
the JSON and instructs Touch to reboot _after it has finished
downloading the current file_.
However, Core has a slightly different requirement. It attempts to
minimise reboots, but when certain packages
@uj__:
> The init process is certainly leaking memory.
How have you proved that init is leaking memory? Can you say that PID 1 is not
just still busy processing the flurry of events that would result from starting
all these docker containers? Please provide further details.
> I've looked at the
Public bug reported:
Currently client.ini specifies:
[gpg]
archive_master: /etc/system-image/archive-master.tar.xz
The problem is that file in /etc are automatically marked as conffiles
by debhelper and as such don't get moved into place until the dpkg
configure step.
This caused an issue for t
I still don't understand why the current icon:
a) is hard-edged - every other icon (in fact every other widget?) has
rounded corners.
Is this simply to discriminate it from everything else? If so, is there any
other way we can do this that is more in keeping with
the softer-edged appeara
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1351423
Title:
dash icon significantly different to th
Rationale for adding icons:
1) The standard shutdown (power) icon, and the restart (circular arrow)
are almost universally recognised (to the extent that you wonder if we
could actually remove the text).
2) Colours only work if you can discriminate between then. Red and green
are alas an unfortun
Public bug reported:
Holding the physical power button displays the shutdown menu with
options to shutdown, restart or cancel. These buttons are colour-coded
but for added clarity I think we should add icons to represent the
operations.
Note that if this menu is changed, there are other parts of
Just got this running hud 14.10+14.10.20140924-0ubuntu1. Just typing in
a console and my CPU chewing script popped up a window to alert me to
the fact.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hud in Ubuntu.
https://bug
Public bug reported:
Currently, after downloading the latest image, system-image-cli reboots
the system.
It would be extremely useful if rather than hard-coding this, system-
image-cli could conditionally call a hook script when it has finished.
Ideally, it would be possible to specify this in /e
Public bug reported:
Setting up lxc (1.1.0~alpha1-0ubuntu5) ...
Failed to issue method call: Unit lxc.service failed to load: No such file or
directory.
invoke-rc.d: initscript lxc, action "start" failed.
dpkg: error processing package lxc (--configure):
subprocess installed post-installation sc
Please can you run 'apport-collect 1376283' (ideally when your system is
experiencing the issue).
Also, assuming you have not created any jobs yourself that might contain
confidential information (?), it would be extremely useful if you could
run the following when experiencing the problem and att
It sounds like you may have modified files below /etc/initramfs-tools/
and/or /usr/share/initramfs-tools/, or created additional scripts that
are somehow modifying the boot path. Further, I think you need to
understand why single is being specified on the boot command-line as
that is non-standard.
@Fabian - thanks for reporting but we need a lot more detail before we
can get to the bottom of this (ps output, strace [you need to install it
in dev mode], etc).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubu
This almost sounds like bug 1235649, but unlikely given that the
upstart-udev-bridge uses the correct NIH D-Bus calls.
I suspect the reason for the memory growth is that the events that are
being created cannot be destroyed until some other job has finished with
them. Once that happens, memory wil
*** This bug is a duplicate of bug 1198180 ***
https://bugs.launchpad.net/bugs/1198180
** This bug has been marked a duplicate of bug 1198180
possible leak in upstart 1.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
With your cursor on "Ubuntu, with Linux 3.16.0-18-generic (recovery
mode)", press 'e' and you should see 'recovery' specified somewhere on
the line that starts 'linux'. If not, your grub config is incorrect for
some reason.
To test if recovery mode works, again having pressed 'e', remove
'single'
Your cmdline shows that you are actually in single-user-mode, not
recovery mode. On a standard system, selecting "recovery mode" from the
grub boot menu will add 'recovery' to the boot command line, which will
trigger recovery mode to be started.
--
You received this bug notification because you
> UPSTART_EVENTS=runlevel
> UPSTART_INSTANCE=
> UPSTART_JOB=rcS
This is the cause of your problem - you are not actually in recovery mode. What
is your /proc/cmdline? Have you modified /etc/default/grub or any of the
initramfs configuration?
--
You received this bug notification because you are
@elfy - is plymouth is still crashing for you?
$ sudo grep SEGV /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into gra
1 - 100 of 217 matches
Mail list logo
