The backing file itself is properly registered in both cases:
$ qemu-img info /var/lib/uvtool/libvirt/images/kvmguest-artful-normal.qcow
image: /var/lib/uvtool/libvirt/images/kvmguest-artful-normal.qcow
file format: qcow2
[...]
backing file:
/var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS
The extra info of the backing file info is added on "instantiating" the guest.
So even on zesty a defined guest doesn't have the section:
Only after starting it this is generated for the "live" xml content.
So it is not a uvtool issue as the base content i
Using the uvt-kvm option "--no-start" (only in artful) lets one create
the system (iage files, xml in libvirt) without running into the error
and therefore without the cleanup on error.
Comparing Zesty with Artful:
Zesty:
type analysis (only as doc, current theory is on uvt change missing to
add the path)
The first disk is the base qcow disk which refers to the base file.
The loop iterates through backing stores.
Debugging types in old code on the loop:
Print all relevant Data in the loop
printf "type: %ld path
** Changed in: expect (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/550474
Title:
Bad handling of zero-length writes
To manage notifications about this b
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704479
Title:
Change CONFIG_IBMVETH to module
To manage notifications about this bug
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697381
Title:
update-notifier crashed with SIGSEGV in g_hash_table_lookup_node
To manage notifications about this bug
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697373
Do you have an update about this bug ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687779
Title:
Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
To manage notifications about this bug go
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696445
Title:
OpenPower: Some multipaths temporarily have only a singl
It took me a day to find out why our Java App stop printing after a
while and cupsd is gone without a notification at all. Could please
someone explain why the "cupsd -l" should be useful at all?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Added tag kernel-fixed-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672782
Title:
Graphics trouble after hibernation or Sleep
To manage notification
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689360
Title:
TCMU: Fix p
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Interestingly if just parsing the same XML on 2.5 and 3.5 they behave
the same:
Test xml:
kvmguest-artful-normal
0b4a7877-7bd2-4059-8ab3-9d02a763a682
524288
hvm
/usr/bin/kvm
On 2017-07-14 09:58, Christian Ehrhardt wrote:
> I revisit dormant bugs on a regular scheduling following our triaging policy.
> It seems nothing happened upstream still.
>
> For the Debian reporting you can do so through the mail interface - you don't
> need a Debian system.
> Usually it is pref
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698844
Title:
Fix /proc/cpuinfo revision for POWER9 DD2
To manage not
Note on test triggers:
s390x
https://jenkins.ubuntu.com/server/view/Virt/job/virt-in-release-s390x-a/19/consoleText
https://jenkins.ubuntu.com/server/view/Virt/job/virt-in-release-s390x-a/20/consoleText
https://jenkins.ubuntu.com/server/view/Virt/job/virt-in-release-s390x-a/21/consoleText
ppc64el
h
@jsalisbury - I will try - but it appears to be rather intermittent - so
not actually convinced of where the issue is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704470
Title:
playback fails usi
I use two cables with no adapters but I still experience the problem. I
tried both DP-DP and HDMI-HDMI cables on both monitors, with no luck.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267
Titl
Huh? Jibel, did we try to add the “wayland“ tag at the same time? I
tried to add it, but didn't touch “wayland-session“...
It might have been re-added by saving my addition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
The patch posted in comment #19 was included in mainline as commit
62a6cfddcc0a5313e7da3e8311ba16226fe0ac10 and was cc'd to upstream
stable.
This commit is in the Ubuntu-4.4.0-79.100 kernel. Can you apply the latest
updates and see if this bug is resolved?
** Changed in: linux (Ubuntu)
--- Comment From bren...@br.ibm.com 2017-07-17 08:40 EDT---
Canonical, we also need this fix backported to Zesty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704479
Title:
Change CONFIG_I
** Tags added: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700816
Title:
Micropolis shows garbled ingame graphics when on Wayland
To manage notifications about this bug go to:
ht
gdb break on "vah_add_file" which is the generic path adder for most calls.
A debuggable call is like:
/usr/lib/libvirt/virt-aa-helper --create --dryrun --uuid
'libvirt-0b4a7877-7bd2-4059-8ab3-9d02a763a682' < kvmguest-artful-normal.xml
Trace of the old code that added it is:
Breakpoint 1, add_f
** Changed in: linux-firmware (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704363
Title:
Add firmware for Redpine 9113 chipset
To manag
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702741
Title:
QtCreator crashes when opening a filechooser under wayland
To manage notifications about this bug go to
The function is rather old:
dc12cec6 Wed Sep 3 18:54:56 2014 util: storage: Convert disk locality check to
switch statement
But the usage of it from the iterator is not:
commit c3a83bad2aa69a26d03ee8a0b817234f0f78b4a5
Author: Michal Privoznik
Date: Thu Mar 30 17:02:39 2017 +0200
virDomain
** Tags removed: wayland-session
** Tags added: wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700816
Title:
Micropolis shows garbled ingame graphics when on Wayland
To manage notifications
Effective change from:
if (actualType != VIR_STORAGE_TYPE_NETWORK &&
actualType != VIR_STORAGE_TYPE_VOLUME &&
to:
switch (type) {
case VIR_STORAGE_TYPE_FILE:
case VIR_STORAGE_TYPE_BLOCK:
case VIR_STORAGE_TYPE_DIR:
return true;
case VIR_STORAGE_TYPE
So an apparmor issue that seems to have started with Artful (working before).
Could be a 3.5 issue as the older errors were different.
Generated rules have:
"/var/lib/uvtool/libvirt/images/kvmguest-artful-normal.qcow" rw,
"/var/lib/uvtool/libvirt/images/kvmguest-artful-normal-ds.qcow" rw,
The
Public bug reported:
It is not possible to install Skype from partner repository, yet all the
docs (i.e. https://help.ubuntu.com/community/Skype) still offer to
install it from this repository. Please fix either docs or repository.
** Affects: ubuntu-docs (Ubuntu)
Importance: Undecided
Public bug reported:
ua had some troubles with har disk, some physical erros. I fixed moving
some parts of disk and reintalling ubuntu from 14.04 to 16.04 but ai
still have some problems installing and executing softwares
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.28~
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704789
Title:
package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
failed to install/upgrade: subpr
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Cha
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701013
Title:
linux: 4.10.0-28.32 -proposed tracker
To manage notifications about this bug go to:
ht
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
** Description changed:
+ SRU Justification
+
+ Impact: The redpine driver in xenial has been updated, and a
+ corresponding firmware update is also required.
+
+ Fix: Add new firmware files.
+
+ Test case: Test with affected hw and with a kernel which has the driver
+ update.
+
+ Regression p
** Tags added: kernel-da-key
** Tags added: artful xenial yakkety zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704435
Title:
[Xenial] nvme: Quirks for PM1725 controllers
To manage notifica
--- Comment From heinz-werner_se...@de.ibm.com 2017-07-17 08:36 EDT---
Changed to new target, will be fixed with related s390-tools for kernel 4.12
** Tags removed: targetmilestone-inin1704
** Tags added: targetmilestone-inin1710
--
You received this bug notification because you are
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Ch
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701271
Title:
linux: 4.11.0-10.15 -proposed tracker
To manage notifications about this bug go to:
ht
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704469
Title:
r8169
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704004
Title:
linux-joule: -proposed tracker
To manage notifications about this bug go to:
https://
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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 t
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Cha
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Artful)
Importance: Medium
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704297
Title:
Parrot Zik headphones stuck in A2DP profile
To manage notifications about this bug go to:
https://bugs.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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 t
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702912
Title:
linux: 4.4.0-84.107 -proposed tracker
To manage notifications about this bug go to:
ht
Below is a fix/workaround/solution that might work for some who are
visiting this thread.
Short version:
Stop using external video adapters and instead use the natively supported
connections.
Medium version:
Ubuntu 14.04 _AND_ 16.04. My problem started when I started using a external
video ada
@kai I'm using the usual way after managing every dimms to test them by
memtest singly, coupled and together. IF the problem should occur again
I'll apply the workaround. However I've just red some interesting news
about 4.13 kernel on improvements on power management..
--
You received this bug n
If someone reaches this page again with this problem, try this:
Install alsamixer if you don't have it installed.
Open a terminal and execute the command below:
alsamixer -c0
this will run the alsamixer, use the left/right arrows and find "loopback"
option(Usually it's on the right side). When you
Public bug reported:
Our automated tests spotted an issue with the last libvirt upload.
In uvtool the setup is using a qcow with a base device:
So the (generated) aa profiles for the guests used to have an entry like:
"/var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZX
Hi Benjamin Wynne,
function keys are working ok only with kernel 4.12 (with which among other
problems wifi doesn't work too).
On my laptop with Windows 10 charging sometimes stops at 95% or 97% with the
notification "Plugged in not charging", and sometimes it goes to full 100%.
With Ubuntu I h
This issue was fixed in the openstack/requirements 1.1.0 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653967
Title:
nova raises ConfigFileValueError for URLs with dashes
To manage notifi
Is now working but users need to set up themselves, instructions here
https://ubuntuforums.org/showthread.php?t=2365449&p=13663158&viewfull=1#post13663158
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => Fix
This bug was fixed in the package linux-raspi2 - 4.10.0-1011.14
---
linux-raspi2 (4.10.0-1011.14) zesty; urgency=low
* linux-raspi2: 4.10.0-1011.14 -proposed tracker (LP: #1701017)
* arm64 kernel crashdump support (LP: #1694859)
- [Config] CONFIG_CRASH_DUMP=y on arm64
* hi
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the assoc
This bug was fixed in the package linux - 4.10.0-28.32
---
linux (4.10.0-28.32) zesty; urgency=low
* linux: 4.10.0-28.32 -proposed tracker (LP: #1701013)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the assoc
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-raspi2 - 4.10.0-1011.14
---
linux-raspi2 (4.10.0-1011.14) zesty; urgency=low
* linux-raspi2: 4.10.0-1011.14 -proposed tracker (LP: #1701017)
* arm64 kernel crashdump support (LP: #1694859)
- [Config] CONFIG_CRASH_DUMP=y on arm64
* hi
Public bug reported:
Test case:
Install nvidia drivers ,restart.
Open nvidia-settings, switch prime profile.
Will be prompted to log out/in, do so
What happens: user goes into a log in loop
To actually get back to the ubuntu-session one must restart.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
--- Comment From heinz-werner_se...@de.ibm.com 2017-07-17 07:49 EDT---
@XNOX, can you please point me to the updated release notes entries for
closure.. Many thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Yo!
MELBOURNE, Fla. — It was a real-life case of Jesus taking the wheel.
http://felixsolis.mobi/cottonx.php?4647
Warmest regards, Jessie Jeffries
** Attachment added: "86EEF48319E9A7567676270456990BBA.jpg"
https://bugs.launchpad.net/bugs/127280/+attachment/4916154/+files/86EEF48319E9A75676
This bug was fixed in the package linux-raspi2 - 4.8.0-1043.47
---
linux-raspi2 (4.8.0-1043.47) yakkety; urgency=low
* linux-raspi2: 4.8.0-1043.47 -proposed tracker (LP: #1701020)
* arm64: 'reboot' doesn't work, needs to pull the plug (LP: #1696436)
- [Config] BCM2835_WDT=y
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you ar
This bug was fixed in the package linux-raspi2 - 4.8.0-1043.47
---
linux-raspi2 (4.8.0-1043.47) yakkety; urgency=low
* linux-raspi2: 4.8.0-1043.47 -proposed tracker (LP: #1701020)
* arm64: 'reboot' doesn't work, needs to pull the plug (LP: #1696436)
- [Config] BCM2835_WDT=y
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_R
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_R
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_R
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_R
This bug was fixed in the package linux - 4.8.0-59.64
---
linux (4.8.0-59.64) yakkety; urgency=low
* linux: 4.8.0-59.64 -proposed tracker (LP: #1701019)
* KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device (LP: #1699651)
- Bluetooth: btusb: Add support for 0489:e0a2 QCA_R
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
501 - 600 of 740 matches
Mail list logo
