Public bug reported:
Currently ntpdate is started every time the network interface changes to up.
On systems that have a hardware clock this is not nessesary, causeing
unnessesary traffic and load on ntp servers.
If easily possible ntpdate shold rather be called daily or weekly via
cron, if
Public bug reported:
ntpdate calls a ubuntu specific ntp server on network-interface startup.
This causes some slight but unnessesary privacy issues as it identifies
the client software to anyone listening on the network.
This issue can be solved easily by adding the ubuntu/canonical ntp
Adding golang toolchain to MIR; scale testing to 1000 clients had some
rather nasty side-effects on the juju bootstrap node, which pushed a
virtual memory footprint of 50G/resident at 1G. Compared to the
binaries built using golang gc, this is an significant increase (over
twice the footprint
** Changed in: spamassassin (Debian)
Status: New = Fix Committed
--
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/538470
Title:
split sa-compile into a separate package
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I'm not sure what the implications would be for making this change, and
so am not comfortable with it. There may be issues with depending on
third party servers, and also implications for Canonical IS to join a
Hi,
first thanks for submiting your bug.
Short answers:
1. Where are you find a privacy issue? Please read the docu at
- http://www.ietf.org/rfc/rfc5905.txt
- http://www.ietf.org/rfc/rfc5906.txt
- http://www.ietf.org/rfc/rfc5907.txt
- http://www.ietf.org/rfc/rfc5908.txt
2. The use of
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I recently dealt with this area of ntpdate's operation.
On systems that have a hardware clock this is not nessesary, causeing
unnessesary traffic and load on ntp servers.
Can you quantify this, please? I
We already point people at the NTP pool:
$ cat /etc/ntp.conf
...
server 0.ubuntu.pool.ntp.org
server 1.ubuntu.pool.ntp.org
server 2.ubuntu.pool.ntp.org
server 3.ubuntu.pool.ntp.org
...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
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/1276714
Title:
package openssh-server 1:6.2p2-6ubuntu0.1 failed to
Humm, feeling ashamed I did not quite realized what was going on here.
Since my system has changed behaviour since upgrade I (wrongly) concluded the
issue was dig.
The issue is due the upgrade that replaced my cache dns with dnsmasq ... and
now it seems this one is the culprit.
I'll
I've also pushed this update out to the havana-proposed pocket of the
cloud-archive.
** Changed in: cloud-archive
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to migrate in Ubuntu.
No problem; thank you for confirming.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1277467
Title:
dig 9.9.3
** Attachment added: attachment
https://bugs.launchpad.net/bugs/1278446/+attachment/3975925/+files/attachment
** Description changed:
Cannot open byobu-config.
How to reproduce:
- 1. $ byobu-screen
- 2. ~⟫ byobu-config
- ERROR: Could not import the python snack module
+ 1. $
Public bug reported:
Cannot open byobu-config.
How to reproduce:
1. $ byobu-screen
2. ~⟫ byobu-config
ERROR: Could not import the python snack module
WORKAROUND:
manually specify python version like:
~⟫ python3 /usr/lib/byobu/include/config.py
ProblemType: BugDistroRelease: Ubuntu
I've run the three topology tests against the proposed pocket of the
havana cloud-archive - all three passed testing OK.
As the packages have been in proposed for a good week, releasing to
updates today.
** Changed in: cloud-archive
Status: Confirmed = Fix Committed
** Changed in:
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: clamav (Ubuntu Precise)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: clamav (Ubuntu Raring)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
Public bug reported:
Raising this now as upstream have alerted me to the fact that the
firefly release date has slipped until the start of March.
Firefly is the next stable release of Ceph, and has alway been the
intended release target for 14.04.
I'll be uploading a rc of firefly between now
** Changed in: juju-core
Milestone: None = 1.18.0
--
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/1273769
Title:
ppc64el enablement for juju/lxc
To manage notifications about this
** Summary changed:
- needs to use add-apt-archive for cloud-archive:string
+ needs to use add-apt-repository for cloud-archive:string
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
OK, I started a sync for 0.4.2-1 in trusty. This bug should be closed
when it is done. Thanks so much!
The one delta now is Debian dropping python3-greenlet-dbg, but (A) we
have dbgsym so don't really need it and (B) it was broken anyway, since
it included the python2 symbols instead of python3,
@mterry
ubuntu-server team are happy to enable glusterfs support in qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1274247
Title:
[MIR] Glusterfs
To manage notifications about
** Branch linked: lp:~evarlast/cloud-init/lp-1244355
--
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/1244355
Title:
needs to use add-apt-repository for cloud-archive:string
To
same here after update from 12.04 to 13.10 :-(
--
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/1157626
Title:
Unable to use virsh migrate on two hosts after moving to raring
To manage
I think the fix here is fairly simple: in maasserver.api.pxeconfig(),
when trying to boot a machine that we've not seen before, we should
consult BootImages before automatically defaulting to i386.
I'd like ot suggest that the most effective way to solve this is to allow the
user to set the
** Also affects: kickseed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kickseed (Ubuntu)
Status: New = Triaged
** Changed in: kickseed (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Tags added: cts-cloud-review
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to charm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1182905
Title:
charm-tools installs juju-0.7
To manage notifications about this bug go to:
** Branch linked: lp:~louis-
bouchard/ubuntu/trusty/clamav/lp799623_fix_logrotate
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/799623
Title:
Incorrect generated logrotate file
To
Because of the fan problem in Ubuntu 12.10 I still work with 12.04 LTS. In
itself there is nothing wrong with that.
Until February 4, 2014. On that day, an update arrived and I installed it as
usual.
Later that day I started my laptop again and after a while began the fan
unnecessarily run at
** Also affects: libvirt (Ubuntu Saucy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1228977
Title:
n-cpu seems to crash when running
Based on the newest listed patch being 'Push nwfilter update locking up
to top level', and this patch being applied in trusty, i will mark this
as fix released in trusty.
I'm testing a saucy package with all the v1.1.1-maint patches applied.
** Changed in: libvirt (Ubuntu)
Importance:
I can confirm that this bug is fixed by upstream in 5.5.36 (latest). I
believe it might be http://bugs.mysql.com/bug.php?id=68749
Here's the results of the testcase showing expected output:
morgo@Rbook:~/sandboxes/msb_5_5_36$ ./use ~/Desktop/testdump6.sql.txt
count(distinct(testtab.foo))
111
** Changed in: debian-installer-utils (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not
I've committed the start of this upstream, now that I've fixed things to
permit the use of GNU wget. My strategy here is going to be:
* make fetch-url (for preseeding) and kickseed both work with HTTPS
* overload debian-installer/allow_unauthenticated=false to imply wget
If the proprietary amd graphics driver is causing excessive heat, you
will need to take that up with amd, or stop using the proprietary
driver.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
Re comment #13, I'll rename SSLCERTS to SSL_CERTS - fits better into the
other variable names.
** Changed in: kickseed (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: kickseed (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
You received this bug notification
Could you please check whether the package 'qemu-slof' is installed?
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
--
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/1278161
@erikd,
this is marked Fix Released in QEMU project, but comment #28 suggests
that commit f4f1e10a58cb5ec7806d47d20671e668a52c3e70 does not in fact
solve this bug. If there is a set of patches upstream that does fix the
bug, please let me know and I'll pull them into trusty. Thanks much!
--
This bug was fixed in the package debian-installer-utils - 1.104ubuntu1
---
debian-installer-utils (1.104ubuntu1) trusty; urgency=medium
* Resynchronise with Debian. Remaining changes:
- user-params: Don't propagate vga=*, break=*, *-ubiquity, or
noninteractive to
This bug was fixed in the package python-greenlet - 0.4.2-1
Sponsored for Jackson Doak (noskcaj)
---
python-greenlet (0.4.2-1) unstable; urgency=low
* New upstream release.
* Drop non-zero-on-test-failed patch, upstream solved its function.
* Drop python-support build
** Changed in: debian-installer (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not
Verified on saucy with success. Attaching cloud-init.log for saucy.
** Attachment added: cloud-init.log for saucy verification
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1272115/+attachment/3976186/+files/cloud-init_saucy.log
--
You received this bug notification because you
** Branch linked: lp:~ubuntu-core-dev/debian-installer/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support https when using
** 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/1269626
Title:
cloud-init Azure Datasource does not detect new instance
To manage notifications
This bug was fixed in the package kickseed - 0.61ubuntu1
---
kickseed (0.61ubuntu1) trusty; urgency=medium
* Resynchronise with Debian. Remaining changes:
- Add basic RAID support. (LVM-on-RAID won't quite work yet.)
- Add basic iSCSI support.
kickseed (0.61) unstable;
** Project changed: swift = python-keystoneclient
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to swift in Ubuntu.
https://bugs.launchpad.net/bugs/1231339
Title:
keystone s3_token middleware not usable
To manage notifications about
** Changed in: byobu (Ubuntu)
Importance: Undecided = High
** Changed in: byobu (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1278446
This bug was fixed in the package pollen - 3.17-0ubuntu1
---
pollen (3.17-0ubuntu1) trusty; urgency=low
* pollinate:
- improve kernel debug info
* debian/control, debian/pollen.install, Makefile:
- TEMPORARILY disabling the building of pollen, until
either gccgo or
** Bug watch added: Debian Bug tracker #715264
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715264
** Also affects: php5 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715264
Importance: Unknown
Status: Unknown
** Changed in: php5 (Ubuntu)
Status: New =
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1278446
Title:
ERROR: Could not import the python snack module
To manage notifications about this bug go
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Status: Incomplete = Triaged
--
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/1277466
** Branch linked: lp:ubuntu/trusty-proposed/byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1278446
Title:
ERROR: Could not import the python snack module
To manage
** Changed in: byobu (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1278446
Title:
ERROR: Could not import the python snack module
This bug was fixed in the package byobu - 5.71-0ubuntu1
---
byobu (5.71-0ubuntu1) trusty; urgency=low
* usr/bin/byobu-janitor, usr/lib/byobu/date,
usr/lib/byobu/include/constants, usr/lib/byobu/include/shutil,
usr/lib/byobu/time, usr/share/byobu/profiles/tmux,
Log file and notes from verification on precise.
- Testing was successful on a host with plain text in the cloud-init:user-data
metadata field.
- Testing failed on a host which had base64 data in the cloud-init:user-data
metadata field.
I also saw that the user-script ran twice, producing two
** Branch linked: lp:debian/debian-installer-utils
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support https when using with
** Branch linked: lp:debian/kickseed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support https when using with preseed files
To
This bug was fixed in the package debian-installer - 20101020ubuntu295
---
debian-installer (20101020ubuntu295) trusty; urgency=medium
* Add SSL_CERTS variable, which can be used to build images with embedded
SSL certificates with c_rehash run over them so that OpenSSL can see
** Changed in: maas (Ubuntu)
Assignee: Andres Rodriguez (andreserl) = Jason Hobbs (jason-hobbs)
--
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/1268795
Title:
unable to
** Changed in: lxc (Ubuntu)
Status: Triaged = Fix Committed
--
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/1277466
Title:
unprivileged containers fail to start with
Public bug reported:
Panic email supplied this:
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 19000 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace
The fix that was commited to the Qemu git tree fixed the original test
case I had. @pittit then found another test case that fails and I intend
to fix that when I find a good chunk of free time. Problem is I only
work on Wemu sporadically and it takes me quite a bit of time to get up
to speed when
@rcj: this is as expected. The cloud-init user-data needs to have a
metadata key of base64_keys=cloud-init:user-data in order for it to
work.
The logs indicate that the instance your on is lacking a ubuntu user.
Can you re-run the test, but create the ubuntu user before running the
test?
--
You
I've filed a feature request with upstream. In 5.1/5.5 the InnoDB
storage engine will have a background thread that wakes up every one
second.
In future versions there will be more threads for background work (as
this is required for multi-core scalability), so it is an interesting
question how
Marking as verification-done. The logs from comment #8, actually
indicate that the test cases succeeded, however, it was failing due to
using a non-official Ubuntu image.
I verified the test cases. This SRU is good to go for release.
** Tags removed: verification-needed
** Tags added:
[Expired for keystone (Ubuntu) because there has been no activity for 60
days.]
** Changed in: keystone (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
[Expired for tomcat7 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tomcat7 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
[Expired for simplegeneric (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: simplegeneric (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to simplegeneric in Ubuntu.
[Expired for libpam-mount (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: libpam-mount (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-mount in Ubuntu.
[Expired for ldap-auth-client (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ldap-auth-client (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ldap-auth-client in
[Expired for glance (Ubuntu) because there has been no activity for 60
days.]
** Changed in: glance (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
[Expired for iscsitarget (Ubuntu) because there has been no activity for
60 days.]
** Changed in: iscsitarget (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
[Expired for likewise-open (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: likewise-open (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to likewise-open in Ubuntu.
[Expired for likewise-open (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: likewise-open (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to likewise-open in Ubuntu.
[Expired for glance (Ubuntu) because there has been no activity for 60
days.]
** Changed in: glance (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
[Expired for python-django (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: python-django (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-django in Ubuntu.
[Expired for glance (Ubuntu) because there has been no activity for 60
days.]
** Changed in: glance (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
[Expired for likewise-open (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: likewise-open (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to likewise-open in Ubuntu.
** Changed in: php5 (Debian)
Status: Unknown = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1253990
Title:
sessions removed even if max life time isn't reached
To
Hello,
So we need some more information. Please run from a terminal window:
apport-collect 1278635
and then change the status of the bug to 'Confirmed'.
Jörg
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of
Reviewed: https://review.openstack.org/71687
Committed:
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=d73af8787280002321ab52a3262a2d0b5a8e54cd
Submitter: Jenkins
Branch:master
commit d73af8787280002321ab52a3262a2d0b5a8e54cd
Author: Joe Gordon joe.gord...@gmail.com
Date:
*** This bug is a duplicate of bug 1273272 ***
https://bugs.launchpad.net/bugs/1273272
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 #1273272, so is being marked as such.
81 matches
Mail list logo
