Public bug reported:
libvirt by default disables IPv6 as a result of this patch:
https://bugzilla.redhat.com/attachment.cgi?id=355689action=diff
This is incorrect behaviour. IPv6 should never be disabled by default,
and the need for IPv6–enabled software grows greater every day.
Currently,
Public bug reported:
Binary package hint: postfix
This response occurs now after all updates. Originally started after
SYNAPTIC requested some updates. Included in these was some new
additions ie including Google Chrome something about mailx. I had
already installed Google Chrome beta from the
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/39851792/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39851793/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/39851794/Dmesg.txt
** Attachment
** Patch added: debdiff which fixes aforementioned problem
http://launchpadlibrarian.net/39851835/libvirt-dont-disable-ipv6.lp528934.1.debdiff
** Summary changed:
- IPv6 shouldn’t be disabled by default
+ IPv6 shouldn’t be disabled by default in libvirt
--
IPv6 shouldn’t be disabled by
The initial bug report was associated with the I386 architecture. The
same thing happened on my ADM 64bit system.
--
package mysql-server-5.1 5.1.37-1ubuntu5.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
I decided to up the level of input. Please persevere.
ide...@karmic:~$ sudo rm /var/run/libvirtd.pid
ide...@karmic:~$ sudo gdb libvirtd
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is
** Summary changed:
- qemu-arm-static fails installing mono assemblies if /proc is mounted in the
chroot
+ mono assertion failure under qemu-arm
(ERROR:mini-arm.c:2063:arm_patch_general: assertion failed: (thumb_supported))
--
mono assertion failure under qemu-arm
Aha, I think I understand why ...
During the CLC install, I think the user is prompted for eucalyptus
/cloud-address (if it exists), and if the user leaves it blank (and none
is detected on the network), then the installer suggests installing this
machine as the CLC. Hence,
Public bug reported:
Ubuntu 9.10 - sudo apt-get upgradegives the following:
x...@x:~$ sudo apt-get upgrade
[sudo] password for x:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
mysql-server-5.1
1
** Attachment added: .etc.apparmor.d.usr.sbin.mysqld.txt
http://launchpadlibrarian.net/39855316/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39855317/Dependencies.txt
** Attachment added: Dmesg.txt
Public bug reported:
Binary package hint: qemu-kvm
qemu should emulate /proc/cpuinfo contents as some apps parse it to find
out which CPU they are running on.
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
Should emulate /proc/cpuinfo
Attaching /var/log/installer/syslog from my CC/SC install.
Search this file for 10.1.1.71 (the address of the CLC) and you'll see
that eucalyptus/cloud-address is set to 10.1.1.71:8773, at least for a
bit.
Maybe it's set correctly in the installer environment but that doesn't
get propagated to
Public bug reported:
This bug does not present a good initial experience to UEC new commers:
- When running the first instance, downloading the default Ubuntu 9.10
image from the Image Proxy, and try to simply launch it with all default
settings, fails to run the instance.
It seems the disk
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Adding an upstream task.
Anthony will be able to tell us if this is possible, and why
/proc/cpuinfo is structured the way it currently is in QEMU.
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Wishlist
** Changed
Just out of curiosity why does knowing about a fix preclude one from
applying the fix? What Chuck wrote fixes this error but that should be
handled automatically by the package installer script and not have to be
done manually by a user.
--
package samba-common 2:3.4.0-3ubuntu5.4 failed to
Public bug reported:
was setting up git
ProblemType: Package
AptOrdering:
openssh-server: Configure
python-setuptools: Configure
gitosis: Configure
Architecture: i386
Date: Sat Feb 27 15:27:09 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39862292/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/39862293/Dmesg.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/39862294/DpkgTerminalLog.gz
--
package
Configuration file handling is quite complex. Basically if the user
removes a configuration file, the package shouldn't reinstall it by
itself... That's why the package only suggests appropriate action.
More details at:
http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
--
package
I don't know what is meant by should emulate /proc/cpuinfo. Can you
please be more specific?
NB, the default CPU that is exposed is a generic one which allows for
maximum portability with respect to live migration. You can use the
'-cpu host' option to expose the underlying host CPU although
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Tags added: karmic
--
Anonymous ftp not disabled by default
https://bugs.launchpad.net/bugs/528860
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
It seems like the downloaded deb is corrupted. This could be a filesystem issue
or an aborted download. Please perform the following in a terminal:
$ sudo touch /forcefsck
$ sudo reboot
... wait while computer reboots, then login. then open a terminal and run these:
$ sudo apt-get clean
Now run
Public bug reported:
Binary package hint: samba
/etc/logrotate.d/samba produces error output, because the smbd stanza
calls 'invoke-rc.d --quiet samba reload /dev/null' in a postrotate
stanza (no stderr redirection, nor should there be). This should be
updated to use Upstart's facilities. I
I can confirm this ... but this error appeared in the system where IPv6
was disabled in the kernel. In a fresh installation, this error does not
occur.
** Changed in: openssh (Ubuntu)
Status: Incomplete = Confirmed
--
X11 forwarding via SSH does not work after upgrade to karmic
Public bug reported:
Binary package hint: mailman
mailman 2.1.12
postfix 2.6.5
ubuntu 9.10/karmic
setup according to the instructions in postfix-to-mailman.py.
when postfix recipient_delimiter=-, the 'user' gets passed to postfix-
to-mailman.py with the trailing -xxx removed. mail to
26 matches
Mail list logo
