Changelog for that lists these:
drm/radeon: only apply bapm changes for AC power on ARUBA
drm/radeon: enable bapm by default on KV/KB
drm/radeon: enable bapm by default on desktop TN/RL boards
Only the last one seems to be the only one to apply to Trinity APUs. The diff
is here and it is the
Yes, this device does pair and work with the desktop successfully as
'audio device' type. See below for info from hcitool:
BD Address: 12:1F:83:05:03:B4
Device Name: Avrha Vivaldi
LMP Version: 2.0 (0x3) LMP Subversion: 0x2
Manufacturer: Accel Semiconductor Ltd.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1349462
This is perhaps not the exactly the same bug as affects me because MW600
shows up a sound output device but it only works as a handset (HDP/HFP)
but not as audio (A2DP). It worked in 12.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Package changed: linux (Ubuntu) = ubuntu-mate
** Changed in: ubuntu-mate
Status: Confirmed = New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366653
Title:
kernel BUG at
** Tags added: needs-bisect regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1363180
Title:
utopic alternate install CD doesn't boot
Status in “linux” package in
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1363180
Title:
utopic alternate install CD doesn't boot
Status in “linux”
Shoham Peller, thank you for reporting this and helping make Ubuntu better. As
per http://www.gigabyte.com/products/product-page.aspx?pid=3503#bios an update
to your BIOS is available (F11). If you update to this following
https://help.ubuntu.com/community/BiosUpdate does it change anything?
You have been subscribed to a public bug:
After updating from Ubuntu 12.04 too 14.04 on my HP 255 G1 the touchpad
will not work. I went back too 12.04 it worked fine then updated too
14.04 and no touchpad again!
** Affects: linux (Ubuntu)
Importance: Low
Status: Incomplete
**
Nachorigar95, could you please test the latest release via
http://cdimage.ubuntu.com/daily-live/current/ and advise if this is
reproducible?
As well, please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 1363176
When reporting
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1362742
Title:
kernel panic attempting to unmount device with errors
Stephen Flaherty, thank you for reporting this and helping make Ubuntu better.
Could you please execute the following in a terminal:
apport-collect 1326822
** Package changed: ubuntu = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
** Changed in: linux (Ubuntu)
Paul Stephenson, as per
Public bug reported:
I have my root partition encrypted using dm-crypt.
I could not get kdump working with the encrypted root partition, the computer
simply hangs forever and will never reboot. (I tried the same kdump and grub
settings on an identical install without encrypted root on the same
The systemd side of this is fixed in utopic, closing. The kernel (and
main) side keeps open.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: makedumpfile (Ubuntu)
Status: New = Triaged
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided = Medium
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a
still an issue !
more
/usr/src/linux-headers-3.13.0-35-generic/include/uapi/linux/netfilter_ipv4.h
/* IPv4-specific defines for netfilter.
* (C)1998 Rusty Russell -- This code is GPL.
*/
#ifndef _UAPI__LINUX_IP_NETFILTER_H
#define _UAPI__LINUX_IP_NETFILTER_H
#include linux/netfilter.h
/*
I'm not sure why a upgrade would have mattered, unless you had done
something with the files in /lib/firmware which was undone by a linux-
firmware update. Anyway, there are some changes which will be included
in the next kernel version which I think are likely to help with your
disconnections.
I'm not sure why a upgrade would have mattered, unless you had done
something with the files in /lib/firmware which was undone by a linux-
firmware update. Anyway, there are some changes which will be included
in the next kernel version which I think are likely to help with your
disconnections.
Cédric, what is the LP# for the qemu-slof update?
Thanks for this nice achievement.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1362514
Title:
LE KVM support for 14.10
Status in
3.17.0-031700rc4-generic
Download: 0.58 Mbits/s
Upload: 0.10 Mbits/s
** Tags added: kernel-bug-exists-upstream-3.17-rc4
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
C?dric, what is the LP# for the qemu-slof update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1362514
Title:
LE KVM support for 14.10
Status in “linux” package in Ubuntu:
Fix
I think we can mark this as Fix Released by now; fixes for this have
been landed in ubuntu-touch and ubuntu-rtm images for a while and we've
tested it, it does appear to work properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Hmm, this didn't include the information I expected. Here's a different
command to use, again with the speaker in range:
hcitool inq
You should get a list of all the devices in range and their class, etc.;
the class information is what I need.
In the meantime, I'll dig in the code and make sure
Public bug reported:
After updating rsyslog from 7.4.4-1ubuntu2 to 7.4.4-1ubuntu2.1 the rsyslogd
process started to take all the CPU on my machine.
The modification made by this release is described in #127, it is the
activation of KLogPermitNonKernelFacility option.
I don't know exactly
I upgraded the BIOS to latest per suggestion, and the connection is
still dropping and periodically asking to re-input my wireless password
(initial behavior from initial bug).
Output from sudo dmidecode -s bios-version sudo dmidecode -s bios-
release-date:
WYLPT10H.86A.0028.2014.0814.1906
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1366829
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Package changed: linux (Ubuntu) = rsyslog (Ubuntu)
** Changed in: rsyslog (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366829
Title:
A bios update shouldn't make any difference except possibly in the case
that the bios was disabling the wireless radio, but that isn't what's
happening here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
This patch has been submitted upstream and is queued up for inclusion in
mfd-next:
https://git.kernel.org/cgit/linux/kernel/git/lee/mfd.git/commit/?h=for-
mfd-nextid=eb61b3276e099d937fcdae2c67aec4766bba2dc3
Please include this patch in Trusty and Utopic.
** Affects: linux
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =
Parameswaran Sivatharman (psivaa)
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed = In Progress
--
You received this bug notification because
Public bug reported:
Since installation of 14.04.1 I've been trying to get bluetooth working.
Under preferences bluetooth says it's disabled. So I did $rfkill list
all, and that showed me that asus bluetooth is soft blocked. I did an
$rfkill unblock all, and nothing. I have tried everything
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1366841
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366841
Title:
mfd: rtsx_pcr: Fix MSI enable error handling
Status in
Public bug reported:
When attempting to use the 1.12.10 firmware with linux kernel versions
3.13.0-36.63 and above the system will not boot.
SATA1 link 0 timeout
SATA1 link 1 timeout
AHCI1 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq pm only pmp fbss pio slum part ccc
It appears the .deb file is corrupt.
You may need to run the following:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package.
If that does not resolve your issue, please mark the bug as Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided =
Public bug reported:
[Impact]
When using KVM, if one suspends the VM using actual power suspending
code, the guest cannot resume using 'virsh dompmwakeup'.
[Test Case]
1) Create a KVM VM and install Trusty using libvirt (although qemu alone will
also exhibit this problem)
2) Inside the vm run
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1366867
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: trusty utopic
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Medium
Status: Triaged
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee:
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366841
Title:
mfd: rtsx_pcr: Fix MSI enable error handling
Status
Hi,
This is a known compatibility issue with u-boot versions earlier than 1.13.28.
Please update u-boot and confirm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366867
Title:
PC
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
I can confirm that I see the same behavior on my Dell Venue Pro 11
(Model 7130).
Every version of Ubuntu 14.04. (that I tried) boots into a black screen on the
tablet
whereas the daily snapshot of 14.10. boots into a working screen, but doesn't
have a
working touchscreen (no response to taps
Upgraded to 3.13.0-35-generic, and now I'm not getting USB resets any
more.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just to confirm the value of that option, can you run the following
command while running the test kernel:
cat /boot/config-$(uname -r) | grep CONFIG_PCI_REALLOC_ENABLE_AUTO
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
the latest slof should reach Utopic soon :
https://launchpad.net/ubuntu/+source/slof/20140630+dfsg-1ubuntu1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1362514
Title:
LE KVM support
I took a look at the acpi tables, and I can't see anything obvious the
kernel does wrong which would make this happen. It is possible for us to
change the state of the wireless block in the bios, but it shouldn't be
getting set that way, and I don't see any way for it to be inadvertently
enabled
C?dric, what is the LP# for the qemu-slof update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1362514
Title:
LE KVM support for 14.10
Status in “linux” package in Ubuntu:
Fix
output from hcitool inq:
12:1F:83:05:03:B4 clock offset: 0x264cclass: 0x240414
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1364008
Title:
Cannot pair with Altavoz Vivaldi
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.13 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
Can you apply the latest updates and confirm if this bug is fixed or
not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359766
Title:
Kernel fails to execute code for killing OOM task
Can you apply the latest updates and confirm if this bug is fixed or
not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1327360
Title:
xfs_btree_cur leak
Status in “linux” package in
sudo apt-get --reinstall install linux-headers-3.13.0-24-generic
resolved after using the above command
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366126
Title:
Looks like it's not problem any more on system I mentioned earlier.
There are no long kernel crashes on resume.
Though, bug https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1252121 now is in effect... But that's other story.
--
You received this bug notification because you are a
I built an additional test kernel with just
CONFIG_PCI_REALLOC_ENABLE_AUTO re-enabled. It consists of the following
two .deb packages:
linux-image-3.13.0-36-generic_3.13.0-36.63~lp1363313v2_amd64.deb
linux-image-extra-3.13.0-36-generic_3.13.0-36.63~lp1363313v2_amd6
It can be downloaded from:
I built the next test kernel, up to the following commit:
5d434fcb255dec99189f1c58a06e4f56e12bf77d
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1354710
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
*** This bug is a duplicate of bug 1366448 ***
https://bugs.launchpad.net/bugs/1366448
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a
*** This bug is a duplicate of bug 1366448 ***
https://bugs.launchpad.net/bugs/1366448
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a
*** This bug is a duplicate of bug 1366448 ***
https://bugs.launchpad.net/bugs/1366448
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 #1366448, so is being marked as such.
*** This bug is a duplicate of bug 1366448 ***
https://bugs.launchpad.net/bugs/1366448
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 #1366448, so is being marked as such.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366448
Title:
[SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C] suspend/resume
failure
Status
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366448
Title:
[SAMSUNG ELECTRONICS CO., LTD.
** Changed in: bluez (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1273629
Title:
HSP fails on Ubuntu Touch [Bluetooth headset does
I am using the r8192ee module compiled from source on my t440p and it works
most of the time though does disconnect and fail periodically. I am using linux
mint 17. Unfortunately I am getting periodic system crashes: keyboard stops
working or starts emitting endless carriage returns. Sometime
bug is not present in latest kernel
http://kernel.ubuntu.com/~jsalisbury/lp1354710
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1354710
Title:
Backlight control does not work, but
What source are you using?
The latest version of the driver is at
http://github.com/lwfinger/rtlwifi_new.git. That version will build on
any kernel 3.0 or later, as long as the kernel headers are available.
--
You received this bug notification because you are a member of Kernel
Packages, which
Mainline kernel install did not fix the problem. Perhaps it made it
worse.
kernel-bug-exists-upstream
kernel-bug-exists-upstream-mainline/v3.16-utopic/linux-image-3.16.0-031600-lowlatency_3.16.0-031600.201408031935_amd64.deb
please excuse errors...my first time attempting this reporting.
I built the next test kernel, up to the following commit:
c6c1f325adc8a8e0cd06c6ad0ca232a6880a1783
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1356558
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Public bug reported:
Bluetooth doesn't work on Gigabyte f2a88xn motherboard.
Generally it's not detected. In order to have it detected, one needs to
boot into Windows, then on Ubuntu again.
Even when it's detected, it doesn't connect to the peripherals.
ProblemType: Bug
DistroRelease: Ubuntu
This patch is in the 3.15 kernel. Ubuntu 14.10 Utopic Unicorn is
based on the 3.16 kernel.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change is also in the 3.14.7 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1316689
Title:
Radeon VDPAU clients crash at vlVdpDecoderCreate with 1080p videos
Status in The
This is a qemu issue, not a kernel issue. This works with qemu 2.1, and
not 2.0. Doing a bisect now.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: New = Fix Released
** No longer
** Description changed:
Background: kernel and apparmor userspace updates to support abstract,
anonymous and fine-grained netlink socket mediation. These packages are
listed in one bug because they are related, but the FFes may be granted
and the uploads may happen at different times.
+
Copied to -proposed and overrides adjusted.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed = Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Adam Conrad
(adconrad)
--
You
** Description changed:
This bug is for tracking the 2.6.32-66.132 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
1 - 100 of 168 matches
Mail list logo
