Fixed changelog mistake in commit
3595280d8803319f71b53a22e39c386fab1577bf of the tree.
The changelog in the merge of 9.10.3-3167576 accidentally dropped
history and pulled in content from a dead development branch. This
patch fixes the changelog to reflect actual changes.
--
You received this
** Changed in: open-vm-tools (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werew
Merging upstream 9.10.3-3167576:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=641279a0debd198005d53de8e494a09207e2f16a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500581
T
Merge from Debian 2:10.0.0-3000743-3-ubuntu-1:
https://git.launchpad.net/~rcj/ubuntu/+source/open-vm-tools/commit/?id=769eeb593ce62eec332f13db653785429a942f39
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Package @ ppa:rcj/open-vm-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492429
Title:
please update open-vm-tools to version 10.0.0
To manage notifications about this bug go to:
https://bugs
Package @ ppa:rcj/open-vm-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to build on kernel 4.2 (Wily Werewolf)
[error: implicit declaration of functio
While bug #1482777 is being worked ([MIR] open-vm-tools 9.10.2 build
dependencies: xml-security-c and xerces-c) we will build 10.0 without
SAML-based guest authentication.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
I am working on bringing open-vm-tools 10.0 (bug #1492429) to Xenial.
I will disable xmlsecurity and xerces while this bug is being worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482777
Title:
** Package changed: ubuntu => ubuntu-on-ec2
** Changed in: ubuntu-on-ec2
Importance: Critical => Undecided
** Changed in: ubuntu-on-ec2
Status: Confirmed => New
** Changed in: ubuntu-on-ec2
Assignee: Ben Howard (utlemming) => (unassigned)
--
You received this bug notification be
I marked this bug as verification failed because scrolling, while
working after boot, breaks after suspend/resume. Do you want to ship
the current fix and address suspend/resume separately? This should
alleviate a lot of pain for users (and users of the Bluetooth version
won't see the suspend/res
As much as I'd like this to be fixed, it is not. During verification I
found that scrolling and middle click worked but after a suspend/resume
cycle scrolling stopped. I had to disconnect the USB keyboard and
reconnect it to get scrolling working again. Marking as verification
failed.
** Tags r
Debian has moved to 10.0.0. Ubuntu will update 9.10.2 to 9.10.3 for
Wily and pull in 10.0.0 for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500581
Title:
open-vm-tools-dkms fails to buil
We will sync 10.0.0 for xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492429
Title:
please update open-vm-tools to version 10.0.0
To manage notifications about this bug go to:
https://bugs.
I agree that this shuffling around is not pretty, but we need a solution
that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in
use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.wily/revision/2360
The current situation conflicts with how clouds
Séphane,
When this was added to the cloud seed we changed this from "users that
install LXC will loose connectivity to a 10.0.x.0/24 network" to "all
cloud users do not have connectivity to a 10.0.x.0/24 network at boot"
and the cause/effect will not be as clear to an end user. This had come
up i
My testing with the cloud image containing the proposed package has been
successful.
Just a note again that the test case detailed in the description is fine
with the understanding that network testing needs to ensure the lxc-net
service has started lxcbr0 or a false positive is possible (per comm
Be aware in your testing that the lxd-net's service can come up slowly
depending on the speed of your cloud instance. Without the bridge
(lxcbr0) the container's networking will function prior to that service
starting; watch out for this false positive in your testing.
--
You received this bug no
Cloud image downloads for amd64, i386, and ppc64el are available @ http
://cloud-images.ubuntu.com/proposed/wily/20151024/
The amd64 image is also available in canonistack lcy02 region as
lp1509414/wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Cloud images build from proposed are available.
Next action:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image produces broken lxc (and later lxd)
cont
Cloud images build from proposed are available.
Next action:
- Verification of proposed package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image produ
The cloud-image builder picked up the change and is building images.
They are with the LP buildds now. I will update this bug once
publication completes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Action plan:
Stage 1 - Configure lxc-net at boot rather than at install.
* This addresses the network failure for 15.10 containers started on 15.10
hosts (patch above in comment #6)
Stage 2 - Start lxc-net through systemd on the first launch of an LXC container.
* This mitigates the unroutable
** 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
Bugs, which is subscribed to Ubuntu.
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/op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/22/2015 02:05 PM, Robert C Jennings wrote:
> If LP were aware of the upstream git tree for a package such that
> MoM will take over and keep things fresh these would be resolved.
> Specifically http://pad.lv/u/keychain needs to k
If LP were aware of the upstream git tree for a package such that MoM
will take over and keep things fresh these would be resolved.
Specifically http://pad.lv/u/keychain needs to know about
https://github.com/funtoo/keychain
Fixes for this and other bash eval error (keychain --confhost)
https://gi
Here is a simple fix for the command.
** Patch added: "keychain.patch"
https://bugs.launchpad.net/ubuntu/+source/keychain/+bug/1508699/+attachment/4502012/+files/keychain.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
keychain has an extra '=' which breaks the --list option:
$ keychain --list
/usr/bin/keychain: 1537: [: end: unexpected operator
end
$ diff -u /usr/bin/keychain.orig /usr/bin/keychain
--- /usr/bin/keychain.orig 2015-10-21 16:50:54.411003504 -0500
+++ /usr/bin/keychain
Joseph, I installed your test kernel and it works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508178
Title:
Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
To manage
** Tags removed: patch
** Tags added: patch-accepted-upstream
** Tags added: bisect-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508178
Title:
Thinkpad USB keyboard mouse scroll not working
I have compiled a kernel with the above 3 patches (per
https://help.ubuntu.com/community/Kernel/Compile) and tested locally
with success. My keyboard is known as the "ThinkPad Compact USB
Keyboard with TrackPoint (cptkbd)" in the driver which is usb id 0x6047.
The patch will also affect the "Thin
** Patch added: "[PATCH 1/3] HID: lenovo: Use constants for axes names"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501264/+files/hid-lenovo_use_constants_for_axes_names.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "[PATCH 2/3] HID: lenovo: Add missing return-value check"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501265/+files/hid-lenovo_add_missin_return-value_check.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Patch added: "[PATCH 3/3] HID: lenovo: Hide middle-button press until
release"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501266/+files/hid-lenovo_hide_middle-button_press_until_release.patch
--
You received this bug notification because you are a member of
Here is the original patch set description from Jamie Lentin:
A collection of unrelated patches to improve support for the Thinkpad
compact keyboards. The first 2 are just cleanup patches.
The final patch alters the behaviour of the middle button so userspace
either gets wheel events or a butt
Attached 3 part patch series against Ubuntu-4.2.0-16.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508178
Title:
Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
To manage n
Public bug reported:
When moving to Wily scrolling with the middle mouse button will stop
functioning for External ThinkPad USB keyboards (mine is model KU-1255).
This is fixed upstream in drivers/hid/hid-lenovo.c (email
https://lkml.org/lkml/2015/8/11/742):
* 7f65068 HID: lenovo: Use constants
Attaching my output from:
$ xinput list
$ xinput list-props "TPPS/2 IBM TrackPoint"
** Attachment added: "xinput.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501263/+files/xinput.out
--
You received this bug notification because you are a member of Ubuntu
B
I may have recreated this locally in a lxd container. There is no
output in the attached log which points to root cause, so I started the
latest trusty daily in lxc and installed the package.
The install failed because 'invoke.rc' failed to start 'xe-daemon'.
Trying by hand (and commenting out th
Next action:
- test install in virtualized environment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504481
Title:
package xe-guest-utilities 6.2.0-1120+dsf1-0ubuntu1~14.04.1 failed to
install:
I have verified python-tz in precise, trusty, and vivid from -proposed using
the testcase in the description.
I have verified python3-tz in trusty and vivid from -proposed using the
testcase in the description.
** Tags removed: verification-needed
** Tags added: verification-done-precise verific
** Patch removed: "precise debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481526/+files/precise.debdiff
** Patch added: "precise debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481823/+files/precise.debdiff
--
You received this bug notification beca
** Patch added: "trusty debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481527/+files/trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473533
Title:
CountryNameDi
** Patch removed: "precise debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481458/+files/precise.debdiff
** Patch removed: "trusty debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481459/+files/trusty.debdiff
** Patch removed: "vivid debdiff"
https
** Patch added: "vivid debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481528/+files/vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473533
Title:
CountryNameDict
Updated patches with dep-3 tags
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473533
Title:
CountryNameDict function trying to parse UTF-8 iso3166.tab as US-ASCII
To manage notifications about thi
** Patch added: "vivid debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481460/+files/vivid.debdiff
** Changed in: python-tz (Ubuntu Precise)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: python-tz (Ubuntu Trusty)
Assignee
I have attached the debdiffs for the 3 SRUs and have them uploaded to
ppa:rcj/test as well. I have tested with the packages from that PPA.
Just need upload review.
** Changed in: python-tz (Ubuntu Precise)
Status: New => In Progress
** Changed in: python-tz (Ubuntu Trusty)
Status:
** Description changed:
+ [Impact]
+
+ * The latest tzdata update change the content type for iso3166.tab
+and zone.tab to UTF-8 which causes an exception in pytz
+
+ [Test Case]
+
+ $ apt-get install -y python-tz python3-tz
+
+ # These should produce exceptions for country_names. This t
** Patch added: "trusty debdiff"
https://bugs.launchpad.net/pytz/+bug/1473533/+attachment/4481459/+files/trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473533
Title:
CountryNameDi
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
This affects precise, trusty, and vivid. Please backport this low-risk
fix for those releases. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
drat, wrong bug. I meant to put that in bug #1473533
** No longer affects: tzdata (Ubuntu)
** This bug has been marked a duplicate of bug 1473533
CountryNameDict function trying to parse UTF-8 iso3166
** 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=800322
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
Public bug reported:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/
Validated trusty and precise. Only libxenstore3.0, xenstore-utils, and
xe-guest-utilities were installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496730
Title:
[SRU] xe-guest-utilities sudden
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Assignee: Robert C Jennings (rcj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Robie, can you review the patch in comment #10 for this fix? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406105
Title:
Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ubu
I spoke with racb and he thought that "the right thing to do might be to
debconf-ize grub-legacy-ec2 so that you don't need to change the [grub's
menu.lst] manually." rather than changing things outside of packaging
within the cloud image build.
--
You received this bug notification because you a
To add clarity, the debconf proposal in comment #5 is the long-term
solution. In the interim, the workaround in comment #4 to remove the
ucf registry entry is needed. For existing users, this will need to be
done by hand. For future cloud images the ufc entry will be removed
(in the short-term)
At the root of this issue is ucf. The ucfr command will store a path
that contains symlinks during insertion but will only match the symlink-
resolved path when attempting removal. Cloud image builds modify grub's
menu.lst but have attempted to purge the ufc registry entry. This bug
in ucf cause
This has been properly fixed by correcting a bad symlink change on the
source system.
** Changed in: ubuntu
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: ubuntu
Status: Triaged => Fix Released
--
You received this bug notification because you are a mem
Colin,
I read that you were considering[1] enabling it during t+1 and I wanted
your opinion for enabling it in Trusty on EC2 images at this time.
Also, what testing were you doing to evaluate this previously? Thanks.
[1] https://lists.ubuntu.com/archives/kernel-team/2014-April/040795.html
--
Y
Back to the prior patch to reduce scope by removing changes for 'init.d'
-> 'service' for force-reload operations in postinst scripts if invoke-
rc.d is not available. This is not changed as we can assume invoke-rc.d
is installed and the SRU change needs to be minimal.
** Patch added: "trusty_fre
** Description changed:
+ [Impact]
+
+ * freeradius can not be reloaded, upstart will lose track of the
+ process and leave the original process running (blocking future service
+ starts)
+
+ * log rotation will not function as intended. The service is not
+ reloaded and the file handles for t
** Changed in: freeradius (Ubuntu Vivid)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406105
Title:
Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8 on Ub
Ubuntu Trusty)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406105
Title:
Broken logrotate script in freeradius-2.1.12+dfsg-1.2ubuntu8
Updated the patch. The post-install scripts will restart the daemon so
that an upgrade will restart the daemon so that future reloads do work.
This addresses the 3rd scenario in comment #7. There would be no
regression for users on upgrade. If the service has been reloaded prior
to the upgrade
Marking as "won't fix" due to hardy EOL.
** Changed in: freeradius (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/315896
Title:
freeradius upgrade broken
Robie / Chris,
Can you review comment #6 for the proposed patch and upgrade
issue/strategy?
The upstart config for freeradius is bad; reload(8) or restart(8) will
lose track of the process. A reload won't send SIGHUP to the right
process and a restart(8) will not stop the existing freeradius pr
bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1406105/+attachment/4439415/+files/trusty_freeradius_lp1406105.debdiff
** Changed in: freeradius (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
ice. Then change logrotate script in trusty to call 'service freeradius
reload' and consider removing the redirect to /dev/null.
I have run out of time today but have left these notes so that we can
pursue it further.
** Changed in: freeradius (Ubuntu)
Assignee: Robert C Jennings
** Changed in: freeradius (Ubuntu)
Assignee: (unassigned) => Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406105
Title:
Broken logrotate script in freeradius-2.1
Marking as 'in progress' but holding off on marking as fixed. The issue
has been triaged but further work is required to validate the fix for
root cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Bootstrap of GCE juju environment with release streams is functioning
again for me, this was also confirmed by Curtis Hovey (sinzui on IRC)
** Changed in: ubuntu
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
So the it's just udev and systemd changes here. utlemming took the
working 20150608 ami, booted, upgraded, and rebooted and the instance
didn't survive the reboot.
This affects HVM only, PV is unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Here are the package changes between the last working and first failing
builds:
20150608 good
20150610 bad
$ diff manifest-amd64-daily-20150608.txt manifest-amd64-daily-20150610.txt
101c101
< iso-codes 3.57-1
---
> iso-codes 3.58-1
248c248
< libpam-systemd:amd64 219-10ubuntu1
---
> libpam-systemd
Last good test for EC2 occurred on June 9th with serial 20150608
https://jerff.canonical.com/job/NG_Test-EC2/376/
Ben is trying out:
wily server daily 20150608ebs-ssd amd64 us-east-1
ami-6f9e7404hvm
--
You received this bug notification because you are
** Tags added: kernel-hyper-v
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452074
Title:
[Hyper-V] hv_netvsc: Eliminate memory allocation in the packet send
path
To manage notifications about t
Verification of proposed walinuxagent completed on Utopic. Tests
passed.
** Tags removed: verification-done-trusty
** Tags added: verification-done
** Changed in: walinuxagent (Ubuntu Utopic)
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: walinuxagent (Ubuntu Tru
Test case #3 completed for Trusty.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442392
Title:
[SRU][FFE] update walinuxagent to 2.0.12
To manage notificat
Test cases #1 and #2 completed successfully for Trusty. Building
proposed image now and will test when available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442392
Title:
[SRU][FFE] update wali
I tested the vivid package. 1:4.1.5.1-1.1ubuntu3 recreated the issue
but in 1:4.1.5.1-1.1ubuntu4 --force works.
Requesting SRU of fixes from bug #1436937 back to Trusty/Utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Public bug reported:
Storage driver performance updates for vivid
K. Y. Srinivasan (7):
scsi: storvsc: Increase the ring buffer size
scsi: storvsc: Size the queue depth based on the ringbuffer size
scsi: storvsc: Always send on the selected outgoing channel
scsi: storvsc: Retrieve informa
This bug report doesn't lend itself to collection by apport-collect.
Moving to the confirmed state.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
There is no meta-package that I can find that point to the HWE cloud-
tools on Trusty, I would have to add them by name (linux-lts-utopic-
cloud-tools-) I think but I might be missing something.
Anyhow, I would like to create an image build recipe once that keeps up
with the current HWE kernel and
Public bug reported:
In bug #1393877 the linux-hwe-virtual-trusty meta package was created to
track the latest HWE kernel for trusty, however there is no mechanism to
install the latest HWE cloud tools on trusty.
Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for
use with cl
Verified on precise:
... Setting up distro-info-data (0.8ubuntu0.6) ...
Setting up distro-info (0.8.2) ...
$ distro-info --devel
ubuntu-distro-info: Distribution data outdated.
# enable proposed and upgrade distro-info-data (0.8ubuntu0.7)
$ distro-info --devel
vivid
$ distro-info --devel --full
Public bug reported:
Given an fstab with a legal fuse entry like:
encfs-reverse#/home/rcj /home/rcj.enc fusedefaults
0 0
(From
http://bazaar.launchpad.net/~vgough/encfs/trunk/view/head:/encfs/encfs.pod#L159)
We will get a traceback when parsing the fstab.
** Changed in: ubuntu
Assignee: (unassigned) => Daniel Watkins (daniel-thewatkins)
** Changed in: ubuntu
Importance: Undecided => Critical
** Tags added: spike
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I've nominated Precise as well based on the description indicating a
recreate there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371591
Title:
file not initialized to 0s under some conditions on
** Changed in: ubuntu
Assignee: Robert C Jennings (rcj) => Ben Howard (utlemming)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354839
Title:
precise vagrant cloud-images still use raring
Michael, you're correct and I hadn't tested on trusty hwe kernel before
posting comment #2. I am working on a solution for a supported kernel
that works with the virtualbox guest dkms package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: ubuntu
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354839
Title:
precise vagrant cloud-images still use raring HWE stack
To manage notifica
I have confirmed that this issue exists and I am working on a solution
that includes moving from linux-generic-lts-raring to linux-generic-lts-
trusty.
** Changed in: ubuntu
Assignee: (unassigned) => Robert C Jennings (rcj)
** Changed in: ubuntu
Status: New => Confirmed
-
Public bug reported:
A user can not delete themselves using the command 'sudo userdel -rf
', this is common in cloud tools that clean up running images
prior to capture. A quick test shows that this worked from Precise
(didn't look back further) to Raring and stopped working with Saucy.
Here's a
That should have been "with the correct *boot* device"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To manage notifications
I have reviewed the patch (lp:~utlemming/ubuntu/precise/cloud-
init/lp1336855 through r211) and tested it on EC2 and an OpenStack cloud
and it performed well. The upgrade of cloud-init forced a grub-install
and it ran with the correct root device.
--
You received this bug notification because yo
Confirmed your fix Ben. Changed /usr/lib/python2.7/dist-
packages/cloudinit/CloudConfig/cc_grub_dpkg.py, removed
/var/lib/cloud/instance/sem/config-grub-dpkg, and ran cloud-init-cfg
grub-dpkg. The cloud-init log confirmed xvda was selected and an
upgrade of grub worked.
--
You received this bug
401 - 500 of 609 matches
Mail list logo
