This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~18.04.1
---
docker.io (18.09.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport to 18.04 (LP: #1815683).
-- Michael Hudson-Doyle Wed, 13 Feb 2019
13:24:14 +1300
** Changed in: docker.io (Ubuntu Bionic)
Sta
This bug was fixed in the package openssl-ibmca - 1.4.1-0ubuntu1.1
---
openssl-ibmca (1.4.1-0ubuntu1.1) bionic; urgency=medium
* Cherrypick upstream hw accelerated crypto perfomance fix to prefer
RSA-CRT, instead of RSA-ME. LP: #1806483
-- Dimitri John Ledkov Tue, 12 Feb 201
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu4.1
---
libseccomp (2.3.1-2.1ubuntu4.1) bionic; urgency=medium
* d/p/lp-1755250-add-the-statx-syscall.patch: add statx support (LP: #1755250)
* d/p/lp-1815415-*: Add syscalls up to kernel 4.15 (LP: #1815415)
-- Christ
This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~16.04.1
---
docker.io (18.09.2-0ubuntu1~16.04.1) xenial; urgency=medium
* Backport to 16.04 (LP: #1815683).
* Revert "Let dh_systemd install .service file: replace .install file entry
with symlink"
* Build with t
This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~16.04.1
---
docker.io (18.09.2-0ubuntu1~16.04.1) xenial; urgency=medium
* Backport to 16.04 (LP: #1815683).
* Revert "Let dh_systemd install .service file: replace .install file entry
with symlink"
* Build with t
The verification of the Stable Release Update for libseccomp has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
The verification of the Stable Release Update for libseccomp has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~18.04.1
---
docker.io (18.09.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport to 18.04 (LP: #1815683).
-- Michael Hudson-Doyle Wed, 13 Feb 2019
13:24:14 +1300
** Changed in: docker.io (Ubuntu Bionic)
Sta
Public bug reported:
With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user
space code crashes while handling a netlink message from the kernel, the
kernel module will be stuck waiting for the response. This situation can
only be resolved with a server reboot.
=== SRU Justificati
** Description changed:
This appears to be the same bug that was present, two kernels ago:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795
I switched to the 46 kernel from the 45 today, and noticed my tablet
hangs when its plugged into the docking station. Without the d
Public bug reported:
This is actually a regression in Disco from Artful, Bionic and Cosmic,
where this was fixed in https://bugs.launchpad.net/bugs/1717951
Since the update to Disco the unprofessional and childish ImageMagick
icon is back. It was removed in Artful, Bionic and Cosmic for the
follo
The verification of the Stable Release Update for libxcb has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
Here's a log from a boot using your kernal at
https://people.canonical.com/~khfeng/lp1814069/
Kernel parameters are as you requested and a modprobe hv_netvsc after boot.
I'm not sure exactly how to retrieve dmesg properly nowadays but I used
journalctl -k -b -2 to retrieve the kernel messages for
This bug was fixed in the package libxcb - 1.13-2~ubuntu18.04
---
libxcb (1.13-2~ubuntu18.04) bionic-proposed; urgency=medium
[ Timo Aaltonen ]
* Package libxcb-xinput0/libxcb-xinput-dev. (Closes: #733227) (LP: #1777994)
[ Andreas Boll ]
* control: Fix VCS urls.
-- Jonathan
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+attachment/5245519/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819
This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.1
---
resolvconf (1.79ubuntu10.18.04.1) bionic; urgency=medium
* Pull systemd-resolved conf from non-stub file; the stub file should
not be used unless all dns traffic goes to the local stub resolver.
Specific
--- Comment From heinz-werner_se...@de.ibm.com 2018-12-12 05:40
EDT---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646805
Title:
MAC address needs to be unique and unchanged during entire
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the
status to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Pub
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the
status to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Pub
Since Kernel 5.0 just landed in disco's release pocket, I'm changing the
status to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Pub
I'm not able to recreate this on stein (that is, assuming I understand
the problem correctly).
$ openstack domain list
+--++-+--+
| ID | Name | Enabled | Description
** Also affects: systemd
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/1819471
Title:
gsd-power is not using lid-close-suspend-with-external-monitor value
Public bug reported:
[Impact]
Per https://patchwork.kernel.org/cover/10737541/ :
"Every controller HW version has had bugs. These bugs have been very
painful to debug. One useful tool to debug these is being able to capture
and export HW registers and driver control structures at point of failure
Since Kernel 5.0 landed in disco's release pocket today, I'm changing
the status to Fix Released.
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification b
Kernel 5.0 landed in disco's release pocket today, hence changing status
to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
This bug was fixed in the package virt-manager - 1:1.5.1-0ubuntu1.2
---
virt-manager (1:1.5.1-0ubuntu1.2) bionic; urgency=medium
* d/p/lp-1796932-tests-osdict-fix-ordering-issue-with-new-osinfo.patch:
fix FTBFS due to self-tests failing with new osinfo (LP: #1796932)
-- dann f
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Crash from :i915 module with 4.15.0-46-gene
Since Kernel 5.0 landed in disco's release pocket today, I'm changing
the status to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because
NOTE: The pen also reports a 1% battery all of the time. I'm not sure if
this is directly related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819389
Title:
i2c_hid_get_input: incomplete report i
These are the commands I used to cause the bug:
1st time:
sudo apt purge wpasupplicant
2nd time:
sudo apt install wicd-gtk
sudo apt remove network-manager-gnome network-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Over the last couple of weeks gnome-control-center has autonomously uninstalled
(or perhaps just disabled) twice: once as I uninstalled wpa_supplicant, and the
second time when I uninstalled NetworkManager (and installed WICD instead). In
both cases, trying to run gnome-con
The verification of the Stable Release Update for virt-manager has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encoun
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245520/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-themes (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/1788998
Title
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245530/+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/1819486
Title:
Cr
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245523/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245518/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Crash
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245528/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Titl
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245529/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Cr
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245524/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245525/+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/1819486
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245521/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Cras
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245519/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245526/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245531/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245522/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819486
Title:
Cras
apport information
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
** Description changed:
While previously working using 4.15.0-45-generic, booting my thinkpad
T480 on a dock with additional screen connected and "kernel
4.15.0-46-generic" le
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1819486/+attachment/5245527/+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/1819486
This bug was fixed in the package pglogical-ticker - 1.3.1-1ubuntu1
---
pglogical-ticker (1.3.1-1ubuntu1) disco; urgency=medium
* d/p/fix-test-error-11.2.patch: Fix test issue with
postgresql 11.2 (LP: #1815665)
-- Christian Ehrhardt Mon, 11 Mar
2019 13:32:27 +0100
** Chang
** Description changed:
- network loss and traffic loss problems experienced by customer with i40e
2.1.14-k in Xenial HWE Kernel 4.15
- The traffic issues were reported from our customer deployments and we had
Intel helping us with the troubleshooting of the problem. Intel recommends and
custom
Try idle=halt! It is the workaround that fixes the random freezes! You
don't need anything else (at least not with Ryzen 1*** and 2***U
processors, as it works wonders on my desktop with a 1600 and my
notebook with a 2700U).
IDLE=HALT IS THE WORKAROUND THAT FIXES THIS BULLSHIT!
I REPEAT:
IDLE=HALT
Hi ! I haven’t read all the comments here because there are too many by
now, but I’m puzzled that many consider this to be a Linux-only issue,
because I can tell you that it definitely happens on Windows (10) too,
and I found other people with the same freeze/reboot problem on Windows.
For me the c
I had the same issue, followed David's instructions, but I still get a
rapidly expanding syslog file when I lock the screen. I am running
Ubuntu 18.04.02 with gnome shell 3.28.3, dual monitor and intel
graphics.
Something I can see is that when locked the screens are first turned to
black, then th
Here (Asus CrossHair VI, 1600, gentoo with any kernel around), no
suggested workaround works. The system freezes when in very light use
and I was never able to obtain a single line of debug via serial (I put
a small linux mini itx box near this computer just to receive the serial
log).
It seems li
I'm also not familiar with dpkg-statoverride, but the pattern seems to be
something along those lines:
- if there is no override for path /foo/bar, call dpkg-statoverride with
--update
Example from cron's postinst:
# Fixup crontab binary for new group 'crontab'.
if ! dpkg-statoverride --list /us
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
** Description changed:
- network loss and traffic loss problems experienced by customer with i40e
2.1.14-k in Xenial HWE Kernel 4.15
- The traffic issues were reported from our customer deployments and we had
Intel helping us with the troubleshooting of the problem. Their conclusion was
that
The same happens with 5.0.0 (it is the uppermost folder in the mainline
builds, but I think it is older than 5.0.1). Still, I can reproduce the
bug with both of them.
** Tags added: kernel-bug-exists-upstream-5.0.0
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You rece
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done 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/1787729
Title:
apport-autorepo
Dear Christopher Penalver,
I also updated the tags and set to confirmed. Thank you for the clear
and explicit instructions!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819362
Title:
HUAWEI E3531
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 1819493
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
network loss and traffic loss problems experienced by customer with i40e
2.1.14-k in Xenial HWE Kernel 4.15
The traffic issues were reported from our customer deployments and we had Intel
helping us with the troubleshooting of the problem. Their conclusion was that
this fi
The snaps were never published in the manifest in "flat" images:
https://forum.snapcraft.io/t/no-more-preinstalled-snap-on-ubuntu-19-04/10339/7.
However, adding them is trivial and I can handle it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
March 5 was the day the glibc 2.29 migration landed in the release
pocket, bringing with it a large number of other dependent packages.
This could be due to version skew of glibc itself between the d-i initrd
and the image, or it could be a regression introduced by some other
package updated in the
The .manifest issue isn't a regression: see
https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/1819287/comments/4. However, this is valid and could be
added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I tested with linux-image-
unsigned-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb and
linux-modules-5.0.1-050001-generic_5.0.1-050001.201903100732_amd64.deb
and it still shows the same behavior:
Mär 11 18:10:01 pshp usb_modeswitch[2143]: usb_modeswitch: switched to
12d1:14dc on 1/6
https://launchpad.net/ubuntu/+source/libpdfbox2-java
** Changed in: libpdfbox-java (Ubuntu)
Status: New => Fix Released
** Package changed: libpdfbox-java (Ubuntu) => libpdfbox2-java (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Is it possible to collect dmesg?
Boot with latest Ubuntu kernel with kernel parameter "blacklist=hv_netvsc
modprobe.blacklist=hv_netvsc", then run `sudo modprobe hv_netvsc`.
Attach dmesg afterward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819438
Title:
Install fails on ppc64: partman: *** stack smashing detected ***
To manage notifications about this bug g
** Changed in: ubuntu-z-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/1814684
Title:
[19.04 FEAT] [LS1801] PCI Virtual function enablement
To ma
After some extensive testing I have further information to report that
may help solve this issue.
I can confirm that the issue exists in Lubuntu 18.04.2, Lubuntu 18.10,
Xubuntu 18.04.2 and Xubuntu 18.10, all of which use light-locker 1.8.0.
Of interest a fresh installation of the original Lubuntu
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking
Public bug reported:
After system update Nvidia proprietary driver is not working anymore.
Default 18.04 install fully updated.
Hardware: GTX 1080
Kernel: 4.15.0-46-generic
Xorg.log:
[ 5.855] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please
see the
[ 5.855] (EE) NVIDIA
** Also affects: sbuild (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: sbuild (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: sbuild (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: sbuild (Ubuntu Bionic)
Status: New =
@seb128 please see "In 16.04 the NetworkManager package used to carry
this patch..." in the bug description above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS le
** Description changed:
Doing a clean install of ubuntu server 18.10 alt install, with gpt -> mdraid
-> lvm -> btrfs. Installer completes successfully, grub-install completes
successfully, but upon first boot I receive a grub "lvmid disk not found" error
and thrown into the recovery console.
I am looking for if the patch was included before the release of mesa
"19.0.0-rc7"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815236
Title:
totem assert failure: totem: src/intel/genxml/gen9_pac
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
*** This bug is a duplicate of bug 1818519 ***
https://bugs.launchpad.net/bugs/1818519
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
This bug was fixed in the package linux - 5.0.0-7.8
---
linux (5.0.0-7.8) disco; urgency=medium
* linux: 5.0.0-7.8 -proposed tracker (LP: #1818519)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* unnecessary request_queue freeze (LP: #1815733)
-
I could check the kernel easily with dkms enabling all proposed pocket,
I had to reboot with 4.4.0-143 to check dkms installation, and after that
everything went fine.
The change is a no-op for virtualbox-hwe, since the change is in r0drv,
and that code is run only on host, but we should keep th
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572908
Title:
sssd-ad pam_sss(cron:account): Access denied for user
To manage notifications about this bug go to:
https://b
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819471
Title:
gsd-power is not using lid-close-suspend-with-external-monitor value
** Description changed:
- When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel
- 4.15.0-32.35 amd64, wifi via rtl8723be works OK.
+ === SRU Justification ===
+ [Impact]
+ Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36.
+
+ [Fix]
+ The commit that causes the
Public bug reported:
Doing a clean install of ubuntu server 18.10 alt install, with gpt -> mdraid ->
lvm -> btrfs. Installer completes successfully, grub-install completes
successfully, but upon first boot I receive a grub "lvmid disk not found" error
and thrown into the recovery console.
I kno
They could pass to [1]mesa_19.0.0~rc7
[1]
https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog
https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.
** Bug watch added: freedesktop.org Bugzilla #109535
https://bugs.freedeskt
Thank you for your bug report, that might be best reported upstream on
https://lists.gnu.org/mailman/listinfo/bug-tar
** Changed in: tar (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Also affects: openhft-chronicle-threads (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/1814133
Title:
update to openjdk 11 in 18.04 LTS
To man
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1819485/+attachment/5245477/+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/1819485
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1819485/+attachment/5245472/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819485
Title:
AMD
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1819485/+attachment/5245476/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181
201 - 300 of 616 matches
Mail list logo
