I've too also installed the package from proposed, and all is well.
--
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/540747
Title:
Apache Web DAV incorrect permissions
To manage not
*** This bug is a duplicate of bug 916576 ***
https://bugs.launchpad.net/bugs/916576
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #916576, so is being marked as such. Ple
*** This bug is a duplicate of bug 913809 ***
https://bugs.launchpad.net/bugs/913809
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #913809, so is being marked as such. Ple
[Expired for zookeeper (Ubuntu) because there has been no activity for
60 days.]
** Changed in: zookeeper (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
https://bugs.l
> lxc-start 1331084251.275 ERRORlxc_utmp - Too many open files
- failed to inotify_init
Note I don't know that just stopping utmp watching will help this,
however,
> lxc-start 1331084251.275 ERRORlxc_start - failed to add utmp
> handler to mainloop
> lxc-start 133108425
Johannes- The bug is that it does not route anywhere. AFAICS, its in
the list (with the rest of the versions reported) to maintain ec2
compatibility. In fat, I came across the issue when testing a tool
designed for EC2 on nova.
On EC2, for example:
adam@ath0:~$ curl http://169.254.169.254/
1.0
Public bug reported:
Doing some load testing on LXC, I noticed that I'm unable to start more
than 35 containers on my machine.
The limitation is apparently inotify and the utmp inotify watch:
lxc-start 1331084250.970 NOTICE lxc_conf - 'test40' is setup.
lxc-start 1331084250.970 NOTI
Is the bug that 1.0 doesn't route anywhere or that 1.0 is in the list in
the first place? I can't find any documentation on what a 1.0 API should
be.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad
Fix proposed to branch: master
Review: https://review.openstack.org/5003
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
Public bug reported:
Requests that are routed to the metadata url return a list of supported
metadata endpoints:
'1.0',
'2007-01-19',
'2007-03-01',
'2007-08-29',
'2007-10-10',
'2007-12-15',
'2008-02-01',
'2008-09-01',
'2009-04-04',
However, all but /1.0/ is configured in the default api-paste.in
Public bug reported:
eth* device names are hardcoded. This affects systems with biosdevname
enabled, as they use em* and p*p* instead.
Places where this is hardcoded are:
1. contrib/network
2. if-pre/post scripts
3. vlan_test{,2}.pl
** Affects: vlan (Ubuntu)
Importance: Undecided
S
Public bug reported:
In the bridge-utils.sh script in this package, eth* NIC names are
hardcoded. This affects systems with biosdevname enabled, as they use
em* and p*p* instead.
See line 11 of this script in bridge-utils (0.9.2-1):
set regex eth.\* noregex "$@"
This appears to be the o
This is due to the container running udevadm trigger --action=add.
Those events also get sent to the host, causing some hardware to be
reset. For me, in addition to sound levels being reset, my keyboard
bindings are also reset.
This won't happen with a Precise guest as it won't run udev. At the
clamav doesn't use dh_apparmor any more. Marking Invalid.
** Changed in: clamav (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/948481
Tit
I agree that if this is expected behaviour then it should be documented
more clearly - specifically in the Directory section as well as the
DirectoryMatch section.
I'm reluctant to suggest a change in Ubuntu for this, unless the
upstream Apache project who develop the software also carry the fix,
Public bug reported:
Now that dh-apparmor is a separate package, packages in 12.04 and later
that use dh_apparmor should Build-Depends on dh-apparmor so we can drop
the Depends delta in debhelper. I will be adding tasks for all packages
that still lack a Build-Depends on dh-apparmor. Note that dh-
** Changed in: horizon
Assignee: (unassigned) => Nebula (nebula)
** Changed in: horizon
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/93
Public bug reported:
This has been happening at least since 11.10 on several different computers.
Whenever I start an LXC, it changes the volume of the host computer. Sometimes
it turns it up, sometimes down.
It's quite puzzling :)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/948447
Title:
Starting an LXC changes the volume (sound!) of the host
To manage notifications about this bug go to:
https://bugs.launchpad
If it's really not a bug, would you please change the documentation of
"Directory" to make clear that end-of-line $ is not intended to work?
I see now that it says this for DirectoryMatch but there is no mention
of this limitation where Directory is documented in the manual.
Thanks.
--
You recei
** Changed in: whois (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in Ubuntu.
https://bugs.launchpad.net/bugs/943502
Title:
whois doesn't properly query .hr/.sx/.pe TLDs and inc
@ReedMerged 5.0.15 as well, thanks for the tip!
@Chris J Arges, I've also subscribed ubuntu-sponsors so sponsors can
take a look at your oneiric fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to whois in Ubuntu.
https://bugs.launch
** Also affects: whois (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Changed in: whois (Ubuntu)
Status: Confirmed => Triaged
** Changed in: whois (Ubuntu)
Importance: Undecided => Medium
** Changed in: whois (Ubuntu Oneiric)
Status: New => Triaged
** Changed i
** Also affects: python-novaclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/939766
Title:
python-novaclient flav
It's not bulletproof on an IPv6 host. I think if you can't resolve
localhost you have bigger problems.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/948320
Title:
main.cf should no
Public bug reported:
The postfix package distributes a main.cf configuration file that refers
to localhost in at least one of the parameter settings. Instead, it
should use localhost's IP address (127.0.0.1), because postfix might not
be able to resolve "localhost" even though it is defined in /et
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipxe in Ubuntu.
https://bugs.launchpad.net/bugs/948323
Title:
Rom images for e1000 and ne2k missign vendor and device id
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
The build system depends on a certain naming scheme of the rom images.
The basename of the rom file (e.g. rtl8139.rom -> rtl8139) must be
defined in the drivers PCI_ROM or ISA_ROM makro. For the rtl8139 driver
this is correctly done:
PCI_ROM(0x10ec, 0x8139, "rtl8139", "
** Changed in: asterisk (Ubuntu Oneiric)
Status: New => Confirmed
** Changed in: asterisk (Ubuntu Precise)
Status: Triaged => Confirmed
** Changed in: asterisk (Ubuntu Oneiric)
Assignee: (unassigned) => Paul Belanger (pabelanger)
** Changed in: asterisk (Ubuntu Precise)
A
** Also affects: asterisk (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: asterisk (Ubuntu Precise)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in
debdiff for oneiric-proposed
** Patch added: "asterisk_1.8.4.4~dfsg.oneiric-proposed.diff"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/920020/+attachment/2824101/+files/asterisk_1.8.4.4%7Edfsg.oneiric-proposed.diff
--
You received this bug notification because you are a member of
Debdiff for preceise
** Patch added: "asterisk_1.8.4.4~dfsg.precise.diff"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/920020/+attachment/2824075/+files/asterisk_1.8.4.4%7Edfsg.precise.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I just want to add that I got the same bug on 11.10 and that the
rc.local trick doesn't seem to work but if I run `reload autofs` once as
a local user, it will start to work instantly!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to aut
This is different then
https://issues.asterisk.org/jira/browse/ASTERISK-16425, as the patches
from it are already merged into asterisk 1.8.4.4.
Still working on finding the actual problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
This seems like it is likely fixed in seabios http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=604735 .
** Bug watch added: Debian Bug tracker #604735
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604735
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I pushed a minimal change to LXC disabling the apparmor profile for now.
Instead of removing the profile or using aa-disable I simply changed the path
to /usr/bin/lxc-start to /usr/bin/lxc-start.disabled in the profile, whenever
apparmor is fixed we'll just need to add the mount statements, bump
This bug was fixed in the package lxc - 0.7.5-3ubuntu33
---
lxc (0.7.5-3ubuntu33) precise; urgency=low
* Update apparmor profile to temporarily disable it.
This will be reverted once apparmor has been fixed. (LP: #947617)
-- Stephane GraberTue, 06 Mar 2012 12:25:21 -0500
*
Once this lands in Debian, could you perform a merge of it? (Ubuntu has
modifications of the samba package.)
Until then I'll unsubscribe the sponsors team from the bug, please
resubscribe when ready.
Thanks again for your work on this.
--
You received this bug notification because you are a mem
Is this still a problem for you?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/907197
Title:
ip address can't be injected into the instance when using lxc
To manage notifications abo
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/942061
Title:
need support for maas
To manage notifications about this bug go to:
https://bugs.launc
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
amavis start-stop script fails to stop amavisd
To manage notifications about this bug
Public bug reported:
PHP 5.4 is a major release which was released about a week ago.
Would it be pushed to Ubuntu repositories in the upcoming 12.04 release?
For Desktop and Server
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/948157
Title:
package ntp 1:4.2.4p8+dfsg-1ubuntu2.1 failed to install/upgrade: sub-
processo script post-installation instalado retornou
Public bug reported:
The package failed to update.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: ntp 1:4.2.4p8+dfsg-1ubuntu2.1
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-generic i686
Architecture: i386
Date: Tue Mar 6 11:59:04 2012
Err
I've also installed the package from proposed, and all is well.
--
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/540747
Title:
Apache Web DAV incorrect permissions
To manage notifica
** Description changed:
https://launchpad.net/maas
We need to support hte maas DataSource in cloud-init. That entails:
- * adding a maas data source, that
-* uses oath for communication
-* can be configured with url of maas server
- * accepting pre-seed to indicate data above
+
Blueprint changed by Clint Byrum:
Whiteboard changed:
Work Items:
[lamont] multinstance support: DONE
[clint-fewbar] upstart documentation: TODO
[clint-fewbar] apport pattern for invalid hostname: DONE
[lamont] not preseedable - investigate if this is fixable and document it
either
This should be fixed in the last upload.
** Changed in: nova (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/929780
Title:
console.ring file
Quoting Stéphane Graber (stgra...@stgraber.org):
> I'm happy to update our apparmor profile as soon as apparmor stops
> crashing :)
>
> For now, the only way I found to get containers working again is to turn
> off the apparmor profile.
Yikes.
It sounds like temporarily disabling the apparmor pr
Public bug reported:
Hi,
The postinstall script supposed to detect if the system is running
upstart or not with the following code:
if [ -f /etc/init/mcollective.conf ]; then
sed -i "s@^daemonize.*@daemonize = 0@" $MCOLLECTIVE_SERVER_CFG
fi
This seems wrong to me as an upstart j
@stgraber,
I hope you don't mind I've assigned this to you, as you were looking at
it yesterday, and I'm out until next monday.
I marked it high priority, because it will hit a lot of people. But on
the other hand there *is* a workaround, so I guess the priority should
be dropped... But I'll le
I'm happy to update our apparmor profile as soon as apparmor stops
crashing :)
For now, the only way I found to get containers working again is to turn
off the apparmor profile.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ub
Blueprint changed by Ben Howard:
Whiteboard changed:
Etherpad:
edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudimages-cloudinit
time slider:
http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudimages-cloudinit/latest
Work Items:
- [utlemming] Implement public glance ser
This bug was fixed in the package ntp - 1:4.2.6.p3+dfsg-1ubuntu3
---
ntp (1:4.2.6.p3+dfsg-1ubuntu3) precise; urgency=low
* debian/apparmor-profile: Add samba4 ntp signing socket to ntpd apparmor
profile (LP: #930266)
* debian/control: Build-Depends on dh-apparmor
-- Jamie Str
Blueprint changed by Scott Moser:
Whiteboard changed:
Etherpad:
edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudutils
time slider:
http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudutils/latest
Work Items:
Update ubuntu-cloudimg-query to read /query2 data: TODO
Upda
Blueprint changed by Scott Moser:
Whiteboard changed:
Etherpad:
edit: http://pad.ubuntu.com/uds-p-servercloud-p-cloudimages-cloudinit
time slider:
http://pad.ubuntu.com/ep/pad/view/uds-p-servercloud-p-cloudimages-cloudinit/latest
Work Items:
- Implement public glance server: TODO
-
This bug was fixed in the package glance - 2012.1~e4-0ubuntu1
---
glance (2012.1~e4-0ubuntu1) precise; urgency=low
* New upstream release.
* debian/control: Add python date-util. (LP: #943748)
* debian/control: Add ca-certificates. (LP: #932800)
* debian/control: Add python-is
This bug was fixed in the package glance - 2012.1~e4-0ubuntu1
---
glance (2012.1~e4-0ubuntu1) precise; urgency=low
* New upstream release.
* debian/control: Add python date-util. (LP: #943748)
* debian/control: Add ca-certificates. (LP: #932800)
* debian/control: Add python-is
** Changed in: ntp (Ubuntu)
Status: New => In Progress
** Changed in: ntp (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.
** Summary changed:
- apparmor rights bug with bind9 and resovconf
+ resolvconf uses wrong path for bind9 and resovconf
** Tags removed: apparmor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.
Looks like this landed in E4. Please reopen if there is more to it.
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/904532
Ti
** Tags removed: apparmor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/913857
Title:
ntp-keygen documentation lists options that ntp-keygen does not
support
To manage notifications
The shell crashed during startup, so I'm changing the package to dash.
This is at least closer to the mark than exim4.
** Package changed: exim4 (Ubuntu) => dash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
Seems it's a mistake in /etc/apparmor.d/usr.bin.lxc-start
Don't know how to fix it, but if you want to make lxc work quickly (without
apparmor):
ln -s /etc/apparmor.d/usr.bin.lxc-start
/etc/apparmor.d/disable/usr.bin.lxc-start
service apparmor restart
lxc-start ..
--
You received this bug n
>From http://httpd.apache.org/docs/2.2/mod/core.html#directorymatch:
"The end-of-line character ($) cannot be matched with this directive."
I appreciate that you're using rather than
, but I cannot find any documented difference
between the two. I suspect that they work the same internally.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
VarLogDistupgradeTermlog looks corrupt to me. For example, line 5445 has
come out of line 5429. It looks like gzip has errored during
compression. I may be mistaken but I think this has probably been caused
by faul
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unixodbc in Ubuntu.
https://bugs.launchpad.net/bugs/901638
Title:
Remove iodbc2 (causes upgrade failure from Oneiric to Precise)
To manage notifications about this
I've marked this as Fix Released because the current development version
is 0.8 and so presumably the bug is fixed in the current development
version as per the bug report. I've nominated the fix for Lucid to keep
the bug alive, even though we have no patch at this time.
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
racoon 0.8 is available in the current (non-LTS) release, Oneiric, and
will also be in the upcoming LTS release.
> The suggested correction is to update racoon to version 0.8.
I understand that this issue is pres
*** This bug is a duplicate of bug 947617 ***
https://bugs.launchpad.net/bugs/947617
I just happened to notice that this is a dup of 947617 and so have
marked it as such.
** This bug has been marked a duplicate of bug 947617
After update, lxc does not start
--
You received this bug notif
Public bug reported:
I'm unable to start lxc instances:
> sudo lxc-start --name precise-dotdee
lxc-start: failed to mount rootfs
lxc-start: failed to setup rootfs for 'precise-dotdee'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to sp
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/947804
Title:
Unable to start lxc instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+b
I have been searching over the internet, but I haven't seen neither the
-t option declared
** Summary changed:
- scp -f option not documented
+ scp -f and -t options not documented
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to opens
Blueprint changed by James Page:
Whiteboard changed:
+ Status 20120603
+
+ Testing packages avaliable for hadoop, hbase, pig and hadoop-zookeeper
+ in http://launchpad.net/~hadoop-ubuntu/+archive/testing
+
+ sudo add-apt-repository ppa:hadoop-ubuntu/testing
+
+ Juju charms avaliable for hadoop,
Blueprint changed by James Page:
Whiteboard changed:
Status 20122501
Dev packages avaliable for hadoop, hive, pig, hbase and hadoop-zookeeper
in http://launchpad.net/~hadoop-ubuntu/+archive/dev
sudo add-apt-repository ppa:hadoop-ubuntu/dev
Targe
Here's a prospective patch for this issue. I'm currently discussing it
with the Debian maintainers and upstream; it holds up in my testing
(running the upstream 'virtuosobackendtest' test suite), so I'm
reasonably confident we have a winner here.
** Changed in: soprano (Ubuntu Precise)
Sta
76 matches
Mail list logo