11.04 is EOL'd, so marking as invalid.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/789351
Title:
UEC c
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to hv-kvp-daemon-init in Ubuntu.
https://bugs.launchpad.net/bugs/1078106
Title:
[MIR] hv-kvp-daemon-init
To mana
Marking as fix released. Fix went out with 13.10.
** Changed in: hv-kvp-daemon-init (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to hv-kvp-daemon-init in Ubuntu.
https://bugs.launch
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
** Changed in: apache2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1232469
I can reproduce this on Debian sid. Somehow openssl's int_free_ex_data()
calls a free_func that points into nirvana. I guess this may be due to
all the libraries being loaded, unloaded and then loaded again during
apache config parsing. Some library using ssl may do the wrong thing
during unloading
I agree that the postinst is a better place than the init script to run
"resolvconf -u".
I'm not sure that it should be conditional on IGNORE_RESOLVCONF though -
given that the update script will be run next time anything touches
resolvconf, what's to be gained by not running it in the postinst? A
** Branch linked: lp:~philip-g-potter/dnsmasq/update-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1247803
Title:
dnsmasq temporarily breaks DNS resolution when starting
My Saucy dom0 is also affected by this. I wasn't able to get the dmesg
in text but I attached a picture of it.
The problem seems to be this:
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Then the SATA link back down a on speed (6 -> 3 Gbps) and the same
o
Here is the dmesg of the *non dom0* kernel that boots properly.
** Attachment added: "Non dom0 dmesg"
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1127214/+attachment/3903963/+files/non-dom0-dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xen (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xen in Ubuntu.
https://bugs.launchpad.net/bugs/1127214
T
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
https://bugs.launchpad.net/bugs/1249588
Title:
package freeradius-krb5 2.1.12+dfsg-1.2ubuntu5 failed to
install/upgrade: su
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
https://bugs.launchpad.net/bugs/1249587
Title:
package freeradius-ldap 2.1.12+dfsg-1.2ubuntu5 failed to
install/upgrade: su
Public bug reported:
Setting up freeradius-krb5 (2.1.12+dfsg-1.2ubuntu5) ...
initctl: Unknown job: freeradius
reload: Unknown job: freeradius
invoke-rc.d: initscript freeradius, action "force-reload" failed.
dpkg: error processing freeradius-krb5 (--configure):
subprocess installed post-installat
Public bug reported:
Setting up freeradius-krb5 (2.1.12+dfsg-1.2ubuntu5) ...
initctl: Unknown job: freeradius
reload: Unknown job: freeradius
invoke-rc.d: initscript freeradius, action "force-reload" failed.
dpkg: error processing freeradius-krb5 (--configure):
subprocess installed post-installat
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/109157
15 matches
Mail list logo
