** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
--
For the commit mentioned in the test case:
* The problem has been fixed by commit:
* 764baba80168 "ovl: hash non-dir by lower inode for fsnotify"
In commit 764baba80168, it stated that:
The issue dates back to initial version of overlayfs, but this
patch depends on ovl_inode co
*** This bug is a duplicate of bug 1016823 ***
https://bugs.launchpad.net/bugs/1016823
** This bug has been marked a duplicate of bug 1016823
thunderbird crashed with SIGSEGV in i915_set_draw_region()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Both Ubuntu and Thunderbird versions now long time EOL. Re above comment
and amount of time that has elapsed since I'm closing this by marking as
"Invalid".
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of U
vlotho and anyone else affected,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu and Thunderbird since that
time.
Do you still see a problem related to the one that
Public bug reported:
On system installation, whether I let the system create the partitions
or if I create EFI and system partitions, I can't get this to succeed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Un
A few minutes ago Firefox crashed again several times in a row. This is
the tail of /var/log/kern.log right now (lots of times):
e_~dThread[15841]: segfault at 0 ip 7fc94cabac91 sp 7fc944914ac0 error
6 in libxul.so[7fc949715000+48b5000]
Nov 15 11:37:12 x1cbn kernel: [ 8970.728562] Code: 8
The issue seems to be that in Cosmic the libboost-python lib naming
convention has changed and that affects the debian rules scripts picking
the correct lib python version.
Bionic: /usr/lib/x86_64-linux-gnu/libboost_python-py36.so.1.62.0
Cosmic: /usr/lib/x86_64-linux-gnu/libboost_python36.so.1.67.
This happened to me after upgrading to ubuntu 18.10 , i was previously
using the PPA version and the upgrade commented it out, it then
installed a newer version of remmina during the upgrade. to fix this i
needed to uncomment the ppa definition in my
/etc/apt/sources.list.d/remmina-ppa-team-ubuntu
Roi,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Do you still see a problem related to the one that you reported?
Please let us know if you do
On trusty :
- apt install ghostscript, upgrades only ghostscript and libgs9 but NOT
libgs9-common :
jo@trusty-build:~$ dpkg -l | grep ghostscript
ii ghostscript 9.25~dfsg+1-0ubuntu0.14.04.1
amd64interpreter for the PostScript language and for PDF
jo@tr
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
** Summary changed:
- freeplane didn't show interface
+ bionic SRU for freeplane [was: freeplane didn't show interface]
** Summary changed:
- bionic SRU for freeplane [was: freeplane didn't show interface]
+ Bionic freeplane SRU [was: freeplane didn't show interface]
--
You received this bug n
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verifica
Axel,
Thank you for reporting this bug to Ubuntu. We are sorry that we do not
always have the capacity to look at all reported bugs in a timely
manner.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com
I already switched back to Thunderbird. TB has its issues, too. But I
can use it as a productive tool. Unfortunately, evolution is not usable
in a professional environment at this stage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
murtyvonna and anyone else affected,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu and Firefox since that time.
Do you still see a problem related to the one that
I'm having the same issue. The login screen appears after I press
ctrl+alt+f2 and then ctrl+alt+f1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798790
Title:
Ubuntu 18.10 login screen never appea
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbolt runtime D3 and PCIe D3 Cold support (LP: #1800770)
- ACPI / hotplug / PCI: Don't scan
[Impact]
* freeplane depends on knopflerfish-osgi (libknopflerfish-osgi-framework-java)
as OSGi runtime
* libknopflerfish-osgi-framework-java 6.1.1-2 does not set source and
target level for java. Thus, it will use "11" (or "1.11") when compiled
with OpenJDK11 (the default in bionic).
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbolt runtime D3 and PCIe D3 Cold support (LP: #1800770)
- ACPI / hotplug / PCI: Don't scan
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbolt runtime D3 and PCIe D3 Cold support (LP: #1800770)
- ACPI / hotplug / PCI: Don't scan
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbolt runtime D3 and PCIe D3 Cold support (LP: #1800770)
- ACPI / hotplug / PCI: Don't scan
*** This bug is a duplicate of bug 1800788 ***
https://bugs.launchpad.net/bugs/1800788
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbol
This bug was fixed in the package linux-oem - 4.15.0-1026.31
---
linux-oem (4.15.0-1026.31) bionic; urgency=medium
* linux-oem: 4.15.0-1026.31 -proposed tracker (LP: #1800788)
* Thunderbolt runtime D3 and PCIe D3 Cold support (LP: #1800770)
- ACPI / hotplug / PCI: Don't scan
** Changed in: snapd
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/1772844
Title:
snapd didn't initialize all the seeded snaps
To manage notifications about this
--- Comment From heinz-werner_se...@de.ibm.com 2018-11-15 06:17 EDT---
Our latest date to have the kernel patches applied to 18.04.1(kernel 4.15) is
the December SRU, because we have long lasting customer service durations as
well as an ongoing customer PoC.
For testing reason , we do nee
Ive also noted the revert and have now my servers complaining about
that. Should we wait for 0.40.2 or should we manually downgrade to
0.36.3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793309
Tit
Doesn't appear to have been a Firefox issue so marking as "Invalid" to
close.
** Changed in: firefox (Ubuntu)
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/943
Marking as "Fix Released" as 3 users affected and reporter said issue
fixed five years ago.
** Changed in: firefox (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.launchpa
I managed to fix this by installing a BIOS upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803525
Title:
Grub install fails on Dell PowerEdge T110 II
To manage notifications about this bug
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
Here is the changelog entry for the SRU:
knopflerfish-osgi (6.1.1-2ubuntu1) bionic-updates; urgency=medium
* Build with source=1.7 and target=1.7 (LP: 1800147)
-- Felix Natter Mon, 12 Nov 2018 14:30:53 +0100
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
I have Hungarian and English keyboard layouts set up.
However at the login screen it's English and Afghan. Have no idea why. It
changed at some point during 18.04.
$ grep XKBLAYOUT /etc/default/keyboard
XKBLAYOUT="us,af"
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
In order to respect the local initscript policy layer that may be
present in /usr/sbin/policy-rc.d, the postinst script of the udev
package should use "invoke-rc.d stop" instead of "systemctl stop".
This direct systemctl call can be found in the handle_service_rename()
functi
@albertomilone here is my gpu-manager.log this is a fresh install and
all updates have been made
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5213084/+files/gpu-manager.log
--
You received this bug notification becaus
Thanks for the not-too conflicting patch series.
I gave it a try and must agree that it seems backportable reasonably (checked
only qemu for now).
To me it looks safe in terms of not affecting other use cases, nor other
architectures.
It also looks safe for upgrades/migrations not affecting acti
shinyblue,
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing i
** Also affects: boost1.67 (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/1800264
Title:
python3-libtorrent linking libboost_python27.so instead o
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jesse Sung (wenchien)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803335
Title:
linux-headers-4.18.0-1004-azure contains links to non-
Sorry wrong file this is the file with the $ prime-select intel
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5213087/+files/gpu-manager.log
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug was fixed in the package linux-aws - 4.18.0-1004.5
---
linux-aws (4.18.0-1004.5) cosmic; urgency=medium
* linux-aws: 4.18.0-1004.5 -proposed tracker (LP: #1801114)
* Update ENA driver to version 2.0.1K (LP: #1798182)
- net: ena: remove ndo_poll_controller
- net:
Public bug reported:
Fontconfig 2.13.0 changed the cache file naming scheme to be based on
the contents of ".uuid" file in the directory rather than a hash of the
directory name. On a pure debs system this doesn't really matter since
everything is using the same libfontconfig.so.
When snaps are
Sorry, i missed comment #29, but there are a lot of bug reports out
there, some of them over a year old, which describe the same issue.
My reproduction steps, tested on a virtualbox machine:
1) Fresh-Install Ubuntu 18.0.4.1 LTS
2) Install package 'chrome-gnome-shell'
3) Navigate to https://extens
This bug was fixed in the package linux-aws - 4.18.0-1004.5
---
linux-aws (4.18.0-1004.5) cosmic; urgency=medium
* linux-aws: 4.18.0-1004.5 -proposed tracker (LP: #1801114)
* Update ENA driver to version 2.0.1K (LP: #1798182)
- net: ena: remove ndo_poll_controller
- net:
This bug was fixed in the package linux-kvm - 4.18.0-1004.4
---
linux-kvm (4.18.0-1004.4) cosmic; urgency=medium
* linux-kvm: 4.18.0-1004.4 -proposed tracker (LP: #1799453)
[ Ubuntu: 4.18.0-11.12 ]
* linux: 4.18.0-11.12 -proposed tracker (LP: #1799445)
* arm64: snapdragon: W
** 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 associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kern
This bug was fixed in the package linux-gcp - 4.18.0-1003.4
---
linux-gcp (4.18.0-1003.4) cosmic; urgency=medium
* linux-gcp: 4.18.0-1003.4 -proposed tracker (LP: #1799452)
* Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox
modules (LP: #1796647)
-
A backport of the UUID cache file directory feature from fontconfig
2.13.
** Patch added: "fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff"
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+attachment/5213086/+files/fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff
--
You rece
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
** 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 associated workflow s
So the backward compatibility links were broken in libboost_python 1.67:
https://salsa.debian.org/debian/boost/commit/264a065b6996f87b3825afdc679474faff78d748#8756c63497c8dc39f7773438edf53b220c773f67_185_182
There is the new:
libboost_python$(py3default).so
The old:
libboost_python3-py$(py3def
This needs fixes in both qtbase and qttools. In addition, I will upload
a no-change rebuild of qtdeclarative to demonstrate that the fix works.
Updating the description accordingly.
** Description changed:
[Impact]
The packaged Qt documentation, which can be viewed in browser (qt*-doc-html
valentina,
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Do you still see a problem re
101 - 200 of 644 matches
Mail list logo
