Please get this into the archive ASAP. There will be things we'll need
to fix (like arm64 support), but let's sort that after it's in, rdeps
rebuilt, and everything seems sane on x86.
FFe approved.
** Changed in: xen (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug
Public bug reported:
Failed to install
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: nginx-naxsi-ui 1.4.1-3ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.12.5-0ubuntu2.2
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1294508
Title:
package nginx-naxsi-ui 1.4.1-3ubuntu1.1 failed to install/upgrade:
subprocess
Hi,
Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags
Sorry for terse description above. I hit this issue on 12.04.1 while
running a devstack update and having the icehouse-staging Cloud Archive
PPA installed. It sounds like the real problem is that devstack has
always tried to install where it should have been installing the qemu-
kvm package. It
Sorry for terse description above. I hit this issue on 12.04.1 while
running a devstack update and having the icehouse-staging Cloud Archive
PPA installed. It sounds like the real problem is that devstack has
always tried to install the kvm package where it should have been
installing the qemu-kvm
For ref: https://bugs.launchpad.net/devstack/+bug/1294557
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1294248
Title:
ubuntu kvm upgrade failure
To manage notifications about this
Can you please edit the bug description to give a lot more detail about
your system and about the malfunction?
--
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/1294239
Title:
dnsmasq
*** This bug is a duplicate of bug 1202655 ***
https://bugs.launchpad.net/bugs/1202655
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 #1202655, so is being marked as such.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mod-wsgi in Ubuntu.
https://bugs.launchpad.net/bugs/1202655
Title:
mod_wsgi crashes during shutdown
To manage notifications about this bug go to:
So I tried your workaround guys sudo pm-powersave false and doesn't
work for me. Still have 70 - 100 % usage cpu .. sometimes more 100+ :D.
So I decide to try install Xubuntu-desktop.. when I switch to xfce
everithings works well with all efects ..compiz etc.. CPU stay between 4
- 8% . Should be
Public bug reported:
i can't update the distro
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: spamassassin 3.3.2-6ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
AptOrdering:
spamc: Remove
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1294614
Title:
package spamassassin 3.3.2-6ubuntu2 failed to install/upgrade: il
This bug was fixed in the package apache2 - 2.4.7-1ubuntu2
---
apache2 (2.4.7-1ubuntu2) trusty; urgency=medium
* d/index.html: replace Debian with Ubuntu on default page
(LP: #1288690).
-- Robie Basak robie.ba...@ubuntu.com Wed, 19 Mar 2014 11:04:21 +
** Changed in:
exits in
xubuntu 13.10 32bit
and you may get egrep not found error as well
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
https://bugs.launchpad.net/bugs/454566
Title:
False positive for SucKit
To manage
Thanks Daviey
Adding task for release notes so we don't forget; I have 0.77 in local
testing - just waiting for 0.78 and will then upload.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bug 831628 suggests to me that the start condition should match the
current squid3 start condition: just start on runlevel [2345].
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
Public bug reported:
Update please MySQL to 5.6. Mark Shuttleworth say MySQL in Ubuntu 14.04, but i
can't find this package in repo http://packages.ubuntu.com and on launchpad.
https://plus.google.com/116812394236590806058/posts/j8L5kLdTtcH
** Changed in: juju-core
Milestone: 1.20.0 = 1.18.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1248283
Title:
juju userdata should not restart networking
To manage
** Changed in: squid-deb-proxy (Ubuntu Trusty)
Assignee: (unassigned) = Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/820697
Title:
squid-deb-proxy
** Branch linked: lp:~racb/squid-deb-proxy/upstart-runlevel-start
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/820697
Title:
squid-deb-proxy will not be started on
*** This bug is a duplicate of bug 1256931 ***
https://bugs.launchpad.net/bugs/1256931
** This bug has been marked a duplicate of bug 1256931
please include MySQL 5.6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in
I didn't realise until I went to do this that the package is synced from
Debian, is a native package, and uses upstream bzr in lp:squid-deb-
proxy. So I've submitted an MP, and would like feedback from mvo on
whether it's worth an Ubuntu delta here or not, or if he can just upload
a fix to Debian
I created new container with the command you suggested, same results as
original Ubuntu container I created.
Here's trace output.
lxc-start 1395236983.307 INFO lxc_start_ui - using rcfile
/var/lib/lxc/ubuntu/config
lxc-start 1395236983.309 WARN lxc_log - lxc_log_init called
Removing ubuntu-14.04-beta-1 milestone, since we're past feature freeze
now. There is currently no Ubuntu delta for this package; I'm hesitant
to suggest introducing one, particularly where upstream and Debian both
appear mostly inactive.
** Changed in: iptraf (Ubuntu)
Milestone:
@Tycho
Does DEBIAN_FRONTEND=noninteractive not work? Or are you unable to do
this in your case?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1284652
Title:
maas/installation-note
This bug was fixed in the package clamav - 0.98.1+dfsg-4ubuntu1
---
clamav (0.98.1+dfsg-4ubuntu1) trusty; urgency=low
* Merge from Debian unstable. Remaining changes:
- Drop build-dep on electric-fence (in Universe)
- Add apparmor profiles for clamd and freshclam along
Thanks for the info. Really this sounds like a bug in upstart - the lxc
startup all goes fine.
If you chroot into the container, does that go all right?
sudo chroot /var/lib/lxc/ubuntu/rootfs
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Yeah, I can use chroot without issues.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about
What's the time frame for this MIR review to complete?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo-go, gccgo-4.9, golang
To
Hi Robie,
On Wed, Mar 19, 2014 at 02:02:23PM -, Robie Basak wrote:
@Tycho
Does DEBIAN_FRONTEND=noninteractive not work? Or are you unable to do
this in your case?
We were listing maas as a dependency for the cloud installer, so we'd
have to ask the user to run with a non-interactive
Still experiencing this bug on Ubuntu 12.04.4
(http://i.imgur.com/C7q5XRu.png). Stopping Pacemaker manually will cause
the system to reboot normally.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
So 12.04 doesn't have the option. I even tried to trick the system
into
Right, that was the conclusion I unfortunately came to yesterday. So I
will look at the qemu source and see if there is a reasonable way to
resize the vram when the mismatch is found at migration time.
--
You received
OK, thanks. That makes sense. I'm not sure what the original rationale
was to add that message in the first place, since in the general case we
avoid such things on Ubuntu. So I'll leave the bug open for that, but I
think we can drop the milestone if it's not blocking you.
** Changed in: maas
Please install strace in the container
sudo chroot /var/lib/lxc/ubuntu/rootfs apt-get install strace
and then strace init:
sudo lxc-start -n ubuntu -- /usr/bin/strace /sbin/init
Also, does
sudo lxc-execute -n ubuntu -- /bin/bash
work?
--
You received this bug notification
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1294711
Title:
power management broken after
On Wed, Mar 19, 2014 at 03:14:35PM -, Robie Basak wrote:
OK, thanks. That makes sense. I'm not sure what the original rationale
was to add that message in the first place, since in the general case we
avoid such things on Ubuntu. So I'll leave the bug open for that, but I
think we can drop
lxc-execute appears to work, but it does output two errors.
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
And here's the output from strace:
lxc-start:
Public bug reported:
MAAS was unable to power control nodes after an upgrade from Saucy to
Trusty - specifically the template rendering throws an error:
[2014-03-19 11:10:08,272: WARNING/Worker-9] name 'ip_address' is not defined at
line 18 column 4 in file
Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.
--
You received this bug
An inactive Debian maintainer and upstream is reason NOT to introduce a
delta? I would think the opposite being the case.
It's really sad to see Ubuntu letting so many valuable patches bitrot to
death. Shame on Ubuntu! (this might sound harsh, but I feel my history
with Ubuntu and FOSS entitles
Yes, I did run into that yesterday as well. However, we have to
start somewhere :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise
Please show the output of
sudo lxc-start -n ubuntu -- /sbin/init --debug --verbose
--
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/1294284
Title:
LXC Ubuntu containers do not start in
Uname -a returnes:
Linux 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 i686 i686
i386 GNU/Linux
lshw output is attached below.
Firefox 26.0 with F5 Network Access plugin, Ver. 7080.2012.1101.1
VMware Horizon View Client, V. 2.1.0 Build 1213173
Details about the error: (you
Public bug reported:
The output of running the command is:
ubuntu@rockne-02:/etc/init$ sudo /usr/bin/mongod --auth
--dbpath=/home/ubuntu/.juju/local/db --sslOnNormalPorts --sslPEMKeyFile
'/home/ubuntu/.juju/local/server.pem' --sslPEMKeyPassword ignored
--bind_ip 0.0.0.0 --port 37017 --noprealloc
for context this problem is seen on rockne-02, but not on winton-02.
** Summary changed:
- mongodb on ppc64el with 64k pagesize
+ mongodb fails assertion on ppc64el with 64k pagesize
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It seems the pages size of rockne-02 is
ubuntu@rockne-02:~/go/src/launchpad.net/juju-core$ getconf PAGESIZE
65536
but winton-02 has:
ubuntu@winton-02:~$ getconf PAGESIZE
4096
this may be it... no idea why mongo does the alignment check anyway,
seems like crack
--
You received this bug
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1294284/+attachment/4032647/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1294284/+attachment/4032645/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Syslog attached.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032651/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
6init: Handling startup event
6init: mountall goal changed from stop to start
6init: mountall state changed from
apport information
** Tags added: apparmor apport-collected trusty
** Description changed:
I have a testing server which I installed Ubuntu 13.10 and then upgraded
to Ubuntu 14.04 beta using do-release-upgrade -d. I do not have the
option to create clean install with 14.04 directly as
On 20.03.2014 00:07, Robie Basak wrote:
Taking arbitrary patches that aren't upstream impose a maintenance burden.
Please discuss the patch that IS available in this ticket for almost
four years on it's technical merits and demerits instead of calling
other people's work arbitrary. It makes
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1294284/+attachment/4032646/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Without upload rights to Ubuntu, I can't fix the situation. The best I
can do is to plead here and backport iptraf-ng to precise as well as an
iptraf package including this patch in my stable PPA
https://launchpad.net/~r0lf/+archive/stable
HTH
--
You received this bug notification because you
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1294284/+attachment/4032648/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Comment out the line `dns=dnsmasq` in
/etc/NetworkManager/NetworkManager.conf and reboot.
** Changed in: dnsmasq (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Does the problem go away when you add the line
lxc.aa_profile = unconfined
to /var/lib/lxc/ubuntu/config?
your kern.log has a lot of deniels for filesystem mounts which should be
allowed, like mounting /sys.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Meminfo attached.
** Attachment added: meminfo
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032652/+files/meminfo
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Confirming (again) - seen with 1.17.5 on trusty - bootstrap node does
not have bridge networking.
Raising distro task for tracking.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Importance: Undecided = Critical
** Also
Shame on Ubuntu!
I don't think this is fair. Taking arbitrary patches that aren't
upstream impose a maintenance burden. I don't mind if some other person
or group wants to take that on, but I don't, which is why I'm declining
to introduce a delta in Ubuntu for this package.
I'm certainly doing
apport information
** Attachment added: lxcsyslog.txt
https://bugs.launchpad.net/bugs/1294284/+attachment/4032649/+files/lxcsyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
As a matter of fact, even if I stop the apparmor service it doesn't
change the problem with Ubuntu containers.
--
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/1294284
Title:
LXC Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like this bug was fixed in Debian in 1.3.1+dfsg-3, and Ubuntu is
now on 1.3.2-2build1, so this is fixed in Trusty.
** Bug watch added: Debian Bug tracker #720053
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Branch linked: lp:cloud-init
--
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/1292648
Title:
cloud-init should check/format Azure empheral disks each boot
To manage
I applied this patch and it worked:
=== modified file 'provider/maas/environ.go'
--- provider/maas/environ.gorevid:tarmac-20140314141156-nsn5oeamfi31t1ct
+++ provider/maas/environ.go2014-03-19 16:54:28 +
@@ -266,7 +266,13 @@
userdata, err := environs.ComposeUserData(
Added the line but no change.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about this bug
Nevermind, just saw that Serge already asked you to do this...
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To
Hmm, this is really quite weird...
Can you try:
- lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
- lxc-start -n p1
I want to know whether the issue is related to your rootfs or related to
the host, that should tell us.
--
You received this bug notification because you are a
Please run
apport-collect 1294284
and attach /var/log/syslog (after making sure no sensitive information
like usernames and passwords are there).
Please also show the contents of /proc/meminfo. It seems like services
are starting fine and then being killed, which sounds like the OOM
killer.
ahasenack hazmat: remember the br0 not coming up bug on the bootstrap node?
There were two cloud-init configs involved, right? Because br0 does get up in
services deployed to new machines, just not in the bootstrap one
ahasenack hinting that the one used for bootstrap is different than the rest
I never showed the results for the u1 container as they were identical
to ubuntu.
--
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/1294284
Title:
LXC Ubuntu containers do not start in
Just to be sure - I had used 'lxc-create -t download -n u1' but your
results showed a container name 'ubuntu'. Did you use '-n u1' or '-n
ubuntu when creating the new container?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
** Changed in: cloud-init
Importance: Undecided = Medium
--
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/1292648
Title:
cloud-init should check/format Azure empheral disks
Ok, desperate times call for desperate measures... can you do the following:
- sudo apt-get install debsums procenv
- sudo debsums -sa and attach the output to this bug report
- sudo procenv and attach the output to this bug report
--
You received this bug notification because you are a
Public bug reported:
Many schools and businesses are using Squid as a content filter for
their internal networks.
The current squid package distributed by Ubuntu works great for this,
except that SSL gatewaying support is not enabled, creating a filtering
vulnerability: wherever possible, users
Hi Serge,
Well I have updated to version 12.10 and now I do not have any problem to
suspend when I close the lid.
Thanks for the follow up.
Cheers,
Trygve
2014-03-06 5:42 GMT+01:00 Serge Hallyn 581...@bugs.launchpad.net:
Please reply if this is still an issue.
** Changed in: pm-utils
thats my quick fix:
/etc/init/winbind-squid.conf
start on started squid3
task
script
chgrp -R proxy /var/lib/samba/winbindd_privileged/
chgrp -R proxy /var/run/samba/winbindd_privileged/
end script
--
You received this bug notification because you are a member of Ubuntu
Output you requested attached.
** Attachment added: output.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032814/+files/output.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
This bug was fixed in the package cloud-init - 0.7.5~bzr969-0ubuntu1
---
cloud-init (0.7.5~bzr969-0ubuntu1) trusty; urgency=medium
* New upstream snapshot.
* Azure: Reformat ephemeral disk if it got re-provisioned
by the cloud on any reboot (LP: #1292648)
*
Public bug reported:
We should create a new machine type, perhaps 'trusty', aliased to the
newest qemu machine type. This should help us to ensure the feasability
of lts-to-lts migrations from trusty to next lts.
** Affects: qemu (Ubuntu)
Importance: High
Status: Triaged
**
** Changed in: php-json (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-json in Ubuntu.
https://bugs.launchpad.net/bugs/1262812
Title:
package php5-json 1.3.1+dfsg-2 failed to
Public bug reported:
As of bug #1274702 the hv-kvp-daemon-init pre-reqs the correct packages
to enable host-guest communications for instances running on Microsoft
Hyper-V. This package is in main, I would like to see it added to the
server seed so that trusty installs on hyper-v are enabled
Hello Serge,
Please cancel this bug report. I am currently using the version 1.4.1-12
from the Ubuntu automatic updates and the problem seems to have been
resolved (somewhere...). I think the main problem is that the Broadcom
driver is not the best.
Thanks for the help!
John
On 06/03/14
Patricia, it is currently blocked by (at least) the security team
review; this review is currently blocked by preparing a new apparmor
package upload for trusty. I sincerely hope this upload is completed
this week.
--
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
+ SRU Justification
+
+ [IMPACT] Users on Windows Azure are guaranteed to have the ephemeral
+ device as ext4 for the first boot. Subsequent boots may result in fuse
+ mounted NTFS file system.
+
+ [TEST CASE]
+ Defined in comment 3.
+
+ [Regression Potential] Low.
** Summary changed:
- cloud-init Azure Datasource does not detect new instance
+ [SRU] cloud-init Azure Datasource does not detect new instance
** Also affects: walinuxagent (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Precise)
Importance:
chkrootkit is hilariously overzealous here; it is checking if /sbin/init
contains the string HOME, which upstart most definitely does:
$ grep HOME upstart/saucy/upstart-1.10/init/*
grep: upstart/saucy/upstart-1.10/init/man: Is a directory
grep: upstart/saucy/upstart-1.10/init/tests: Is a
** Description changed:
+ SRU Justification
+
+ [IMPACT] Capturing a Windows Azure Linux instance controlled by Cloud-
+ init will result in any future instance based on it to fail to boot.
+
+ Since booting on Windows Azure for Ubuntu is controlled via Cloud-init
+ and WALinuxAgent, there are
** Also affects: openssh (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Precise)
Status: New = Triaged
** Changed in: openssh (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: openssh (Ubuntu)
Status: Fix Committed = Fix
I think this is fixed in trunk, FWIW.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1294711
Title:
power management broken after upgrade from saucy
To manage notifications about
[Expired for amavisd-new (Ubuntu) because there has been no activity for
60 days.]
** Changed in: amavisd-new (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
Can someone please test this?
lp:~thumper/juju-core/maas-no-restart-networking
I don't have a MAAS setup to hand, but according to the code above, this
*should* work.
Now we go
ifdown eth0
before messing with the network config, and
ifup eth0
ifup br0
after, and no 'restart
Public bug reported:
Please sync nose 1.3.1-1 (main) from Debian unstable (main)
This is a new bugfix release, and fixes a RC bug.
Changelog entries since current trusty version 1.3.0-3:
nose (1.3.1-1) unstable; urgency=medium
* Team upload.
* New upstream release.
* Drop
** Project changed: unity-control-center = unity-control-center
(Ubuntu)
** Summary changed:
- Match the display settings checkbox
+ [ffe/uife] Match the display settings checkbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue on Thunderbird 24.3.0 and Scientific Linux 6.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/411358
Title:
Thunderbird2 gconf gmt problem 'Bad key or directory name' because of
plus
** Description changed:
Distribution: Kubuntu 12.04
- Package: qt4-x11 4:4.8.1-0ubuntu4.6
+ Package: qt4-x11 4:4.8.1-0ubuntu4.6
Program: LibreOffice 4.3 (current master build).
This bugs origin is a crash when using KDE4 native file picker dialogs
from within LibreOffice [1].
Public bug reported:
Currently on desktop the app runs full screen (non-windowed) and we want
desktop apps to run windowed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: camera-app 2.9.1+14.04.20140307-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux
** Tags removed: bios-outdated-2.57
** Tags added: latest-bios-2.57
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267281
Title:
[Lenovo ThinkPad W530] Auto-detection of a monitor being added or
1 - 100 of 1184 matches
Mail list logo
