Re #27, removing -nographic still causes the same lockup for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside double nested kvm VM
Latest kernel panic (from 2nd-level guest) using following kernel
versions:
host: 3.11.0-1-generic (-2 causes problems for my graphics hardware atm)
1st-level guest: 3.11.0-2-generic
2nd-level guest: 3.11.0-2-generic
** Attachment added: kvm.log
Latest kernel panic (from 2nd-level guest) using following kernel
versions:
host: 3.11.0-1-generic (-2 causes problems for my graphics hardware atm)
1st-level guest: 3.11.0-2-generic
2nd-level guest: 3.11.0-2-generic
** Attachment added: kvm.log
Now that 3.11 is out of proposed, we're seeing a different kernel
failure, starting with
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.11.0-2-generic
/boot/vmlinuz-3.11.0-2-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.0-2-generic
Found initrd image:
The kernel BUG: above happens when running bin/prepare-testbed -r saucy -d
i386 from lp:auto-package-testing in canonistack:
the kvm instance spins at ~200% CPU again.
I modified bin/prepare-testbed slightly to log the output of the vm and
disable byoubu. See attached.
** Patch added:
To recreate:
1) Follow instructions on internal wiki (page
InformationInfrastructure/IS/CanonicalOpenstack) to create a keypair.
2) Create an guest instance:
$ keyname=${USER}_lcy01
$ image=$(euca-describe-images|grep saucy|head -1|awk '{print $2}')
$ euca-run-instances -k $keyname -t m1.medium
Now that 3.11 is out of proposed, we're seeing a different kernel
failure, starting with
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.11.0-2-generic
/boot/vmlinuz-3.11.0-2-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.0-2-generic
Found initrd image:
The kernel BUG: above happens when running bin/prepare-testbed -r saucy -d
i386 from lp:auto-package-testing in canonistack:
the kvm instance spins at ~200% CPU again.
I modified bin/prepare-testbed slightly to log the output of the vm and
disable byoubu. See attached.
** Patch added:
To recreate:
1) Follow instructions on internal wiki (page
InformationInfrastructure/IS/CanonicalOpenstack) to create a keypair.
2) Create an guest instance:
$ keyname=${USER}_lcy01
$ image=$(euca-describe-images|grep saucy|head -1|awk '{print $2}')
$ euca-run-instances -k $keyname -t m1.medium
I got the panic again last night. This was running a 3.11 kernel for the
host, but of course the 1st and 2nd level guests were still running 3.10
as 3.11 is still in -proposed. So, although it's possible to get a test
run with (3.11, 3.10, 3.10) I really need to try running with (3.11,
3.11, 3.11)
I got the panic again last night. This was running a 3.11 kernel for the
host, but of course the 1st and 2nd level guests were still running 3.10
as 3.11 is still in -proposed. So, although it's possible to get a test
run with (3.11, 3.10, 3.10) I really need to try running with (3.11,
3.11, 3.11)
Testing with linux-image-3.11.0-0-generic from -proposed with nested=Y
in all 3 environments does appear to solve this issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Testing with linux-image-3.11.0-0-generic from -proposed with nested=Y
in all 3 environments does appear to solve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general
What we know so far:
- the issue is not related to cloud-init.
- the very high CPU load was atleast partly caused by byobu bug 1208853. To
disable byobu...
=== modified file 'bin/prepare-testbed'
--- bin/prepare-testbed 2013-08-06 08:05:16 +
+++ bin/prepare-testbed 2013-08-06 14:01:42 +
Fresh kernel panic from 2nd-level nested VM running with host, 1st level
and 2nd level all running with nested=1.
** Attachment added: kvm.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3763650/+files/kvm.log
--
You received this bug notification because you
What we know so far:
- the issue is not related to cloud-init.
- the very high CPU load was atleast partly caused by byobu bug 1208853. To
disable byobu...
=== modified file 'bin/prepare-testbed'
--- bin/prepare-testbed 2013-08-06 08:05:16 +
+++ bin/prepare-testbed 2013-08-06 14:01:42 +
Fresh kernel panic from 2nd-level nested VM running with host, 1st level
and 2nd level all running with nested=1.
** Attachment added: kvm.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3763650/+files/kvm.log
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside
High CPU may be cloud-init. Using todays server image, running 'prepare-
testbed' spins the CPU at 200%. The end of the log shows:
Aug 6 10:13:15 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running
config-package-update-upgrade-install using lock (FileLock using file
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside nested kvm VM
To
High CPU may be cloud-init. Using todays server image, running 'prepare-
testbed' spins the CPU at 200%. The end of the log shows:
Aug 6 10:13:15 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running
config-package-update-upgrade-install using lock (FileLock using file
Public bug reported:
Using recent server images (today, yesterday), byobu is spawning dozens
of byobu-status instances.
In an OpenStack environment, this caused the nested kvm instance to
consume 200% CPU and makes the system almost unusable.
Killing all byobu, byobu-status and tmux processes
Public bug reported:
Booting saucy under kvm and switching to tty1 results in the screen
going black once lightdm starts and this seems to also stop the user
switching vt's using ctrl-alt-fX.
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Attachment added:
Public bug reported:
Attempting to run apt-get in a nested vm hosted in OpenStack results in
a general protection fault in the kernel in the nested VM.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Attempting to repeat the dep8 test run in the same environment has so
far resulted in the qemu-kvm binary consuming 200% CPU (recreated on
multiple nodes).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
I'm suspecting an issue with nested=1... the nested VM does eventually
boot but it takes many minutes to do so. At this point, the cpu usage of
qemu-kvm drops to reasonable values. But if you ssh into the vm, the
usage jumps up to ~200% again.
To recreate:
$ sudo apt-get install -y genisoimage
** Attachment added: Another general protection fault panic
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1208455/+attachment/3761555/+files/kvm.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Kernel logs can be found on bug 1208509.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside nested kvm VM on
OpenStack
Note that #4 was taken from a local nested kvm environment (not
OpenStack).
** Summary changed:
- general protection fault running apt-get inside nested kvm VM on OpenStack
+ general protection fault running apt-get inside nested kvm VM
--
You received this bug notification because you are a
Hi Jan,
Thanks for reporting this issue. I think you are correct - nm looks like
the culprit. Re-assigning...
** Package changed: upstart (Ubuntu) = network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Attempting to run apt-get in a nested vm hosted in OpenStack results in
a general protection fault in the kernel in the nested VM.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Attempting to repeat the dep8 test run in the same environment has so
far resulted in the qemu-kvm binary consuming 200% CPU (recreated on
multiple nodes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm suspecting an issue with nested=1... the nested VM does eventually
boot but it takes many minutes to do so. At this point, the cpu usage of
qemu-kvm drops to reasonable values. But if you ssh into the vm, the
usage jumps up to ~200% again.
To recreate:
$ sudo apt-get install -y genisoimage
** Attachment added: Another general protection fault panic
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1208455/+attachment/3761555/+files/kvm.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kernel logs can be found on bug 1208509.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside nested kvm VM on
OpenStack
To manage
*** This bug is a duplicate of bug 1208455 ***
https://bugs.launchpad.net/bugs/1208455
Public bug reported:
Fighting with apport (bug 1208508). The attachments should really be
added to bug 1208455.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-6-generic
Note that #4 was taken from a local nested kvm environment (not
OpenStack).
** Summary changed:
- general protection fault running apt-get inside nested kvm VM on OpenStack
+ general protection fault running apt-get inside nested kvm VM
--
You received this bug notification because you are a
** Information type changed from Private to Public
** Branch linked: lp:~jamesodhunt/upstart/quiesce-cleanup-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205443
Title:
init crashed with
** Information type changed from Private to Public
** Branch linked: lp:~jamesodhunt/upstart/quiesce-cleanup-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1202287
Title:
init crashed with
Untested, but looks reasonable. However, note that you can now use the
Upstart apparmor profile rather than using the pre-start for that:
apparmor load /etc/apparmor.d/usr.sbin.mysqld
pre-start script
# ...
end script
--
You received this bug notification because you are a
Version 304_304.88-0ubuntu6 seemed to have introduced the problem, but
version 304.88-0ubuntu7 fixes the issue.
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
APT_LISTCHANGES_FRONTEND only works I'm guessing if apt-listchanges is
installed. I have now removed this package, but the behaviour is still
the same since apt now calls sensible-pager automatically.
A work-around for this issue is to set PAGER=cat to make changelog
viewing non-interactive
This looks like a recurrence of bug 525958 however, I have this issue on
cold boot - no suspend/resume involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203754
Title:
nvidia 304.88-0ubuntu6
** Changed in: upstart (Ubuntu)
Status: Triaged = 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/1163103
Title:
upstart file bridge: unable to write pid file
To manage
@Sworddragon - Thanks for reporting. This is in fact an innocuous
message: the upstart-dbus-bridge should not run at the system level. The
next update will remove the .conf file to make this message go away.
@r0tter77: this problem has nothing to do with the behaviour you
describe. Please raise a
xnox - could you take a look at establishing why upstart.maintscript
isn't doing what it should?
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Latest update to lightdm broke boot for me as ligthdm crashes on
startup.
dmesg shows:
[ 38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4
in libglib-2.0.so.0.3703.0[b746b000+102000]
[ 39.364988] init: lightdm main process (1621) killed by SEGV
** Changed in: lightdm (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203660
Title:
lightdm crashed with SIGSEGV in g_list_last()
To manage notifications
Public bug reported:
Patch attached.
NB: Also noticed that the bzr branch is showing as OUT-OF-DATE.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Attachment added: apport-upstart-bug.diff
Manually downloading the old revision and rebooting does resolve the
problem for me:
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/lightdm_1.7.4-0ubuntu1_i386.deb
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/liblightdm-gobject-1-0_1.7.4-0ubuntu1_i386.deb
$
Public bug reported:
The 3.10.0-4-generic update broke a few things for me:
1) IBM thinkpad acpi fan-control no longer works:
$ sudo modprobe thinkpad_acpi fan_control=1
ERROR: could not insert 'thinkpad_acpi': Unknown symbol in module, or unknown
parameter (see dmesg)
$ dmesg|grep -i
Public bug reported:
The latest nvidia update breaks X on my system:
[ 108.858] (II) Open ACPI successful (/var/run/acpid.socket)
[ 108.858] (II) APM registered successfully
[ 108.870] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 108.870] (EE) *** Aborting ***
[
Looks like this issue may in fact be bug 1203211.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203751
Title:
ibm fan control broken and iwlwifi no longer accepts 11n_disable
option
To manage
The default behaviour of the boot with this bug is that the greeter
never appears; you just see the Ubuntu pulsing plymouth theme.
However, the system has booted so you can switch to a text console
(control+alt+f1 for example), login and take remedial action as shown in
#6.
--
You received this
This is by design:
- http://upstart.ubuntu.com/cookbook/#symbolic-links-don-t-work-in-etc-init
- init(5) under RESTRICTIONS.
** Changed in: upstart (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: upstart
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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_supply-device-
This is rather an interesting one: we first added support for running
upstart as a non-priv user, we forced it to run in debug mode (since
debugging was the main reason for running init as a non-priv user). As
such, when you run init --user, you are automatically in debug mode
('initctl
** 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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_supply
** Changed in: upstart
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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_supply-device-
changed
Correction to the process above: a session only gets created when a job
is queried so a maintainer script is probably invoking
status/start/stop/restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~jamesodhunt/upstart/bug-1199778
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199778
Title:
upstart crashes if re-exec'ed with active chroot sessions
To manage notifications
Failure message, for reference:
conf.c:1510: Assertion failed in conf_source_deserialise_all:
NIH_LIST_EMPTY (conf_sources)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199778
Title:
upstart
of a better way to solve this problem, please jump in.
Kind regards,
James.
--
James Hunt
(*) - just like 'watchprop' does in the Android environment.
#upstart on freenode
http://upstart.ubuntu.com/cookbook
https://lists.ubuntu.com/mailman/listinfo/upstart
Public bug reported:
Problem affects both 1.9 and 1.9.1.
** Affects: upstart
Importance: High
Assignee: James Hunt (jamesodhunt)
Status: New
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart
Importance: Undecided = High
** 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/1199778
Title:
upstart crashes if re-exec'ed with active chroot sessions
To manage
Hi Brian,
If you use a glob pattern in FILE, the way to determine the name of the
matching file in the job is via the MATCH variable:
start on file FILE=/var/crash/*.crash EVENT=create
exec echo matching file was $MATCH
** Changed in: upstart
Status: New = Invalid
** Changed in:
Forgot to mention that this is documented in file-event(7).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199499
Title:
upstart file bridge sets FILE to glob pattern instead of specific file
To
This problem affects those systems hosting chroots but also affects
those with sbuild/pbuilder installed. The failure process is as follows:
- user builds a package in the sbuild/pbuilder env.
- upstart gets updated within the sbuild/pbuilder chroot as part of the package
build.
- as part of the
** Changed in: upstart
Status: In Progress = Fix Released
** Changed in: upstart (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/1188642
Title:
** Summary changed:
- Update to 1.9.1 causes system hang at configure
+ Update to 1.8-0ubuntu1.2 in raring causes system hang at configure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198649
** 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/1197529
Title:
upstart in saucy needs a build-depends
@Sworddragon - Thanks for reporting. Is this on a single system? Do you
just have a single instance of the /proc/self/fd/9 process?
Please can you run 'apport-collect 1197789' on an affected system and
follow the prompts to help debug this.
--
You received this bug notification because you are
Approximately how many running jobs do you have after you've created 40k
containers? If you stop all those network interfaces, is the memory
reclaimed?
Please provide further details so we can investigate more fully.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: upstart
Status: Fix Committed = 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/1197225
Title:
upstart-file-bridge assert failure: string.c:396: Assertion failed in
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Information type changed from Private to Public
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt
** 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/1197225
Title:
upstart-file-bridge assert failure: string.c:396: Assertion failed in
Public bug reported:
My machine was responding sluggishly. Top showed PID 1 consuming almost
70% CPU. The culprit seems to be the startpar-bridge job which had 2
running instances:
$ sudo initctl list|grep startpar
get_started is a job that also specifes 'start on started', so upstart
was chasing both jobs constantly: only 1 job can reasonably specify such
an unspecific start condition.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you
Does your system fail to boot or is it that you are simply unable to
login?
If it is failing to boot, please remove 'quiet' and 'splash' from your
kernel command-line and either attach a log of the console output, or
just attach a picture showing crash details.
--
You received this bug
14:41 Trevinho jodh: unfortunately I'm getting a black screen...
14:41 Trevinho jodh: also removing splash and quiet I'm getting a fast log,
then the screen gets blank
14:43 Trevinho (and nothing in /var/crash this time)
14:55 Trevinho jodh: I'm using the custom cmd line for
@regmka: Thanks very much for both reporting this issue and identifying
the issue! :-)
** Changed in: upstart
Status: New = In Progress
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: upstart
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/1190526
Title:
init crashed with SIGABRT in nih_discard()
To manage notifications about this
Just got this error when manually running apport-bug on 2 crash files
generated in a raring - saucy dist upgrade confirming #6. No apport
backtrace but apport shows the following in the terminal:
ERROR: error('unpack requires a bytes object of length 4',)
(apport-gtk:3903): Gtk-CRITICAL **:
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you
Hi Clint - thanks for reporting. This is an issue with the plymouth-
upstart-bridge which is part of the plymouth package.
** Package changed: upstart (Ubuntu) = plymouth (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Happened soon after a cold boot. I wonder if there is a way to detect
these sorts of bugs from userland (some sort of dmesg/syslog sniffer)
and prompt the user to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.30
Relevant chunk of dmesg attached.
** Attachment added: dmesg-bug.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180270/+attachment/3677120/+files/dmesg-bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the momentum
going so we can turn [2] into a wall of green^H^H^H^H^H err blue sky and
sunshine! :-)
Kind regards,
James.
--
James Hunt
#upstart on freenode
http://upstart.ubuntu.com/cookbook
https://lists.ubuntu.com/mailman/listinfo/upstart-devel
--
ubuntu-devel
On 13/05/13 13:59, Benjamin Drung wrote:
Am Montag, den 13.05.2013, 13:36 +0100 schrieb James Hunt:
Great to see all these new DEP-8 tests [1] appearing! Let's keep the momentum
going so we can turn [2] into a wall of green^H^H^H^H^H err blue sky and
sunshine! :-)
I found a bug: [1] and [2
Thanks Adam, however these diffs are making use of LSB functions (from
/lib/lsb/init-functions), but that script is not being sourced.
Using echo directly to stderr should be sufficient in this context (or
maybe defining a log_failure_msg() function locally to do that).
--
You received this bug
Public bug reported:
To recreate:
1) Select Welcome tab in QtCreator.
2) Select the Tutorials tab.
3) Select any non-video tutorial.
4) Observe how images are overlayed on the text, making the text mostly
illegible.
Expected outcome: text flows around images.
Actual outcome: image float over
shutdown now is supposed to switch to single-user mode (see bug
1065851).
reboot now is invalid - the shutdown command takes a time parameter
(such as now), but the reboot command does not (see the man page). By
specifying reboot now you are asking the system to reboot by running
the now
This is correct behaviour - shutdown now is supposed to switch to
single-user mode unless an explicit option has been set to specify an
alternative form of shutdown. What you probably meant to type was
shutdown -h now which will halt the system (and generally power it off
too).
The man page for
shutdown man page updated upstream to clarify behaviour.
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart
Importance: Undecided = Low
** Changed in: upstart
Status
at the sprint next week.
** Patch added: upstart-bug-1124384-minimal-fix.diff
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3654975/+files/upstart-bug-1124384-minimal-fix.diff
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt
Sorry - haven't been able to test all these kernels yet so will report
back when I've had a chance.
However, what I have discovered is that the bug has something to do with
the quiet and/or splash kernel options: I remove these so my init
menu works correctly. However, I've reverted back to stock
at the sprint next week.
** Patch added: upstart-bug-1124384-minimal-fix.diff
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3654975/+files/upstart-bug-1124384-minimal-fix.diff
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt
fwiw, just before the failed boot, the machine had forcibly shut itself
down as a result of the bug 751689.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172322
Title:
kernel panic on boot
To
Subsequent boot worked correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172322
Title:
kernel panic on boot
To manage notifications about this bug go to:
** Attachment added: IMG_0586.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172322/+attachment/3652371/+files/IMG_0586.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172322
Title:
701 - 800 of 2008 matches
Mail list logo
