Public bug reported:
I have a local APT repository with a non-lowercase suite identifier.
apt-add-repository always forces it into lowercase, which causes apt to
emit warnings when it notices the mismatch:
$ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
Repository: 'deb
We've been running Sergio's exim 4.95-4ubuntu3~ppa2 for 27 hours so far
with no segfaults (previously it was segfaulting every few minutes) --
looks like the bug is fixed with those patches; thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Sergio, unfortunately your patched package does not fix the problem
-- we still see segfaults.
From the upstream discussion, I think we may need this commit as well:
https://git.exim.org/exim.git/commitdiff/8c74b00980bc7e3e479e8dfcd7c0008b2ac3f543
--
You received this bug notification
@tobhe Thanks for looking into this. However that upstream bug was
apparently fixed in GnuTLS 3.7.4; I just tried libgnutls30
3.7.4-2ubuntu1 from kinetic and I still see these crashes in exim4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer
+ Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed:
We are experiencing segfaults in exim since upgrading from impish
(4.94.2-7ubuntu2 with libgnutls30
A similar/identical issue appears to have been discussed briefly on the
Exim list:
https://lists.exim.org/lurker/message/20211008.224037.c1fee944.gl.html
They suggest that it may be a GnuTLS bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
We are experiencing segfaults in exim since upgrading from impish
(4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy
(4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in
_gnutls_trust_list_get_issuer, seemingly in the sender verify callout
during message submission.
I'm not convinced that CVE-2021-20230 is the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847275
Title:
stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS
vulnerability
xe-guest-utilities is the Xen equivalent to open-vm-tools which is still
in Ubuntu to support VMware.
Though xe-guest-utilities may have been added to Ubuntu for one
particular cloud, it is needed on all installations of Ubuntu in VMs
running on Citrix Hypervisor / XenServer, or on XCP-ng etc..
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939157
Title:
HWE kernels: NFSv4.1 NULL pointer dereference
To
Public bug reported:
Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes
(in this case with a NetApp filer mounted):
[ 266.199481] BUG: kernel NULL pointer dereference, address:
[ 266.199495] #PF: supervisor read access in kernel mode
[ 266.199500] #PF:
sshguard in Ubuntu 18.04 is still largely nonfunctional. Is the
relevant change likely to ever be backported to 18.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859809
Title:
sshguard <2.1.0
None of the machines I've upgraded to focal from bionic have a symlink
in /sbin/iptables.
$ namei -l /sbin/iptables
f: /sbin/iptables
drwxr-xr-x root root /
drwxr-xr-x root root sbin
iptables - No such file or directory
However you're right that a fresh install does have
Public bug reported:
On focal, I cannot reload charybdis from the init script (or from
'service' or 'systemctl'):
$ sudo SYSTEMCTL_SKIP_REDIRECT=1 bash -x /etc/init.d/charybdis reload
(...)
+ start-stop-daemon --stop --signal 1 --quiet --pidfile
/var/run/charybdis/ircd.pid
start-stop-daemon:
Public bug reported:
I observe that sshguard 1.7.1-1 in bionic doesn't block SSH bruteforce
attacks which are trying to log in as nonexistent accounts.
Whilst it blocks attacks which result in auth.log messages like:
Jan 15 08:51:19 io sshd[18965]: Failed password for root from 223.223.200.14
Not attaching logs since I can't boot the affected kernels, and this is
a packaging issue.
** 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.
Public bug reported:
In linux-modules-5.3.0-19-generic and earlier, on bionic, modules were
signed (note "signat: PKCS#7"):
$ modinfo /lib/modules/5.3.0-19-generic/kernel/arch/x86/kernel/cpuid.ko
filename: /lib/modules/5.3.0-19-generic/kernel/arch/x86/kernel/cpuid.ko
license:GPL
Hmm, good question. 1.1.1 was pushed to bionic in June? Unfortunately
I don't think I have syslog going back that far on any affected machine.
I only recall this problem happening in the last few months.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: stunnel4 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847275
Title:
stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS
$ stunnel4 -v
[ ] Clients allowed=500
[.] stunnel 5.44 on x86_64-pc-linux-gnu platform
[.] Compiled with OpenSSL 1.1.0g 2 Nov 2017
[.] Running with OpenSSL 1.1.1 11 Sep 2018
[.] Update OpenSSL shared libraries or rebuild stunnel
[.] Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD
*** This bug is a security vulnerability ***
Public security bug reported:
On multiple machines running Ubuntu 18.04 (stunnel4 3:5.44-1ubuntu3), I
am experiencing stunnel crashes seemingly caused by an attacker sending
an invalid handshake of some sort.
Aug 23 14:23:23 callisto stunnel[6302]:
(Report made public since it's being actively exploited.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847275
Title:
stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS
vulnerability
Any progress on this? This is a serious regression for us which makes
preseed substantially less functional in bionic...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses
...Indeed Debian just published roundcube 1.3.6+dfsg.1-1 which drops the
php-mcrypt dependency. roundcube could now be copied back to Ubuntu as-
is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
roundcube does not in fact need mcrypt since version 1.2
(https://github.com/roundcube/roundcubemail/issues/5780). That the
Debian package still depends on php-mcrypt is probably a mistake.
Too late to reintroduce roundcube, minus this dependency?
** Bug watch added:
Debian has accepted my patch into netcfg 1.142 -- please would someone
sync it?
It would be great if this could also be SRU'd into (at least) xenial, as
on our network the bug causes the xenial installer to set a nonsensical
and misleading hostname for the installed system.
--
You received this
** Bug watch added: Debian Bug tracker #862745
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862745
** Also affects: netcfg (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862745
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Furthermore, arguably every RPC service (rpc-statd.service, nfs-
mountd.service, etc.) should explicitly have
BindsTo=rpcbind.service
After=rpcbind.service
because they literally are bound to rpcbind. If rpcbind is
stopped/restarted, every RPC service must also be stopped/restarted so
as
Thanks, Rafael -- I'll put together an environment in which to test the
packages (I'd rather not reboot my live NFS servers).
However, I think nfs-mountd.service still needs tweaking. rpc.mountd
(if using NFSv2 or v3) needs to communicate with rpcbind on startup to
register services. Currently
This seems to be fixed in yakkety, but the crash still exists in xenial
-- any chance that this patch could be applied there too?
It's trivial to exploit -- anyone with access to open TCP connections to
a charybdis 3.5.0 SSL server can crash the ssld.
--
You received this bug notification
Public bug reported:
$ dpkg --status xenstore-utils | grep ^Version:
Version: 4.6.0-1ubuntu4.1
$ ls -l /usr/bin/xenstore-*
-rwxr-xr-x 1 root root 14132 Jun 14 10:33 /usr/bin/xenstore-chmod
-rwxr-xr-x 1 root root 14132 Jun 14 10:33 /usr/bin/xenstore-exists
-rwxr-xr-x 1 root root 14132 Jun 14 10:33
It appears that nfs-mountd.service is missing dependencies:
Wants=rpcbind.service
After=rpcbind.service
(as hinted above in comment 3, but we need After= too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "autoconfig-ntp-typo.diff"
https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1614514/+attachment/4723526/+files/autoconfig-ntp-typo.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The cause: a typo in autoconfig.c causing a buffer overflow into another
field of the netcfg_interface struct. Patch coming up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614514
Title:
netcfg
(This behaviour observed both on the Xenial server ISO and on today's
daily Yakkety server ISO.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614514
Title:
netcfg defaults hostname to
Public bug reported:
When prompted for a hostname during installation, on my network the
default offered is always our second NTP server's IPv6 address, which it
received via stateless DHCPv6. netcfg seems to be using the wrong field
as a hostname, in the absence of an explicit DHCP-provided
Verified fixed in:
wily-proposed: linux-image-4.2.0-32-generic:amd64 4.2.0-32.37
vivid-propsed: linux-image-3.19.0-53-generic:amd64 3.19.0-53.59
(Note: the vivid-proposed kernel does run into another bug on Xen
migrate which can cause the VM to freeze, but that is unrelated and is
not a
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542941
Title:
Regression: problems migrating recent wily/vivid Xen
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542941
Title:
Regression: problems migrating recent wily/vivid Xen VMs
Apologies for the confusion; I had the right commit ID but pasted the
wrong description. Now fixed, I think!
** Description changed:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the
That's the patch which *introduces* the regression.
The missing one is 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542941
Title:
Regression: problems
Public bug reported:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the underlying target dom0 (migrating a
64-bit domU involves a 1GB malloc in dom0, as well as a lot of
unnecessary work).
** 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/1542941
Title:
Regression: problems migrating recent wily/vivid Xen VMs due to
And here's the patch in debdiff form, for convenience.
** Patch added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+attachment/4505875/+files/autofs_lookup_ldap_crash.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
And here's the patch in debdiff form, for convenience.
** Patch added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1503034/+attachment/4505875/+files/autofs_lookup_ldap_crash.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is a regression due to recent (upstream?) refactoring of the
lookup_ldap module's lookup_init function (modules/lookup_ldap.c).
Nothing has initialised the config cache in lib/defaults.c before the
call to defaults_get_ldap_timeout on line 1668.
Previously, this module's first call to
This is a regression due to recent (upstream?) refactoring of the
lookup_ldap module's lookup_init function (modules/lookup_ldap.c).
Nothing has initialised the config cache in lib/defaults.c before the
call to defaults_get_ldap_timeout on line 1668.
Previously, this module's first call to
Public bug reported:
systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in
the absence of other configured DNS servers.
systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
installed by default and will behave in this way if enabled by the user.
$ cat
There's a race in chvt (see my comment at
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/comments/4)
which may be to blame. I suspect something on my system (Nvidia
driver?) is almost always winning this race, so chvt almost always
blocks and I can't suspend.
Perhaps pm-utils should
chvt makes two ioctl calls, one to change the VT and one to wait for the
new VT to become active. There's a race condition here; if something
changes the VT back before the second ioctl, chvt will block
indefinitely (or until something else changes to the correct VT).
--
You received this bug
There's a race in chvt (see my comment at
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/comments/4)
which may be to blame. I suspect something on my system (Nvidia
driver?) is almost always winning this race, so chvt almost always
blocks and I can't suspend.
Perhaps pm-utils should
Would someone mind explaining, please, why this remote code execution
vulnerability was only just now fixed in precise despite being fixed
upstream in January?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is an update planned for 13.04?
http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-0393.html
et al state ignored (reached end-of-life) which is surprising given
13.04's end-of-life is still a week away (27 Jan:
https://lists.ubuntu.com/archives/ubuntu-security-
Is an update planned for 13.04?
http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-0393.html
et al state ignored (reached end-of-life) which is surprising given
13.04's end-of-life is still a week away (27 Jan:
https://lists.ubuntu.com/archives/ubuntu-security-
Public bug reported:
Setting up atftpd (0.7.git20120829-1) ...
*** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script should be fixed to not stop debconf before calling ucf,
On second thought, this may be a rlinetd bug: perhaps update-inetd
should call ucf with --debconf-ok, so that it can be used from
maintainer scripts?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
cron sends mail with the following header:
Content-Type: text/plain; charset=ANSI_X3.4-1968
This is a non-canonical alias for the preferred charset name us-ascii
[1]. A previous changelog entry (for 3.0pl1-101) states that this was
previously fixed:
- Do not use
** Patch added: debdiff against precise
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1169160/+attachment/3644704/+files/cron-mime-charset.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching a debdiff.
I'm not convinced upstream is active as the last release was in 1999,
but I'll contact them regardless.
** Patch added: debdiff
https://bugs.launchpad.net/ubuntu/+source/cfingerd/+bug/1104425/+attachment/3520900/+files/cfingerd.debdiff
** Changed in: cfingerd (Ubuntu)
Whilst that does sound problematic, surely that is a separate issue
entirely? This bug is about the update manager hiding apt-listchanges;
your bug seems to imply that apt-listchanges shouldn't use less without
some restrictions in place.
--
You received this bug notification because you are a
Torsten, this is a XenServer bug and not an Ubuntu bug. No current
release of XenServer is capable of running guests with recent Linux
kernels. A fix is (still) pending from Citrix. If you want an
unofficial fix (a replacement kernel for XenServer dom0, very
unsupported) contact me privately.
Is there any chance this patch could also be applied to release-
upgrader-apt in lucid? I'm encountering the same bug on release upgrade
from lucid to precise (with the aforementioned custom package
installed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Relevant citation is http://tools.ietf.org/html/rfc3442#page-4, Local
subnet routes -- this behaviour should work and this script currently
does not correctly implement RFC 3442.
The Debian bug -- http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=521024 -- has a slightly neater patch (which is
I've been in touch with Mathieu Trudel-Lapierre, the original author of
the Ubuntu patch I linked above, who tells me that his patch was
rejected upstream as Dave Miller does not want these semantics for 'all'
sysctls (and apparently the documentation, rather than the
implementation, is wrong):
Kernel packages with my patch applied are available in this PPA:
https://launchpad.net/~malcscott/+archive/lp994931
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
Altering use_tempaddr
Alternatively: here's my attempt at fixing the IPv6 Privacy
implementation. It could do with code review as I'm not absolutely sure
I've got the locking right (although I think I have!).
** Patch added: fixed IPv6 Privacy implementation
jsalisbury: problem is, simply reverting that commit leaves us with IPv6
Privacy not working at all, and it's on by default now. (There is at
least one upstream bug: e.g.
https://bugzilla.kernel.org/show_bug.cgi?id=42855)
I should add that I've tested my patch for a few days and it seems to
work
@jsalisbury
I would like to submit this upstream, although my patch is just fixing
the previous Ubuntu-specific commit I linked above. Do you know whether
that has already been sent upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Colan: that's a different bug; please file a separate report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995195
Title:
apt-listchanges causes update-manager to appear to hang
To manage
The Debian bug is mainly talking about a different issue, and merely
mentions the screen-profiles divert as the cause. I do not think this
bug should be flagged 'incomplete'.
** Changed in: screen (Debian)
Importance: Unknown = Undecided
** Changed in: screen (Debian)
Status:
ISO9660 Joliet extensions have a filename length limit of 64 characters
(http://en.wikipedia.org/wiki/Joliet_%28file_system%29) which is
probably the cause. Should the CDs be built with Rock Ridge extensions
as well to increase the limit to 255
(http://en.wikipedia.org/wiki/Rock_Ridge)?
--
You
Public bug reported:
If apt-listchanges is configured to show package changelogs, update-
manager displays them in 'less' in a hidden terminal which waits for the
user to quit and continue. There is no indication in update-manager
that something off-screen is waiting for input. The only status
** Attachment added: Screenshot 1: apt-listchanges is waiting for input, but
there is no indication of this
https://bugs.launchpad.net/bugs/995195/+attachment/3132153/+files/screenshot1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Screenshot 2: the situation is revealed after clicking
'Details'
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/995195/+attachment/3132160/+files/screenshot2.png
** Also affects: apt-listchanges (Ubuntu)
Importance: Undecided
Status: New
--
You
apport information
** Tags added: apport-collected
** Description changed:
$ uname -a
Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59
UTC 2012 i686 i686 i386 GNU/Linux
$ sysctl net.ipv6.conf.eth2.use_tempaddr
net.ipv6.conf.eth2.use_tempaddr = 2
# (as
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/994931/+attachment/3132522/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/994931/+attachment/3132523/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/994931/+attachment/3132524/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/994931/+attachment/3132525/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994931
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/994931/+attachment/3132526/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug
For what it's worth, I've improved my patch -- the previous one, with no
timeout whatsoever, caused periodic checks (the calls to DoTimer())
which are intended to be run once per second to be delayed on quiet
servers. The new one uses a 1-second timeout.
It's a shame hybserv has been dropped --
*** This bug is a security vulnerability ***
Public security bug reported:
Network Manager in Precise uses a local forwarding DNS server (dnsmasq).
This does not perform DNSSEC validation, although it is configured to
proxy the DNSSEC validation result from the upstream server, for which
the
As per bug #978995 this happens when an older mysql-server-* package,
e.g. mysql-server-5.1, is purged post-upgrade.
The problem seems to be in dh_apparmor, which added the following to
mysql-server-5.1.postrm:
# Automatically added by dh_apparmor
if [ $1 = purge ]; then
rm -f
Public bug reported:
$ uname -a
Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 UTC
2012 i686 i686 i386 GNU/Linux
$ sysctl net.ipv6.conf.eth2.use_tempaddr
net.ipv6.conf.eth2.use_tempaddr = 2
# (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04)
# Add a
The cuplrit is likely to be lines 4355..4359 of net/ipv6/addrconf.c,
try to bring down and back up the interface to get new temporary
addresses created -- this has unwanted side-effects. This seems to be
Ubuntu-specific code introduced in http://kernel.ubuntu.com/git?p=ubuntu
/ubuntu-
Many thanks for getting this fix into precise quickly! Very much
appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985852
Title:
libapt-pkg regression: infinite loop on processing certain
Public bug reported:
Summary: a typo in apt-pkg/packagemanager.cc means that certain Pre-
Depends cannot be processed, causing libapt-pkg to hang.
Details: I have a custom package whose control file contains
Pre-Depends: grub-pc | grub
When I attempt to install this on a system which has grub
** Patch added: debdiff
https://bugs.launchpad.net/bugs/985852/+attachment/3094503/+files/apt.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985852
Title:
libapt-pkg regression: infinite
I should have said: this bug is in apt 0.8.16~exp12ubuntu9 in precise.
This behaviour did not occur in oneiric or any other previous version I
have used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The release incorporating this fix is due for release around late July /
early August. The only workaround I know for now is to install a
patched kernel in the XenServer dom0. I have one and you may contact me
by email if you would like a copy, but bear in mind that it is very much
not supported
I should clarify that the timeframe for the XenServer release (6.1) I
gave above is an unofficial, unauthoritative estimate and subject to
alteration by Citrix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is more serious than I thought. It appears that because of the
aforementioned apt bug (it sometimes never exits when invoked from one
of the cron.daily scripts), anacron has not run any jobs on my system
for the past month.
This is not a good failure mode. It would be much more safe
This turned out to be a XenServer bug related to the interaction between
blkback and barriers; my contact at Citrix has produced a dom0 kernel
patch which fixes the issue. I'm told the fix will be incorporated in
the next point release of XenServer.
** Changed in: linux (Ubuntu)
Status:
This bug is still present in the 3.2.2-030202 mainline build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage notifications about
This bug is also still present in the 3.3.0-030300rc1 mainline build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors prevent boot in domU
To manage
For the record I've just tested linux-
image-3.2.0-030200rc2-generic_3.2.0-030200rc2.20151435 and the bug
is still present. This is still on XenServer 5.6 SP2; I'll try to test
on a XS 6 install later. (Lucid does work on both versions; the problem
is only with Oneiric.)
Stefan: I hadn't
The bug also occurs on XenServer 6 (with Oneiric's kernel, on NFS-backed
storage).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824089
Title:
Xen blkfront i/o errors on NFS-backed disks prevent
Correction -- the bug DOES *sometimes* occur if the root filesystem is
on local storage. On local storage, the bug has so far occurred on
three out of six boot attempts. I have yet to see a successful boot on
NFS storage.
** Summary changed:
- Xen blkfront i/o errors on NFS-backed disks
For the record, this bug is still present in lucid, although it seems to
have been fixed in oneiric (and possibly some intermediate releases).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/364094
Public bug reported:
When upgrading to oneiric with sane-utils and rlinetd installed:
Setting up sane-utils (1.0.22-2ubuntu2) ...
*** WARNING: ucf was run from a maintainer script that uses debconf, but
the script did not pass --debconf-ok to ucf. The maintainer
script
1 - 100 of 229 matches
Mail list logo
