** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
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/1507
It turns out that the host command will do what you want.
jeffs@jeffs-desktop:~$ host www.g00gle.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
Host www.g00gle.com not found: 2(SERVFAIL)
jeffs@jeffs-desktop:~$ echo $?
1 <==
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: open-vm-tools (Ubuntu)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
http
I have removed the patch from comment #4. Running with the vmhgfs
driver from the 9.10.2 code can result in data corruption. The backport
of the driver from 10.0.0 to 9.10.3 resolves the data corruption issue
as well as addressing the kernel compilation failures for 4.1 and 4.2
kernels.
As noted
*** This bug is a duplicate of bug 1500581 ***
https://bugs.launchpad.net/bugs/1500581
** Bug watch added: Debian Bug tracker #800322
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800322
** Also affects: open-vm-tools (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8003
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: open-vm-tools (Ubuntu)
Milestone: None => wily-updates
** Patch removed: "0001-vmhgfs-support-linux-4.2.x-kernel.patch"
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/
Info is attached. Note that it is from 15.10 and working fine.
** Attachment added: "info.txt"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1508744/+attachment/4502808/+files/info.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
as documented in comment 20 or
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507959 lxc start
fails when using latest LXC package from official ubuntu app repo with
3.2.0-92.130 and 3.2.0-92.131.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
Was yours also on an upgrade from vivid to wily? Were you using the
stock archive lxc packages? Any customizatoin of the lxc-net
configuration?
--
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/
I hit this too, I actually just had to run:
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
And it seemed to put itself back into a state that systemd could work
with
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://b
Public bug reported:
=
Changelog
=
1.8.3
=
See https://launchpad.net/maas/+milestone/1.8.3 for full details.
Bug Fix Update
--
#1495064Declare dependency on metadataserver migration 0015 by maasserver
migration 0121 to allow upgrades from 1.5.4
Hi,
We need this to support HP Moonshot hardware, can this be backported to
1.7 and SRU'ed to trusty?
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in U
I should mention for ScalingStack BOS01. At present, we're using a
custom package in our PPA[1].
[1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra-
workarounds/+packages
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
please i am using the newest version of chkrootkit 0.50-3.1 not 0.49
exchange discusses and it is supposed to correct detect the rootkit
--
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/bu
there is not much have to do to produce this error other than install the
program and type : sudo chkrootkit
according to relevent websites i found this error occurs because ssh didn't use
implement -g so chkrootkits method of this rootkit is no longer valid. par the
following conversation on
** Changed in: chkrootkit (Ubuntu)
Status: Incomplete => New
--
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/1508248
Title:
chkrootkit gives false positive ebury
To manage
Launchpad has imported 7 comments from the remote bug at
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
WRT option c (lie about LTS kernel):
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1508565/comments/3
Can a MaaS customer still get the hwe-t kernel through manual steps if
desired?
What are consequences to support on hwe-u? Are they know forced up to
16.04 sooner (since hwe-u does not hav
Same issue on Wily.
Adding StartupWMClass to .desktop file works around this issue:
$ cat /usr/share/applications/byobu.desktop
I am also curious to understand why MOTD is being controlled by UsePAM
Yes and not just PrintMotd.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/543767
Title:
ssh logins doesn't sh
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1509094
Title:
package mysql-common 5.6.25-0ubuntu1 failed to install/upgrade:
Unterprozess
Public bug reported:
Happens during upgrade to 15.10.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: mysql-common 5.6.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
Date:
Please show the results of
sudo systemctl status lxc-net.service
sudo journalctl -u lxc-net
sudo journalctl -xe
ifconfig -a
cat /etc/default/lxc-net
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team
Sorry, could you please show the result of
sudo journalctl -u lxc-net
if that doesn't seem to show anything, then maybe do
sudo systemctl start lxc-net
sudo journalctl -u lxc-net
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
** Bug watch added: bz.apache.org/bugzilla/ #54973
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973
** Also affects: apache2 via
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Quoting Stratos Zolotas (str...@gmail.com):
> Another one has asked but no reply yet. Is a fix for 12.04 going to be
> released? The bug is still valid there.
Which bug are you looking for? You're using a backport or ppa
or custom built lxc and are looking for a kernel fix?
--
You received this
Verified that 0.1.0~bzr227-0ubuntu1~14.10.1 works correctly on Trusty
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
As suggested by Manfred Hampl, I now open a bug report from this
question:
I use Apache 2.4.7 with mod_proxy_fcgi which is affected of this bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973 .
Is it possible to backport this patch to 2.4.7 (fixed in 2.4.8, see link
@
Filed an issue with go:
https://github.com/golang/go/issues/13024
--
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/1501651
Title:
ARM chroot issues: fatal error: rt_sigaction failure
To
Culprit in qemu code:
http://git.qemu.org/?p=qemu.git;a=blob;f=linux-user/signal.c;h=1141054be2170128d6f7a340b41484b49a255936;hb=HEAD#l82
Proposed fix (that was never merged):
https://codereview.appspot.com/124900043/diff/60001/src/pkg/runtime/os_linux.c
I was able to hack /usr/lib/go/src/runtime
Another test case:
1)
echo "package main
import "fmt"
func main() {
fmt.Println("Hi")
}
">test.go
2) GOARCH=arm go build test.go
3) qemu-arm test
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs
This also fails with upstream qemu.
Related golang bug: https://github.com/golang/go/issues/1508
--
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/1501651
Title:
ARM chroot issues: fatal
I did some investigation on option 'b' above. Attached is a bunch of
doc on how i did that.
The summary is we can exploit bug 1508975 to make all maas ppc64el users
to start getting hwe-v instead of hwe-t by default by deleting the
'com.ubuntu.maas.daily:v2:boot:14.04:amd64:hwe-t' from existance.
@paulgear - it wasn't released because of the other bug, LP: #1476175,
which still needed verification at the time I made my comment.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-tx-tftp in Ubuntu.
https://bugs.launchpad.net/b
The verification of the Stable Release Update for python-tx-tftp has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
This bug was fixed in the package python-tx-tftp -
0.1~bzr38-0ubuntu4~14.04.1
---
python-tx-tftp (0.1~bzr38-0ubuntu4~14.04.1) trusty-proposed; urgency=medium
* debian/patches/05_lp1317705.patch: Regonise error code 8, which is
used to terminate a transfer due to option negotiati
This bug was fixed in the package python-tx-tftp -
0.1~bzr38-0ubuntu4~14.04.1
---
python-tx-tftp (0.1~bzr38-0ubuntu4~14.04.1) trusty-proposed; urgency=medium
* debian/patches/05_lp1317705.patch: Regonise error code 8, which is
used to terminate a transfer due to option negotiati
Bug still present in final release
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1489675
Title:
open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel
module fa
@vorlon
Hi Steve,
I've been told you asked for priority in this testing during today's interlock.
It's was already on my list, but now it's moved higher.
I hope sometime next week is not a problem?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Milestone: None => 1.8.4
--
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/1508565
Title:
maas u
Another one has asked but no reply yet. Is a fix for 12.04 going to be
released? The bug is still valid there.
--
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/1504781
Title:
lxc-test-ubu
the one option that has been floated that i didnt list above is:
c. lie in data and make 'hwe-t' product contain the hwe-u (or hwe-v) kernel
this is less than ideal because it seems almost certain that at some point
someone will expect quite reasonably that they're using hwe-t and they're no
Upgrading to 1.0.7-0ubuntu0.9 from updates fixed it. Sorry for the
noise.
--
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/1504781
Title:
lxc-test-ubuntu hangs forever in trusty-proposed
The above report is against:
lxc 1.0.7-0ubuntu0.7
amd64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: autofs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1503
The fix is already released. Update lxc, then update the kernel.
Regards,
Jan
On 22 October 2015 at 17:44, Paul Sokolovsky <1504...@bugs.launchpad.net>
wrote:
> I got hit by the same issue, with the same unlucky kernel (installed
> from normal update channel):
>
> root@x230:~# uname -a
> Linux x
I got hit by the same issue, with the same unlucky kernel (installed
from normal update channel):
root@x230:~# uname -a
Linux x230 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
Will read suggestions above before going to back to classical VM...
--
This is not a bug, it's a broken installation. You are missing the following
file:
10月 17 13:25:37 sailor nginx[6608]: nginx: [emerg] open()
"/etc/nginx/mime.types" failed (2: No such file or directory) in
/etc/nginx/nginx.conf:26
That's installed usually but it sounds like it didn't get insta
@Maciej Lutostanski:
This bug here is marked Invalid as it is not giving us information, and
is against a superseded version of the package.
Please file a new bug with your information. You may wish to navigate
to /var/crash/, look for a .crash item related to nginx, then run
`ubuntu-bug /var/cr
$ systemctl status lxc-net.service
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Thu 2015-10-22 14:31:57 UTC; 4min
34s ago
Process: 4809 ExecStart=/usr/lib/aarch64
Hello Chuck, or anyone else affected,
Accepted horizon into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/horizon/1:2015.1.2-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Liam, or anyone else affected,
Accepted horizon into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/horizon/1:2015.1.2-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
** Branch linked: lp:ubuntu/vivid-proposed/horizon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1506826
Title:
Upgrade from kilo to liberty fails
To manage notifications about th
** Branch linked: lp:ubuntu/vivid-proposed/horizon
--
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/1506058
Title:
[SRU] Openstack 2015.1.2 point release
To manage notifications about t
Hello Chuck, or anyone else affected,
Accepted keystone into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/keystone/1:2015.1.2-0ubuntu2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
** Branch linked: lp:ubuntu/vivid-proposed/neutron-fwaas
--
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/1506058
Title:
[SRU] Openstack 2015.1.2 point release
To manage notifications a
** Branch linked: lp:ubuntu/vivid-proposed/neutron-lbaas
** Branch linked: lp:ubuntu/vivid-proposed/neutron-vpnaas
--
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/1506058
Title:
[SRU]
Hello Chuck, or anyone else affected,
Accepted neutron-vpnaas into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/neutron-
vpnaas/1:2015.1.2-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Hello Chuck, or anyone else affected,
Accepted keystone into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/keystone/1:2015.1.2-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Chuck, or anyone else affected,
Accepted neutron-lbaas into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/neutron-
lbaas/1:2015.1.2-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Hello Chuck, or anyone else affected,
Accepted neutron-fwaas into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/neutron-
fwaas/2015.1.2-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I am facing exactly the same issue after upgrading from JUNO to KILO, Is there
any work around ?
--
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/1490361
Title:
IncompatibleObjectVersi
actually i'll propose SRU to bug 1347150 since it is the original bug
raised for the issue.
--
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/1508428
Title:
nova image-list failing with S
I can confirm that the patch from 1362766 does fix this issue. I will
propose the SRU on bug 1362766 so please see that bug for progress.
** Changed in: python-glanceclient (Ubuntu)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Changed in: python-glanceclient (Ubuntu)
Status
The problem here is mainly about how to reproduce this issue.
Because sometimes the SoapClient worked for me... sometimes not. I´ll
see if I have the possibility to build a reproducable test.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
** Tags added: large-scale
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1331391
Title:
Usage overview page time's out with a large number of tenants and
instances
To manage not
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
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/1508744
Title:
Upgrade to Ubuntu 15.10 Broken: lxc-net.s
At first sight I thought this was a duplicate of bug 1504897, but that
doesn't seem to be it. If lxc-net.service fails, then the problem is
something else.
** Project changed: lxc => lxc (Ubuntu)
** Summary changed:
- Upgrade to Ubuntu 15.10 Broken
+ Upgrade to Ubuntu 15.10 Broken: lxc-net.servi
You have been subscribed to a public bug:
With lxc installed, the 15.04 -> 15.10 upgrade fails. The upgrade
completes if LXC is removed and then reinstalled later. Here is me using
apt to try and make it work (gives same errors as upgrade-manager did):
Setting up lxc (1.1.4-0ubuntu1) ...
Job for
Setting up nginx-core (1.6.2-5ubuntu3.1) ...
Job for nginx.service failed. See "systemctl status nginx.service" and
"journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
dpkg: error processing package nginx-core (--configure):
subprocess installed post-installation s
70 matches
Mail list logo
