** 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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openjdk-8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788250
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774982
Title:
Marked as Fix Released on Bionic/Xenial because the SRU for bug 1777912
is done. I can't make Artful "Won't Fix", but it should be.
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Bionic)
Status: Confirmed => Fix
Updated SRU template. Let me know if there's anything I'm missing.
** Description changed:
- Per documentation at https://wiki.ubuntu.com/GoogleComputeEngineSSHKeys
- ssh keys for cloudinit and ubuntu users should both be added to the
- 'ubuntu' users authorized_keys file.
+ [Impact]
+
+ * Per
The upstream bug states that the following commit resolves this bug:
7306e32 drm/i915/bios: filter out invalid DDC pins from VBT child
devices
That commit has been in Bionic since v4.15.0-23. Do you still see this
bug with that kernel or newer?
** Tags added: bionic kernel-da-key
--
You
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed
I built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
** 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
*** This bug is a duplicate of bug 1788250 ***
https://bugs.launchpad.net/bugs/1788250
** This bug has been marked a duplicate of bug 1788250
AWT applications fail with java.awt.AWTError: Assistive Technology not
found: org.GNOME.Accessibility.AtkWrapper
--
You received this bug
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 => Medium
Public bug reported:
Updating to linux-image-4.15.0-34-generic broke X at start-up.
[ 157.020] (II) systemd-logind: logind integration requires -keeptty and
-keeptty was not provided, disabling logind integration
[ 157.021] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 157.021] (EE)
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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 built a 4.15.0-35 test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
I've checked behaviour of generic armhf kernel 4.18.7 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.7/
and the bug I report is not visible there - I can connect / disconnect USB
device from host and is is properly enumerated, also can unload/load
ci_hdrc_imx module and keep USB host
If there is no one willing to step up to maintain this in Ubuntu, then
it is not a candidate for main inclusion. Since David Britton NAKed it,
I'm unsubscribing the server team. If another team wants to have it
included in main, please feel free to resubscribe the security team.
** Changed in:
This long standing issue has been fixed during the Inkscape Hackfest in
Kiel. Those who offered money are welcome to donate to the Inkscape Fund
via the Software Freedom Conservancy. Your donations will be used for
example for Hackfest travel reimbursements which make such developer
meetings
I also agree, given OpenSSL Version 1.1.0 will be supported until one
year after the release of 1.1.1 (i.e 2019/09/11), migrating to 1.1.1 LTS
would be the best course of action for 18.04 LTS (EOL 2023/04):
https://www.openssl.org/policies/releasestrat.html
Quoting from yesterday's 1.1.1 release
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
**
Absolutely, please allow a few days until I have access to the device
it's not mine)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791372
Title:
Keyboard backlight not working on Asus ZenBook Flip
Update to my previous comment:
When the updates for Linux 4.15.0-34-generic became available (but
before installing them), I retried some of these tests, and could no
longer reproduce the problem.
I re-added each of those problematic /var/lib/apt/extended_states
entries in turn; in each case,
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: linux (Ubuntu Cosmic)
Importance: Wishlist
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => Triaged
--
You received
Public bug reported:
On Ubuntu 18.04, 'art' from artemis fails to start against default-jre
with an exception related to atk:
$ art
Exception in thread "main" java.awt.AWTError: Assistive Technology not found:
org.GNOME.Accessibility.AtkWrapper
at
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1792209
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: kernel-sru-workflow/automated-testing
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/1791663
Title:
linux: 4.18.0-8.9 -proposed tracker
To
** Changed in: kernel-sru-workflow/automated-testing
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/1791751
Title:
linux-kvm: 4.4.0-1034.40 -proposed tracker
Public bug reported:
Steps to reproduce:
* Try to install edb with `sudo apt install edb`
Expected results:
* Installation ended successfully.
Actual results:
* Installation fails with the following messages:
$ sudo apt install edb
[sudo] password for beaver:
Reading package lists... Done
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791389
Title:
usb
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188078/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Zesty went EOL before this got published I think, so marking Invalid.
** Changed in: ipxe (Ubuntu Zesty)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Can you see if this bug still exists in the latest Cosmic 4.18 based
kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Cosmic)
Importance: High
Status: Confirmed
** Tags added: kernel-key
--
You received this bug notification
apport information
** Tags added: apport-collected
** Description changed:
The USB devices are detected/enumerated correctly with system start, but when
disconnected later and connected once again are not recognized / enumerated
anymore.
Also removal of ci_hdrc_imx module causes the
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188084/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791979
Title:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188081/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791979
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1791411
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791542
Title:
package libglvnd-dev 1.0.0-2ubuntu2.1 failed to
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188085/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188083/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791979
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188082/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188080/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1791979/+attachment/5188079/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
If an admin uses ethtool to change the link speed or duplex setting while the
hardware is still processing packets, a hardware hang may result.
[Test Case]
While traffic is in-progress, use ethtool to change link speed/duplex.
[Fix]
Fixes have been applied
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.19
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.19
** Also affects: jxplorer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788250
Title:
AWT applications fail with java.awt.AWTError: Assistive
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
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.19
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.19
** Changed in: inkscape
Status: Confirmed => 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/170049
Title:
Inverted ruler co-ordinate system
To manage notifications about this
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
the reporting bug has been marked invalid and doing the same here.
** Changed in: qa-regression-testing
Status: New => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
the reported bug was marked invalid, doing the same here
** Changed in: qa-regression-testing
Status: New => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
parsing through ubuntu-kernel-tests bugs, this one is actively being
worked on, taking ownership and will touch base when I'm done.
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Sean Feole (sfeole)
**
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.19
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
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.19
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Hi Sam, is this still an issue?
+60 day bug with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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
Hi Sam, looks like this bug was somewhat fixed , still an issue?
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
Hey Sam, we still working this?
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732883
Title:
uvt-kvm wait command will never
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
hi sam, Should we be looking at this in this current sru cycle?
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged =>
Been sorting through many of the ubuntu-kernel-tests bugs.
This is one of the few that actually is being worked.
Stefan, any update on this? Should this be/ Has it been fixed? I can
revisit once i finish cleaning up the list
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
** Changed in: fwupd (Ubuntu)
Status: Confirmed => 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/1791407
Title:
Thinkpad L570 UEFI destroyed after BIOS update
To manage
closing bug per last comment
** Changed in: ubuntu-kernel-tests
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
just a wish - would it be possible to include nautilus 3.30 for cosmic
as unsupported alternative to 3.26 i.e. in the universe repro ?
Advanced users (not complaining about the missing desktop icons support) can
easily give it a try.
I read somewhere that a snap is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi fooundjem,
It seems that the service failed to restart after the upgrade.
As the console output mentioned, you should check "systemctl status
libvirt-bin.service" and "journalctl -xe" for details.
If this is still unclear I'd recommend saving your modified conffiles
/etc/default/libvirt-bin
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status:
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: qemu (Ubuntu)
Status: New =>
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+
+ * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial
+
+ * Newer guests might use virtio attributes that are clobbered on
+migration with the old qemu code.
+
+ [Test Case]
+
+ * Setup two Xenial hosts on ppc64el
+
+ * Create a
Public bug reported:
upgrading ubuntu
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.24
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Sep 12
This bug is fixed with commit c75c582e to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=c75c582e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1792206
Title:
package libvirt-bin 1.3.1-1ubuntu10.24 failed to install/upgrade:
subprocess installed
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1020.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Hi Sam, still an issue?
very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.
** Changed in: ubuntu-kernel-tests
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu
201 - 300 of 663 matches
Mail list logo
