** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1832558
Added WORKAROUND 3: BIOS upgrade
Please note this workaround is permanent and cannot be reverted, unlike 1,2. So
I will not be able to test this bug anymore.
** Description changed:
Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of
booting, after
> Per the above, are we safe to grab the latest kernel upgrades now and
do away with the dis_ucode_ldr workaround in grub at this point?
Hi, no, or at least problematic.
I don't know if/why it seemed to work for me at that time. Now I was NOT able
to boot ubuntu 5.0/4.18 kernels without the
Here is the v2 patch.
** Patch added:
"v2-0001-UBUNTU-SAUCE-i2c-designware-Add-disable-runtime-p.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1833484/+attachment/5271688/+files/v2-0001-UBUNTU-SAUCE-i2c-designware-Add-disable-runtime-p.patch
--
You received this bug
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1832558
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-googleapi (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/1799619
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833484
Title:
Sometimes touchpad automatically trigger double click
To manage notifications about this bug go to:
The attachment "Set-fSocket-to--1-after-close-on-an-error-to-prevent-a
-double-close.patch" seems to be a patch. If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by a corrupted file
system, or device failure. eg. look in the logs and you'll see lots of
messages like these :-
Jun 20 02:49:58 ubuntu kernel: [ 357.585645]
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1832558
Public bug reported:
Please remove binaries and source from eoan development for neutron-
lbaas and neutron-lbaas-dashboard - projects no longer in development
and superceeded by octavia packages.
** Affects: neutron-lbaas (Ubuntu)
Importance: Medium
Status: New
** Affects:
$ diff -r /boot/efi/EFI/lubuntu/ /boot/efi/EFI/ubuntu/
$
** Summary changed:
- lubuntu grub-install puts efi in the wrong directory
+ lubuntu grub-install puts efi in the wrong directory - could make an
unbootable state
** Summary changed:
- lubuntu grub-install puts efi in the wrong
** Also affects: linux-firmware (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Eoan)
Importance: Undecided
Assignee: Hui Wang (hui.wang)
Status: New
** Also affects: linux-firmware (Ubuntu Disco)
Importance: Undecided
any update on this issue current version snap still does not include
StartupWMClass have to manually add StartupWMClass=chromium in
/var/lib/snapd/desktop/applications/chromium_chromium.desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: gnome-software (Ubuntu Bionic)
Status: Triaged => 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/1806697
Title:
Status of interface connections not properly
For Eoan, the fix is now included here:
libfm-qt (0.14.1-8ubuntu1) eoan; urgency=medium
* Merge from Debian unstable. Remaining changes:
- debian/control:
+ Update Vcs-* and maintainer for maintaining by Lubuntu.
+ Add Breaks/Replaces on old libfm-qt-l10n.
-
Public bug reported:
Lubuntu 19.04
grub-install from grub2-common 2.02+dfsg1-12ubuntu2
Summary:
The lubuntu installer puts the EFI in EFI/ubuntu. The firmware appears
to be hard coded to this path. Lubuntu grub-install puts the EFI in
EFI/lubuntu only, and NOT in EFI/ubuntu, which can result in
The fix is now released. Spinning up a new ISO as we speak.
calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium
* Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805)
* Move before_bootloader_mkdirs process before initramfs.
* Workaround bug in
** Changed in: gnome-software (Ubuntu Disco)
Status: Triaged => 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/1806697
Title:
Status of interface connections not properly
** 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
Sounds like a fix is on the way:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/626
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #643
https://gitlab.gnome.org/GNOME/mutter/issues/643
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/643
It also sounds like VirtualBox might allow me to reproduce the bug...
** Changed in: mutter (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
ubuntu is showing errno5 input/output error while installation. this is
preventing me to install ubuntu on my pc
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux
Because it was mentioned in comment #15 & #34 that this bug cannot be
reproduced, I decided to create a VMWare VM from scratch which managed
to be affected on my first attempt.
I started with ubuntu-18.04.1-desktop-amd64.iso
(19e10acddd14af9a9150399d876b02933c0ee724) and created a snapshot with
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux-oem-osp1 (Ubuntu Disco)
Public bug reported:
nvidia kernel module fails to build each kernel update.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-150.176-generic 4.4.179
Uname: Linux 4.4.0-150-generic x86_64
NonfreeKernelModules:
Public bug reported:
[Impact]
Dell machines which uses goodix touchpad IC emit double click event
while touching the touchpad if designware i2c adapter is in runtime
suspend.
Goodix re-assert the interrupt if host doesn't read the data within
100ms and designware takes a longer time to wake up
My reproducer:
1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force
the OS
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but installing kernel >=
** Changed in: mutter (Ubuntu Bionic)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but installing kernel
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion
Ubuntu 18.04 is actually the only current release that ships an old
version of PulseAudio.
Does anyone see this bug in Ubuntu 18.10, 19.04 or 19.10 ?
** Bug watch added: PulseAudio #509
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/509
** Changed in: pulseaudio
Importance:
Also, progress on this issue is now being made upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/509
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720519
Title:
KDE/Kubuntu:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-shell (Ubuntu)
Status:
This bug was fixed in the package sudo - 1.8.27-1ubuntu2
---
sudo (1.8.27-1ubuntu2) eoan; urgency=medium
* Remove d/p/keep_home_by_default.patch (LP: #1556302)
- This restores sudo handling of $HOME to what everyone else does
-- Dan Streetman Tue, 04 Jun 2019 08:58:02
-0400
** Changed in: keepalived (Ubuntu Bionic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: keepalived (Ubuntu)
Importance: Undecided => Medium
** Changed in: keepalived (Ubuntu Bionic)
Importance: Undecided => Medium
**
** Changed in: logwatch (Ubuntu Bionic)
Status: New => Triaged
** Changed in: logwatch (Ubuntu Cosmic)
Status: New => Triaged
** Changed in: logwatch (Ubuntu Cosmic)
Importance: Undecided => Low
** Changed in: logwatch (Ubuntu Bionic)
Importance: Undecided => Low
--
You
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to
freeze anymore, but network traffic stops working. Happend about 1-2
hours after a fresh reboot (after applying updates). It still answered
to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or
XMPP. After
I'm marking this a security bug, since all double close bugs can
potentially be security bugs in multithreaded programs depending on the
close interleaving.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: povray (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/1800402
Title:
See kodi issue with stack traces:
https://github.com/xbmc/xbmc/issues/16258
** Also affects: jackd2 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added:
"Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch"
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch
** Information type changed from
*** This bug is a security vulnerability ***
Public security bug reported:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
enabled by
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823441
Title:
xen ftbfs in disco
To manage notifications about this bug go to:
I tried your ibus-pinyin ppa; the problem still persists. I will explain
that in better detail later. Basically, after 18.04 (no problem there),
ibus-pinyin fails to update the hierarchy of an "entered" word or phase in
the "candidate list". This is one of the most important features of a
** Also affects: gnome-software (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: gnome-software (Ubuntu Disco)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: gnome-software (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in:
Given SRU and backport team policies, having a newer version of
keepalived in bionic seems pretty unlikely. SRU policy favors backports
of specific fixes rather than entire package backports, while the
backports team generally discourages backports of libraries or services
since they can randomly
Oh, one other thing that will be necessary to file an SRU for this would
be a a series of "paint by number" steps to reproduce the issue, and to
verify the fix. For example, something akin to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1810583/comments/12
** Also affects:
Public bug reported:
Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but
fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2.
Repro steps:
1. Create control Dockerfile:
==
FROM ubuntu:18.04
RUN apt-get update -y && \
Tested snapd-glib 1.48-0ubuntu0.19.04.0 in Ubuntu 19.04 (disco). GNOME
software able to install/remove/launch snaps (moon-buggy tested), pulse
audio still working, gnome-initial-setup showing promoted snaps.
** Tags removed: verification-needed verification-needed-disco
** Tags added:
Yes, that code fixed it. Normal Vcore has been resumed on my AsRock X470
Taichi. Thanks for the quick reply. [[ You don't have to answer, but any
idea why the existing wildcard approach doesn't pick up the Taichi chip
"nct6779-isa-0290" ? ]]
[to have your fix spelled out for others...]In
This bug was fixed in the package s390-tools - 2.9.0-0ubuntu3
---
s390-tools (2.9.0-0ubuntu3) eoan; urgency=medium
* Fix FTBFS LP: #1833238
-- Dimitri John Ledkov Wed, 19 Jun 2019 14:28:12
+0100
** Changed in: s390-tools (Ubuntu)
Status: Fix Committed => Fix Released
I went ahead and disabled the identifyObsoleteKernels function and here
is the relevant part of /var/log/dist-upgrade/main.log:
2019-06-19 15:37:29,707 DEBUG Obsolete: libisl19 libpoppler85
linux-headers-5.0.0-13 linux-headers-5.0.0-13-generic
linux-image-5.0.0-13-generic
This bug was fixed in the package s390-tools - 2.9.0-0ubuntu3
---
s390-tools (2.9.0-0ubuntu3) eoan; urgency=medium
* Fix FTBFS LP: #1833238
-- Dimitri John Ledkov Wed, 19 Jun 2019 14:28:12
+0100
** Changed in: s390-tools (Ubuntu)
Status: Fix Committed => Fix Released
So
[ 7152.173377] audit: type=1400 audit(1560925171.038:439):
apparmor="DENIED" operation="file_r50-221da1d95974" pid=18422 comm
="qemu-system-x86" family="unix" sock_type="stream" protocol=0 "
is really bothering me. This should not be possible.
operation="file_r50-221da1d95974" does NOT exist,
I also tested an upgrade from Ubuntu 19.04 to eoan and here we can see
identifyObsoleteKernels actually attempting to do something wrong -
suggesting to remove the kernel just installed. While this is because
Ubuntu 19.04 and eoan currently have the same kernel version it still
seems like an
** Changed in: dicomscope (Debian)
Status: Incomplete => 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/1656227
Title:
docomscope fails to start UnsatisfiedLinkError: no
** Tags removed: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1807479
Title:
Hashed passwords stored as MD5 hashes in /etc/shadow
To manage notifications about this bug go
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1833438
Thank you for your bug report. Could you add your 'journalctl -b 0' log after
getting the issue?
When you say that the screen goes black, are you speaking about the settings
part of the session? Does it come back after a while?
** Changed in: gnome-control-center (Ubuntu)
Importance:
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.18.0-1022.22 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
I reviewed zope.component 4.3.0-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
Zope is a free and open source web application server written in the
object-oriented programming language “Python”.
zope.component is a framework that
** Tags added: rls-dd-incoming
** Also affects: curl (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: curl (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-shell
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/1705369
Title:
Ubuntu boots to blank screen when using Nvidia (on a desktop with an
Targeted the bug to cosmic only since bionic/azure is a backport of
cosmic/azure and so will get the fix automatically.
** Also affects: linux-azure (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Cosmic)
Status: New => Fix Committed
--
You
The current development release of Ubuntu does not contain this bug so
I'm setting that task to Fix Released.
** Also affects: curl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: curl (Ubuntu Bionic)
Status: New => Triaged
** Changed in: curl (Ubuntu Bionic)
** Description changed:
+ [impact]
+
+ sudo does not set HOME to the target user's HOME
+
+ [test case]
+
+ ddstreet@thorin:~$ sudo printenv | grep HOME
+ HOME=/home/ddstreet
+
+ [regression potential]
+
+ this is a significant behavior change. As mentioned in comment 11 (and
+ later, and
** Changed in: s390-tools (Ubuntu)
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/1833238
Title:
s390-tools ftbfs in eoan
To manage notifications about
Public bug reported:
Ubuntu 19.04 fresh upgrade
Hotspot was working on Elitebook 740G2 on Ubuntu 16.04
was no longer working on Ubuntu 18.04
When Wifi is enabled, I can connect to wifi router. So wifi works
When choosing "Turn on Wi-Fi Hotspot" it pops up the dialog box if I want to
Turn on or
Public bug reported:
Motherboard: Gigabyte GA-Z170X-Gaming GT (rev. 1.0)
Description: Ubuntu 19.04
Release: 19.04
Expected behavior: Audio playback via headphones
Actual behavior: No audio playback heard
If I start Ubuntu 19.04 directly after booting my PC, there is no sound from
the front
*** This bug is a duplicate of bug 1556302 ***
https://bugs.launchpad.net/bugs/1556302
** This bug has been marked a duplicate of bug 1556302
Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by
default
--
You received this bug notification because you are a member
At the risk of posting this in the wrong place ... I encountered a crash
just like this today and I believe it's the same thing. I've got a Dell
Precision 7530 with a discrete AMD card in bypass/direct mode (the Intel
graphics are bypassed).
1. Like the original report, I connected a display to
*** This bug is a duplicate of bug 1556302 ***
https://bugs.launchpad.net/bugs/1556302
** This bug is no longer a duplicate of bug 889936
sudo(8) incorrectly says HOME is reset if env_reset is set
** This bug has been marked a duplicate of bug 1556302
Ubuntu patch to add HOME to
** Changed in: sudo (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/606195
Title:
manpage confused about mail_badpass vs always_set_home
To manage
According to this MS Documentation:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-services
The hv_fcopy_daemon have a low impact on VM.
The role of this daemon isn't necessary to a Azure VM, as you will not use it
to copy files from/to VM (This could be
Testing an upgrade from Ubuntu 18.10 to Ubuntu 19.04 I noticed that the
identifyObsoleteKernels function returns a set of linux packages which
was already identified as obsolete so dropping the functionality as
Balint suggested seems easiest.
Relevant part of /var/log/dist-upgrade/main.log:
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
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 1832082
and then change the status of the bug to 'Confirmed'.
If, due to the
It looks like the verification-done-bionic tag was added, so I don't
understand this comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832659
Title:
openssl 1.1.1-1ubuntu2.1~18.04.1 contains
Hello,
Release 20190618 is out, and has these updates.
I uploaded it to Debian unstable a few hours agoand we will issue it as
a security update as well soon.
I imagine Ubuntu will do the same.
--
Henrique de Moraes Holschuh
--
You received this bug notification because you are a member
Kernel : 4.4.0-151
-- Logs begin at mer. 2019-06-19 22:32:00 CEST, end at mer. 2019-06-19 22:40:41
CEST. --
juin 19 22:32:01 JB-Notebook kernel: microcode: microcode updated early to
revision 0x60f, date = 2010-09-29
juin 19 22:32:01 JB-Notebook kernel: Linux version 4.15.0-52-generic
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832082
Title:
bnx2x driver causes 100% CPU load
To manage notifications about this bug go to:
This was brought up previously on the bash mailing list in 2014:
https://lists.gnu.org/archive/html/help-bash/2014-03/msg00017.html
and then the readline mailing list:
https://lists.gnu.org/archive/html/bug-readline/2014-03/msg00044.html
and elsewhere:
Unsubscribed field-critical since there's a workaround to use package in
stein-proposed and fix seems to be on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826875
Title:
[stein]
I had the same exact problem with my installation. It occurred that the
solution was quite simple. Please update the bios in UX433FN to version
306 or newer (this is the one that helped me). After this update,
everything should start to work without any problems.
--
You received this bug
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797836
Title:
[SRU] logwatch reports false kernel error warning
To manage notifications about this bug go to:
** Tags removed: patch
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823441
Title:
xen ftbfs in disco
To manage notifications about this bug go to:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823441
Title:
xen ftbfs in disco
To manage notifications about this bug go to:
Hi, I have also verified that the fix works on bionic-stein, with
-proposed packages.
https://paste.ubuntu.com/p/nQgKFWxVw4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808951
Title:
python3 +
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Project changed: kernel => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833464
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Connor Kuehl (connork)
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833464
Title:
Request backports of ceph client commits to bionic kernel
To
Related fix proposed to branch: stable/stein
Review: https://review.opendev.org/666433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826419
Title:
dhcp agent configured with mismatching domain and
This bug was fixed in the package evince - 3.28.4-0ubuntu1.2
---
evince (3.28.4-0ubuntu1.2) bionic-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the
This bug was fixed in the package evince - 3.18.2-1ubuntu4.5
---
evince (3.18.2-1ubuntu4.5) xenial-security; urgency=medium
* apparmor-profile: apply hardening from Ubuntu 18.10
- add preamble for expectations of the profile
- evince{-previewer}: restrict access to DBus
I tested with xfce4-session 4.13 and virtualbox 6.0, and I can confirm
this bug. The process does not end immediately though.
VBoxSVC.log:
00:00:25.454822 main VirtualBox: object deletion starts
00:00:25.803381 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005)
Looks like this is fixed upstream with commit
27751d89248c8c5eef6d8b56eb8f7d2084145080.
Upstream patch is attached; this would need applied to cosmic, disco,
and eoan.
** Patch added:
"0001-tools-misc-fix-hypothetical-buffer-overflow-in-xen-l.patch"
1 - 100 of 430 matches
Mail list logo
