https://launchpad.net/ubuntu/+source/openjdk-6/+publishinghistory
confirms that this would have been introduced into Precise on 2014-02-27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295987
Title:
Mailing list discussion:
http://comments.gmane.org/gmane.comp.java.openjdk.jdk6.devel/1114
cleaned up in openjdk7 amongst a much larger commit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295987
I'm currently running with the following patch (not entirely sure how
the packaging works and whether I've done this the right wy). Passes all
tests.
** Patch added: "Patch to ubuntu packaging"
https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1295987/+attachment/4040464/+files/zero-jdk
The above patch has a second instance of the same issue fixed. Mailing list
thread from upstream here:
http://mail.openjdk.java.net/pipermail/jdk6-dev/2014-March/003253.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Jamie: we've verified that the patch I applied *appears* to fix the bug
we are seeing. I say *appears* as the bug manifesting itself seems to be
a function of uninitialized values on the stack; on some runs it
explodes with leaking stuff straight away, other times it runs fine for
many many hours,
Yes , the version I tested (with my patch, as attached to this bug) has
both of those fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295987
Title:
openjdk6 regression causes finalizers never
Will do once they have finished building. Is there a link to the diff in
the mean time so I can check it against the one we've been using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295987
Title:
Jamie: thanks. They look good to me (from inspection of the diffs). Will
get these checked tomorrow once they have built. Normally our tests take
a couple of days to run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Robie: this is me poking you after a couple of weeks, as requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366174
Title:
apache2 SEGV with multiple SSL sites
To manage notifications about t
Robie: no apology needed, and yes I would be happy to check Vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366174
Title:
apache2 SEGV with multiple SSL sites
To manage notifications about th
I have attached a backport to 2.4.7 to this comment. This is a backport
of the backport to 2.4.x in upstream svn. More details in the commit
message.
This is a straight patch to the source (produced from git) rather than a
proper packaged up patch, if you see what I mean.
I've put this up on gith
I have added [Impact] and [Regression potential] sections.
Do the SRU requirements mean we need a patch for U too? I'm not sure
what "current development release" means right now given that U is out.
I believe the upstream 2.4.10 patch should apply straight to U. It's
upstream, so V will presumab
Yes, we did talk on IRC :-)
As far as I can tell, utopic 2.4.10-1ubuntu1 does not build modident
(still). I suspect what might have been fixed in the debian bug my
report got merged into (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=711925) is the constant removal of any module
called modide
Yep, though I think that was what https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=752922 asked for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/188
Title:
mod_ident no longer included in ap
Public bug reported:
Apache2 crashes with multiple SSL sites.
When starting apache2 with multiple SSL sites I get a SEGV like this:
(gdb) bt
#0 0x705faaf3 in ?? () from /usr/lib/apache2/modules/mod_ssl.so
#1 0x729647a6 in int_free_ex_data (class_index=,
obj=0x55af7460, ad=
I think I've got about the minimal case for replication. Attached is a
tiny perl script which generates a number of SSL sites of the form:
ServerName 127.0.0.1:$port
SSLEngine on
SSLCertificateFile/etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl
Actually "DBDriver pgsql" causes the issue, but not "DBDriver mysql",
and it can be outside the virtual host block. So I think this might be a
pgsql driver issue.
Reported upstream at:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56919
** Bug watch added: Apache Software Foundation Bugzill
The number of sites required appears to vary. Also it appears to be
necessary to have mod php5 enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366174
Title:
apache2 SEGV with multiple SSL si
Robie: that attitude is quite understandable. I'm willing to do some work
bisecting it, but I fear the root problem is going to be that addressed this
commit:
http://svn.apache.org/viewvc?view=revision&revision=1573360
The ssl_pphrase_Handle routine is misleadingly named, and in fact is pretty
m
Turns out 2.4.10 also has the bug after all (it's just more difficult to
trigger). I think I have found the root cause. I've put details
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366174
Robie: removing the reference to certinfo_free where
X509_get_ex_new_index is called within ssl_stapling_ex_init works around
the 2.4.10 bug at the expense of a memory leak. I haven't (yet) verified
this entirely fixes 2.4.7 though I suspect it will. I'll test that in a
bit.
Obviously this solutio
I can confirm that the above workaround fixes 2.4.7, both my testcase
and our real world version. I attach a patch. This is probably 'better
than nothing'.
** Patch added: "Patch to avoid calling certinfo_free (ugly workaround)"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1366174/+a
Public bug reported:
Precise included mod_ident in apache2.2. Trusty does not include
mod_ident in apache2.4. There appears to be no other package containing
mod_ident.so. Therefore an upgrade between Precise (LTS) and Trusty
(LTS) will unfixably break anything using mod_ident.
This affects me su
The attached patch appear to result in it building, and being able to be
inserted as a module.
root@trustytest:/home/ubuntu/apache2/apache2-2.4.7# for i in ../*.deb ; do echo
$i ; dpkg -c $i | fgrep ident ; done
../apache2_2.4.7-1ubuntu4_amd64.deb
-rw-r--r-- root/root62 2014-06-23 20:00
If you prefer this as a separate module, this would appear to compile and load
as a module:
https://github.com/abligh/libapache-mod-ident
Direction on which you would prefer would be useful and I will get
testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The fix for this is now committed in trunk. A 2.4 backport is
available. See:
https://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?r1=1631030&r2=1631029
Patch (per the above) at:
https://people.apache.org/~kbrand/mod_ssl-2.4.x-PR54357.diff
--
You received this bug notification beca
This is pretty annoying. In a situation where you have many customer VMs
running on 12.04, and want to migrate them to a host running 14.04 (so
you can do a rolling OS upgrade), I'm afraid "shut down all your
customer VMs and restart" isn't really an option for obvious reasons.
Equally, installing
Looks like there is a patch here:
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20
but it's either take it (and break inbound migrates from quantal etc.)
or don't (and break inbound migrates from precise). Another possibility
(unhelpful for libvirt po
Actually one problem we are seeing should be pretty universal.
When using OCFS2, it will open the shared iSCSI device with O_DIRECT,
and write a heartbeat there. If this errors, then the node self fences
(i.e. reboots).
If the open-iscsi package is upgraded, it calls the init with a stop
method,
Just to document an IRC conversation, another more obvious instance of
the problem is:
a) use OCFS2 with a shared heartbeat service on an iSCSI connected SAN - assume
this is not in the configuration file for iSCSI (not that it makes much
difference)
b) OCFS2 will access the raw block device wit
Public bug reported:
open-iscsi's stop script has within it the following lines:
stop() {
stoptargets
log_daemon_msg "Stopping iSCSI initiator service"
start-stop-daemon --stop --quiet --signal KILL --exec $DAEMON
rm -f $PIDFILE /lib/init/rw/sendsigs.omit.d/`basena
Ritesh,
We're actually seeing 2 problems:
1. on an upgrade to the open-iscsi module, between the stop and the
subsequent start, a daemon is calling iscsiadm and that is failing as
the module isn't loaded. Arguably this is our problem.
2. on a separate system, we have something which does somethi
Public bug reported:
Upgrade of libssl1.0.0 Precise from version 1.0.1-4ubuntu5.5 to version
1.0.1-4ubuntu5.7 causes failure of negotiation by old clients.
I am running apache2 on servers with self-signed certs (I enclose one
such). Before upgrade, I can do a 'curl -k' (insecure) and connect
succ
Sorry, I've tried on Lucid and OS-X both of which are using 0.9.8 (k and
r respectively), i.e.
$ dpkg --list | fgrep libssl
ii libssl-dev0.9.8k-7ubuntu8.13
SSL development libraries, header files and documentati
ii libssl0.9.8
We also suffer from this one. We use the perl module IO::Interface, and
whereas on Lucid etc. interfaces created as specified in the bug
description were listed, under Oneiric they are not, which cases lots of
internal things to fail. Our current workaround is a post-up script, but
that's disgustin
, a...@google.com,
a...@alex.org.uk, sta...@kernel.org
Subject: [patch for 3.2 1/1] net/netfilter/nf_conntrack_netlink.c: fix Oops on
container destroy
From: Alex Bligh
Subject: net/netfilter/nf_conntrack_netlink.c: fix Oops on container destroy
Problem:
A repeatable Oops can be caused if a
Leann,
The kernel at
http://people.canonical.com/~ogasawara/lp843892/oneiric/
seems to work fine.
Thanks for your work on this! (& apologies for spelling your name wrong
last time)
Alex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
We have Maverick running in Xen quite extensively. We use debootstrap
images with normal grub (not pvgrub), i.e. we are passing a full HD
image to Xen (and I know we aren't the only ones to do this). We do
however modify /etc/fstab etc., and aren't using -virtual (I think we
use -server) precisely
The product is not working because it incorporates router(s) than runs
in containers. The containers are necessary to provide proper isolation
of the RIBs/FIBs, iptables, conntrack entries etc. Without the
container, no routers, & no product. So we need a kernel that provides
containers, as 2.6.32
** 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/843892
Title:
Repeatable kernel oops on container delete
To manage notifications a
I have tested this on the supplied Natty kernel
root@test:/home/amb# uname -a
Linux test 2.6.38-12-server #51-Ubuntu SMP Wed Sep 28 16:07:08 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
root@test:/home/amb# dpkg --list | fgrep 2.6.38-12
ii linux-image-2.6.38-12-server 2.6.38-12.51
This is related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1008400
The outcome of bug 1008400 is (I think) 'this is fixed on Quantal by changing
the default IO scheduler to Deadline'. Two problems with that:
1. We see the same problem (but to a lesser extent) on the deadline sched
See also bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1064521
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008400
Title:
Ubuntu server uses CFQ scheduler instead of deadline
To mana
Easier way of replicating:
dd if=/dev/zero of=- bs=1M count=5 | dd if=- of=myfile bs=1M
count=5
(two dd's to prevent dd optimisation of /dev/zero writes), whilst
running Ric's script (he's just about to upload a better version.
--
You received this bug notification because you are a mem
In Precise, the problem is that the configure file shipped is failing to
consider x86_64 a valid target as it does not match the shell glob
'i?86*'. The attached fixes it. Note that configure is meant to be built
from configure.ac etc., but it's far from clear whether this actually
happens at packa
Apologies - please use this patch
** Patch removed: "Fix configure & configure.ac to allow resizecons on x86_64"
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/789196/+attachment/3413354/+files/resizecons-x86_64.patch
** Patch added: "make resizecons work on x86_64"
https://bugs.launc
Public bug reported:
1. Ubuntu release:
# lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
2. Version of package
# apt-cache policy mysql-server
mysql-server:
Installed: 5.5.24-0ubuntu0.12.04.1
Candidate: 5.5.24-0ubuntu0.12.04.1
Version table:
*** 5.5.24-0ubuntu0.
I believe a patch like this (untested) will fix the issue
** Patch added: "Patch to add create_tablespace privilege"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1062716/+attachment/3378633/+files/0001-Add-Create_tablespace_priv.patch
--
You received this bug notification because
Examples of other people stumbling across the same issue:
http://serverfault.com/questions/386903/mysql-grant-option
http://www.ajo.es/access-denied-for-user-debian-sys-maintlocalhost-using-password-yes_47/index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs
The attached disgusting hack fixes the issue on existing installs.
** Attachment added: "Fix to issue on existing installs"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1062716/+attachment/3379713/+files/fix-lp-1062716
--
You received this bug notification because you are a membe
Here's a far shorter and less disgusting workaround that does not
involve changing and restoring the MySQL root password
** Attachment added: "Less disgusting work-around"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1062716/+attachment/3379796/+files/fix-lp-1062716
--
You receiv
apport information
** Tags added: apport-collected
** Description changed:
On the Precise default kernel, it is possible by executing zcat on a
large file for an unprivileged user to disrupt I/O sufficiently that it
causes serious disruption.
Serious disruption means (e.g.) a single M
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390385/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
Titl
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390386/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390387/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
Title:
Kern
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390388/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
Title:
Kern
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390389/+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/1064521
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390391/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390390/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390392/+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/1064521
Title:
Ke
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390393/+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/1064521
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1064521/+attachment/3390394/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064521
Ti
** 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/1064521
Title:
Kernel I/O scheduling writes starving reads, local DoS
To manage no
Public bug reported:
When a cloud image is launched in a kvm based cloud, two disk references
to the same disk appear (/dev/sda and /dev/vda). The former is emulated
(slow) and the latter is paravirtualised (fast). Both appear because (a)
cloud providers cannot know a priori whether the kernel on
Public bug reported:
Cloud images boot with console=ttyS0
Though some clouds support serial consoles, others (e.g. openstack,
Flexiant's extility) provide vnc consoles. The above setting causes no
console output on these clouds using cloud images.
Ideally we'd want two console device. However, I
Personal thoughts:
1. Agree!
2. Agree with first sentence. Re second sentence, I /think/ when I last
went through this it just uses /dev/.../by-uuid/... or whatever, so
provided udev is right, the mountall stuff should be right.
3. Agree.
4. Not sure I understand "and it requires special images
Public bug reported:
libxen-dev does not contain the libxl (i.e. xenlight) libraries or
includes. xenlight is now the preferred API to manipulate xen resources
(rather than via xend), so this is an issue.
dpkg -c libxen-dev_4.1.1-2ubuntu4_amd64.deb | fgrep libxl.h
gives no results
** Affects: x
Public bug reported:
The xend init script should modprobe xen_gntdev. Unless this is done, PV
drivers will not load for HVM guests. Patch attached.
** Affects: xen (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
B
** Patch added: "Patch to add modprobe to init script"
https://bugs.launchpad.net/bugs/894713/+attachment/2607926/+files/xen_gntdev.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894713
Title
Public bug reported:
Summary: bind9 uses very high CPU after an upgrade from Lucid to
Precise. I have traced this to a directory permissions problem as
/var/cache/bind is not writeable by the bind group after an upgrade, but
is writeable after a clean install.
Ubuntu release:
root@dev1-kvm-cluste
** Description changed:
Summary: bind9 uses very high CPU after an upgrade from Lucid to
Precise. I have traced this to a directory permissions problem as
/var/cache/bind is not writeable by the bind group after an upgrade, but
is writeable after a clean install.
Ubuntu release:
roo
The server concerns was automatically installed from a CD-ROM built from
Ubuntu sources and (in respect of bind) it has only had automatic
updates run on it. I am very confident it was not operator error.
It was upgraded with 'do-release-upgrade'.
I can tell you I am not the only person experienc
Well I'm pretty sure the problem is this. I've just gone to another
(unconnected) Lucid box, and:
root@extility-developers:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.4 LTS
Release:10.04
Codename: lucid
root@extility-developers:
OK so my working hypothesis is this. On Lucid /var/cache/bind is created
simply by virtue of it being a directory within the package (see the
bind9.list file). The group write permission is added by the postinst.
If the Lucid package was installed, then removed, then installed again,
the following
To follow this up, the .deb at least on Lucid does NOT have the write
permission set.
amb@nimrod-ubuntu:~/bind-test$ dpkg -c bind9_9.7.0.dfsg.P1-1ubuntu0.8_amd64.deb
| fgrep cache
drwxr-xr-x root/root 0 2012-10-09 14:13 ./var/cache/
drwxr-xr-x root/root 0 2012-10-09 14:13 ./var/ca
Robie,
No problem - I'm just glad I wasn't imagining it.
I agree the 100% CPU problem can't be reproduced on precise.
To be honest I don't quite understand why /var/cache/bind isn't in
/var/run (given it's a cache) but I may be wrong about that.
Alex
--
You received this bug notification beca
As a matter of interest, modern xen provides the qemu device model in
which case .qcow2 files are directly usable by Xen. Indeed we are using
the Ubuntu cloud images for exactly that. I am told that it works fine
under Xen 4.1 (but minus some of the fancy live snapshotting), and fine
under Xen 4.2
Note also modern xen comes with qemu-img included. This is from xen
upstream's 'make deb' option:
amb@DBS:~/xen/xen4.2/xen-4.2.0$ dpkg -c ./dist/xen-upstream-4.2.0.deb | fgrep
qemu-img
-rwxr-xr-x root/root 1462009 2012-10-24 15:05 ./usr/lib/xen/bin/qemu-img
-rwxr-xr-x root/root163448 2012-1
** Description changed:
Affects: 1:9.7.0.dfsg.P1-1ubuntu0.8, 1:9.8.1.dfsg.P1-4ubuntu0.4, 1:9.8.4
.dfsg-1ubuntu1.
bind9.postinst only sets permissions on
/var/cache/bind on a fresh install. When the bind9 package is removed
but not purged, /var/cache/bind is removed, but /etc/bind is l
Note that upgrades from Lucid to Precise can trigger this bug as the
directory permissions may preclude writing to /var/cache/bind - see bug
1086775
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/103819
Would an SRU for Precise be reasonable?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062716
Title:
Regression in privileges of mysql debian-sys-maint user
To manage notifications about this bug g
Oops - my apologies for my launchpad newbiness. I misunderstood the
fact that the milestone entry said only "Ubuntu ubuntu-13.04-beta-1" to
mean no SRU on 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
cloud-init should run resize2fs in the background. In a development
environment I am looking at, the resize takes 2 minutes. Scott Moser
pointed out that as it runs on a mounted file system, there is no reason
not to complete the boot process whilst it runs.
** Affects: cloud
Public bug reported:
On paravirtualised Xen, cloud-init will not rerun grub. KVM may also
have issues.
The problem is at:
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/CloudConfig/cc_grub_dpkg.py
line 47.
The 'if' condition at line 36 handles the case where
** Patch added: "untested patch to fix loop over devices"
https://bugs.launchpad.net/bugs/961240/+attachment/2910439/+files/cc_grub_dpkg.py.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/96124
Public bug reported:
fakeroot-ng fails with 'Operation not permitted'.
To replicate:
amb@alex-test:~$ mkdir -p foo2 ; FAKEROOT_TMPDIR=`pwd`/foo2 fakeroot-ng -l z
echo hello
amb@alex-test:~$ cat z
Debugger started
Could not start trace of process 26862: Operation not permitted
Begin the process
Shachar, thanks, but I can't see any workaround in that bug.
I would have simply backported 0.18 to Precise and asked for an SRU,
except it needs at least g++ 4.7 (apparently), and even if I compile it
elsewhere, I'd need all the 4.7 g++ libraries I think. I can't see we're
going to get an SRU int
It's already set to 1:
amb@dbs-test:~/extility/superproject-3.0/extility-evr$ cat
/proc/sys/kernel/yama/ptrace_scope
1
but setting it to 0 seems to fix things:
amb@dbs-test:~$ mkdir -p foo2 ; FAKEROOT_TMPDIR=`pwd`/foo2 fakeroot-ng -l z
echo hello
hello
I have a feeling I might need to upgrad
Public bug reported:
I believe this was due to updat-grub hanging. strace showed it stuck
reading from stdin, so I killed it.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: kexec-tools 1:2.0.2-3ubuntu4.1
ProcVersionSignature: Ubuntu 3.0.0-27.44~lucid1-server 3.0.45
Uname: Linux 3.0.0-2
That is sadly not an option. LTS-backport kernel has a spectacular and
easy to repeat Oops when namespaces are used. See #843892.
It is not guaranteed by the kernel (it certainly wasn't in 2.6.32) that
namespaces would be created and deleted instantly and without undue
system pressure. It seems to
Note also that if vsftp continues to use clone(NEW_NETNS) (i.e. network
namespaces) it is likely to suffer from #843892 anyway, so not using
network namespaces will give you a stability increase. (NB - I have not
tested vsftp against the bug in #843892 but as you can see from the
text, it is hardly
See also #790863 - another application affected the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844185
Title:
Removal of CONFIG_NS from 2.6.32-32 breaks applications
To manage notificat
Using 2.6.38 backport is NOT a workaround. See #843892.
The only way to fix this is reverting #720095 and fixing that in
userspace (i.e. in vsftp)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863
I think this is two separate problems.
The kernel bug is one thing, but we now think it may not be recreated
using the method specified.
Our method of attempting to recreate the oops (which appears reliably in
an application we have written) does indeed cause an immediate reboot,
but we now think
OK, we are much closer to repeating this oops. Ignore the original
instructions - that seems to be a surprising lxc feature rather than the
oops.
In order to repeat, you need to have
a) a container
b) which is forwarding IPv4 traffic from one interface in the container to
another (2 veth interfac
OK I can now replicate this at will with a perl script on vanilla
Oneiric. This locks the machine hard. You will need a console to the
virtual machine to see the Oops - it doesn't get written to disk as the
lockup is immediate.
** Attachment added: "Perl program to demonstrate crash repeatably"
The attach patch fixes the issue.
The oops is called from cleanup_net when the namespace is destroyed.
conntrack iterates through outstanding events and calls death_by_timeout
on each of them, which in turn produces a call to
ctnetlink_conntrack_event. This calls nf_netlink_has_listeners, which
oo
** Description changed:
- On linux-image-2.6.38-11-generic, destroying a container causes a kernel
- OOPS and an immediate reboot. This is totally repeatable. This is on
- XUbuntu (but I doubt that makes any difference as we've done it on a
- headless Ubuntu server too).
+ On linux-image-2.6.38-11
apport information
** Tags added: apport-collected oneiric
** Description changed:
On linux-image-2.6.38-11-generic and linux-image-3.0.0-10-server,
destroying a container causes a kernel OOPS and hang. This is totally
repeatable.
Procedure to repeat:
Use the attached perl progra
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/843892/+attachment/2382676/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843892
Title:
101 - 200 of 240 matches
Mail list logo
