Note just passed regression test run from the ppa fine as expected.
SRU template prepared.
Making it available to the SRU team for evaluation now.
Uploaded as qemu_2.5+dfsg-5ubuntu10.26_source.changes
** Description changed:
+ [Impact]
+
+ * some more uncommon vnc configurations (e.g. very
i can see only prime profiles, application profiles and nvidia-settings
configuration. This is happening in ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734452
Title:
** Description changed:
Steps to reproduce:
1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
2. Install Human theme from `human-theme` package
3. Select Human theme from `mate-control-center` Appearance
Expected results:
- window title color is set to Ubuntu's orange (#cf8a31)
+ window
same thing happens in ubuntu 16.04 also
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733168
Title:
resume from hibernate is slow and not reliable (nvidia)
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I can confirm the ppa fixing this case.
And OTOH it is fixed in qemu >=2.7.
Furthermore the change is very small and easily reviewable (essentially
only changing a malloc to a malloc0 to initialize properly).
I'm marking the tasks accordingly and prep this as an SRU.
** Also affects: qemu
** Also affects: ubuntu-power-systems
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/1766201
Title:
CTAUTO:DevOps:860.50:devops4fp1:Error occurred during
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello
with kubuntu 18.04 beta (all upgrades done)
When I change the secure boot from enabled to disabled, the login screen (sddm)
became totaly black.
So I see nothing.
If I don't move the mouse, I can login with the default user.
Turning the secure boot to enabled
Default Comment by Bridge
** Attachment added: "drmgr"
https://bugs.launchpad.net/bugs/1766201/+attachment/5125795/+files/drmgr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
Public bug reported:
== Comment: #0 - Application Cdeadmin - 2018-04-20
05:56:03 ==
== Comment: #1 - Application Cdeadmin - 2018-04-20
05:56:05 ==
State: Open by: stccdenv on 18 April 2018 06:27:28
This defect was opened automatically
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (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/1765504
Default Comment by Bridge
** Attachment added: "dmesg"
https://bugs.launchpad.net/bugs/1766201/+attachment/5125794/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766201
Title:
Default Comment by Bridge
** Attachment added: "sosreport"
https://bugs.launchpad.net/bugs/1766201/+attachment/5125796/+files/sosreport-devops4p10-20180420052752.tar.xz
** Changed in: ubuntu
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
**
This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3
---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium
* tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about
** Changed in: kernel-sru-workflow/verification-testing
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/1761462
Title:
linux-hwe: 4.13.0-39.44~16.04.1
** Changed in: kernel-sru-workflow/verification-testing
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/1761461
Title:
linux-gcp: 4.13.0-1013.17 -proposed
** Changed in: kernel-sru-workflow/verification-testing
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/1763296
Title:
linux-oem: 4.13.0-1024.27 -proposed
** Changed in: kernel-sru-workflow/verification-testing
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/1761459
Title:
linux-azure: 4.13.0-1014.17 -proposed
** Changed in: kernel-sru-workflow/verification-testing
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/1761458
Title:
linux-raspi2: 4.13.0-1017.18 -proposed
This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3
---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium
* tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about
This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3
---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium
* tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about
** Changed in: cpprest (Ubuntu)
Status: New => Confirmed
** Changed in: cpprest (Ubuntu)
Importance: Undecided => Medium
** Changed in: cpprest (Ubuntu)
Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco)
--
You received this bug notification because you are a member
There is another aspect to this issue: It also becomes impossible to
execute application-level keyboard shortcuts that contain Alt + Shift,
such as `Alt + Shift + R`.
What is actually executed: Alt + R and Input method is switched
What should have executes: Alt + Shift + R and Input method is
** Changed in: kernel-sru-workflow/automated-testing
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/1766022
Title:
linux-raspi2: 4.15.0-1009.10 -proposed
*** This bug is a duplicate of bug 1471979 ***
https://bugs.launchpad.net/bugs/1471979
** This bug has been marked a duplicate of bug 1471979
Laptop lid setting on AC ignored
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
** 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
Public bug reported:
Hello.
There is a new version available from
https://github.com/troglobit/inadyn/releases - 2.3.1
But even bionic uses 1.99.4
> lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
> sudo apt-get --dry-run install inadyn
Inst
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
** Also affects: gnome-control-center (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/1762952
Title:
Switching backwards between applications with
** 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
The current rsyslog does not store logs properly, nor accept remote logs
(well accepts, but they end up nowhere). This update solves all that.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux-kvm - 4.4.0-1021.26
---
linux-kvm (4.4.0-1021.26) xenial; urgency=medium
* linux-kvm: 4.4.0-1021.26 -proposed tracker (LP: #1761445)
* linux-kvm VFIO support for Kata containers (LP: #1759421)
- kvm: [config] Enable VFIO
[ Ubuntu:
This bug was fixed in the package linux-aws - 4.4.0-1017.17
---
linux-aws (4.4.0-1017.17) trusty; urgency=medium
* linux-aws: 4.4.0-1017.17 -proposed tracker (LP: #1761439)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
* intel-microcode
** 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-kvm - 4.4.0-1021.26
---
linux-kvm (4.4.0-1021.26) xenial; urgency=medium
* linux-kvm: 4.4.0-1021.26 -proposed tracker (LP: #1761445)
* linux-kvm VFIO support for Kata containers (LP: #1759421)
- kvm: [config] Enable VFIO
[ Ubuntu:
** 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-aws - 4.4.0-1017.17
---
linux-aws (4.4.0-1017.17) trusty; urgency=medium
* linux-aws: 4.4.0-1017.17 -proposed tracker (LP: #1761439)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
* intel-microcode
** 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-euclid - 4.4.0-9026.28
---
linux-euclid (4.4.0-9026.28) xenial; urgency=medium
* linux-euclid: 4.4.0-9026.28 -proposed tracker (LP: #1761444)
* CVE-2017-16995
- bpf: fix incorrect sign extension in check_alu_op()
-- Khalid Elmously
This bug was fixed in the package linux-kvm - 4.4.0-1021.26
---
linux-kvm (4.4.0-1021.26) xenial; urgency=medium
* linux-kvm: 4.4.0-1021.26 -proposed tracker (LP: #1761445)
* linux-kvm VFIO support for Kata containers (LP: #1759421)
- kvm: [config] Enable VFIO
[ Ubuntu:
** 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-aws - 4.4.0-1055.64
---
linux-aws (4.4.0-1055.64) xenial; urgency=medium
* linux-aws: 4.4.0-1055.64 -proposed tracker (LP: #1761443)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
* intel-microcode
This bug was fixed in the package linux-raspi2 - 4.4.0-1087.95
---
linux-raspi2 (4.4.0-1087.95) xenial; urgency=medium
* linux-raspi2: 4.4.0-1087.95 -proposed tracker (LP: #1761446)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
*
This bug was fixed in the package linux-aws - 4.4.0-1055.64
---
linux-aws (4.4.0-1055.64) xenial; urgency=medium
* linux-aws: 4.4.0-1055.64 -proposed tracker (LP: #1761443)
[ Ubuntu: 4.4.0-120.144 ]
* linux: 4.4.0-120.144 -proposed tracker (LP: #1761438)
* intel-microcode
** 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
Ok thanks for the data.
That looks like the "normal" openstack double console entry to have an
attachable console that logs to a file at the same time.
I made a new dir:
$ mkdir -p /var/lib/nova/instances/testlp1762769
And added the following to a libvirt 3.6 guest
This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
---
linux-snapdragon (4.4.0-1090.95) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1090.95 -proposed tracker (LP: #1763689)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config]
Only bug 1758364 hasn't been verified. The regression potential of this
change is none, so setting 'verification-testing' as 'Fix released' so
we can continue with the release process.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Changed in:
This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
---
linux-snapdragon (4.4.0-1090.95) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1090.95 -proposed tracker (LP: #1763689)
* Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware (LP: #1763644)
- [Config]
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-artful
** Tags removed: block-proposed
--
You received this bug notification because you
*** This bug is a duplicate of bug 1763689 ***
https://bugs.launchpad.net/bugs/1763689
This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
---
linux-snapdragon (4.4.0-1090.95) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1090.95 -proposed tracker (LP:
*** This bug is a duplicate of bug 1763689 ***
https://bugs.launchpad.net/bugs/1763689
This bug was fixed in the package linux-snapdragon - 4.4.0-1090.95
---
linux-snapdragon (4.4.0-1090.95) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1090.95 -proposed tracker (LP:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
I am new to bug reporting so apologies if I'm doing this wrong.
It seems I am also affected by this. I tried the upgrade from mate 17.10
to 18.04 with nvidia installed which lead to a black screen. Then I
tried upgrading first and then installing nvidia also a black screen. I
have a Lenovo w550s
** 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
** Branch linked: lp:~jibel/ubiquity/lp1765651_OEM_touch_gnome-initial-
setup_flag
** Branch linked: lp:~jibel/ubiquity/lp1765651_OEM_touch_gnome-initial-
setup_flag
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
USB reset-resume quirk prevents the device from runtime suspending,
which increases power usage.
[Test]
With the patch, the power consumption decreases 0.5W.
The tested machine doesn't need the quirk to make btusb work.
[Fix]
Update the btusb reset-resume quirk
It looks like http_proxy isn't picked by snap.
Because I am using an authenticating proxy I'm not sure I should put
that information in a system-wide /etc/environment
Why can't snap just use standard environment variables http_proxy?
--
You received this bug notification because you are a
Same on ThinkPad T470 Intel + Nvidia MX940 on Ubuntu 18.04, tried
nvidia-390 and nvidia-396
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764005
Title:
Black-screen on boot with nvidia 390 for
patch has been merged into upstream:
b1b59e16075f5e5da2943ce8de724ab96bc3c6c2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758797
Title:
[Ubuntu 18.04] USB Type-C test failed on GLK
To manage
comment #8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758797
Title:
[Ubuntu 18.04] USB Type-C test failed on GLK
To manage notifications about this bug go to:
The system was only recently installed, so there was no other version of
the kernel before on this system. However, last week I could get my
hands on this system again and update/upgrade installed a new kernel
which fixed the problem, I did not have the possibility yet to check
whether it now also
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
I am new to bug reporting so apologies if I'm doing this wrong.
It seems I am also affected by this. I tried the upgrade from mate 17.10
to 18.04 with nvidia installed which lead to a black screen. Then I
tried upgrading first and then installing nvidia also a black screen. I
have a Lenovo w550s
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and
** Also affects: linux-oem (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/1764684
Title:
Fix an issue that some PCI devices get incorrectly
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Description changed:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Description changed:
It looks like the Tomcat Java server task got dropped from tasksel
deliberately last month. I'll follow up on that but I suppose the test-
case will have to be removed or modified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Updates Tab"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1709725/+attachment/5125790/+files/2018-04-23%2011-51-12%20ekran%20g%C3%B6r%C3%BCnt%C3%BCs%C3%BC.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Packages for chromium-browser are usually published shortly after chrome is
released.
In this case though, this week is release time for Ubuntu 18.04, so chromium
will make its way to the updates after the dust settles (some time next week).
--
You received this bug notification because you
This might be the same bug as #1764445
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764087
Title:
Wrongly boots into low graphics mode
To manage notifications about this bug go to:
Actually the Updates tab works, showing firmware(fwupd) and flatpak
updates. I think better solution is bug 1733245
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709725
Title:
the updates tab
801 - 900 of 1002 matches
Mail list logo