Public bug reported:
Release: Ubuntu 9.04/Jaunty
Arch: x86_64
Packages:
python-vm-builder: 0.10-0ubuntu2
debootstrap: 1.0.12
console-setup: 1.28ubuntu8
upstart: 0.3.9-8
Running vmbuilder on a text console to build a kvm based VM causes
gettys to stop respawning. Each getty needs to be restart
Update: Confirmed using a new machine that has X installed and a brand
new install of vmbuilder (on same new machine) that when vmbuilder is
run in an xterm that text consoles no longer respawn.
Note: In case it wasn't apparent previously, it's only during the build
process this happens and only o
Update: This can be reproduced without the use of vmbuilder.
I have not as yet tracked down which command run by debootsrap causes
the problem.
Running the following commands reproduce the same behaviour:
mkdir /test-root
debootstrap --arch=amd64 jaunty /test-root http://archive.ubuntu.com/ubu
Q: Is there any way I can add additional debugging to debootstrap (eg:
pausing between installed packages, more verbose output, etc) so I can
possibly track down where this is happening? I am aware that this may
not even be a problem of debootstrap, but a problem caused by a package
in the chroot c
Sorry I've been busy with things like work and looking for a place to
live lately.
Upgraded to Dapper. Same result as Breezy.
It doesn't matter if the device has RAW files on it or not. It's just buggy at
working. Sometimes it works, more often than not, it doesn't. Same is present
using gphot
Public bug reported:
Binary package hint: linux-image-2.6.15-26-686
Bug is also described on the Ubuntu forums at:
http://ubuntuforums.org/showthread.php?t=187770
I have a D-Link DGE-530T that isn't detected by Ubuntu Dapper using the
kernel linux-image-2.6.15-26-686.
Basically, it seems this w
Good to see that a fix is committed. If you need someone to test this,
just point me at packages.
--
Mis/Non detection of D-Link DGE-530T
https://launchpad.net/bugs/55847
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Might be related, hence why I'm not opening a new bug:
Xerox Tektronix Phaser6250 with inbuilt IPP support. Used to work fine
in Breezy, no longer works in Dapper.
Tried:
Deleting and manually adding all printers (Printer does not support browsing)
Uninstalling cupsys (apt-get --purge remove cu
Public bug reported:
Gigabyte 8S661FXMP-RZ (Socket 478 P4 board with SiS661FX and SiS 964
Chipsets) fails to reboot after a reboot is issued using the Ctrl-Alt-
Del hook, invoked via "sudo reboot" or after Alt-SysRq-B is issued
(reboot). The machine appears to go through halting processes fine the
Please ignore. I now have an identical board running the same revision
of Ubuntu which does reboot, but which has a faulty primary Serial ATA
controller. This seems to be a hardware quality issue from this
manufacturer. Please close this bug.
--
SiS 661FX chipset board refuses to "reboot"
https:/
I'd sort of given up on this at the time and just lived with the erratic
behaviour, but since you asked
Further notes:
Tried on a seperate box running Dapper: Same issues (so not the USB port).
Upgraded seperate box to Edgy: Bug not present. (Fixed!)
Tried on another seperate box that is
I too have come across this issue.
In my case, it appears to be related to br0 (my bridge) not becoming
live in time.
As a temp solution, I found that simply adding a 'sleep 4' in the init
script (just before it runs libvirtd) alleviates the issue. This gives
the bridge enough time to become acti
Second file attached.
** Attachment added: "msgs2"
http://launchpadlibrarian.net/39289025/msgs2
--
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Got this today (18/Feb/2010) as well.
Note: Using 'do-release-upgrade -d' to do the upgrade.
--
cyclic dependency between mountall and libplymouth
https://bugs.launchpad.net/bugs/514012
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Manually worked around this by doing the following AFTER receiving the
error from 'do-release-upgrade -d':
1. Run: 'dpkg -i /var/cache/apt/archives/libc6*
/var/cache/apt/archives/libc-bin*' (installing libc6 and libc-bin).
2. Re-run: 'do-release-upgrade -d'
Note: Thanks to a kindly soul on #ubun
Upgraded the libvirt host to lucid (libvirt-bin 0.7.5-5ubuntu7). Since
doing so, I have not been able to replicate the issue with guests not
starting at boot due to the bridge coming up late (after some/all of the
guests have started). Will continue to do more testing.
Notes:
1. eth0 appears to be
As this affects me too...
Upgraded a server install to lucid from karmic today, and plymouth
(0.8.0~-10ubuntu1) was installed during the upgrade process. Upgrade was
performed using 'do-release-upgrade -d'.
As such, the comment from scott makes no sense unless plymouth has been
decided to be remo
I've since moved my test systems to later version of Ubuntu (both were
jaunty, now one is lucid and the other is karmic) since this bug entry
was created.
However, if testing any of this on lucid or karmic is worthwhile, let me
know what needs testing and I'll get to it.
--
building vm image on
Upgraded one of the guests to lucid with no issues. All guests still
start fine.
As this is a test machine, I can always create more VM's, if that seems
like a good idea?
Suggestions for more tests to perform welcome.
--
autostart almost always fails on boot time host
https://bugs.launchpad.net
19 matches
Mail list logo
