https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt
seems to suggest you have packages from multiple Ubuntu releases
installed. If this can be confirmed, then this is more of a support case
than a bug in the software.
This said, more robust handling by the release upgrader
--- Comment From hbath...@in.ibm.com 2019-05-10 13:25 EDT---
Right, Cascardo.
nr_cpus=1 for KDump case has never worked before on ppc64. Mahesh
tried fixing it but the maintainer had a few apprensions and rightly so.
This fix doesn't work in all cases. Say, KVM host (baremetal with SMT
Public bug reported:
I had logged bug 1828569 and then ran this test to provide the
driver/hardware info.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=102475.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This issue was fixed in the openstack/horizon 14.0.3 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806053
Title:
APITestCase still needs to be patched
utils.patch_middleware_get_user()
The attachment "v4l2loopback_0.10.0-1ubuntu1.1.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
This bug was fixed in the package kbd - 2.0.4-4ubuntu2
---
kbd (2.0.4-4ubuntu2) eoan; urgency=medium
* kbd_mode: Add -f option and don't perform dangerous mode switches without
it. In the back-ported fix kbd_mode exits with success, even when the
dangerous mode change is
Ok thanks, please look at this some more, I will try to get back with
you soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard
Thanks for forwarding your change upstream, it looks like they've
incorporated the systemd-logind log handling, via commits dcb79597 and
44d6719b (the latter including mention of your patch), which are now
included in the 7.5.0 release. So, I think we can close this bug as
fixed in eoan. 14.04.6
So; this has landed in Eoan now, and also in -proposed repositories for
18.04, 18.10, 19.04. I'll start doing testing on these releases, but
since I don't have an openvswitch setup, any and all further independent
confirmation that the issue is fixed (or indeed, if it's not), is
welcome.
--
You
Being fixed in upstream
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-
next-5.2=2e26ccb119bde03584be53406bbd22e711b0d6e6
Maybe a candidate for SRUs too after the fix hits eoan (19.10).
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=108514
Importance:
For the xenial->bionic question, I had already implemented the
workaround mentioned here to use Dpkg::Options::="--force-confdef"
across all upgrade tests, which has been working fine. I can remove the
workaround and try it if you are specifically interested in finding out
whether it's necessary
This bug was fixed in the package cloud-init - 19.1-0ubuntu1
---
cloud-init (19.1-0ubuntu1) eoan; urgency=medium
* New upstream release.
- release 19.1 (LP: #1828479)
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
Commits 32adbfdd and 3abbb24d address this issue, and both are included
in upstream's 7.5.0 release, which is packaged for and released in
Ubuntu disco (19.04). We can consider this fixed now.
** Changed in: logwatch (Ubuntu)
Status: New => Fix Released
--
You received this bug
I was able to recreate this today by taking a stock cosmic lxc image,
installing ubuntu-mate-desktop, and then upgrading to disco. Here's the
DuplicateSignature from the crash:
== DuplicateSignature =
package:libvlc-bin:3.0.6-1
Setting up fontconfig
** Branch linked: lp:ubuntu-docs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827788
Title:
Add #ubuntu as 'get more help' resource in the docs
To manage notifications about this bug go to:
This part might have something to do with the issue:
sudo add-apt-repository ppa:jonathonf/python-3.6
sudo apt-get update
sudo apt-get install python2.7-dev python3.5-dev python3.6-dev pylint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dub (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/1828466
Title:
Dub
Public bug reported:
When I switch to wayland the gnome desktop locks up before I see my desktop.
It doesn't lock up when I have my laptop closed and only one display connected.
When I connect up the second display, it locks up every time.
I tried deleting my monitors.xml file.. that doesn't
This bug is believed to be fixed in cloud-init in version 19.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 19.1. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Public bug reported:
[ Impact ]
The DKMS package fails to install on kernels based on 5.0; specifically
noticed in the Bionic HWE Edge kernel.
[ Test Case ]
Install the v4l2loopback-dkms package with a 5.0 kernel. The package
should install without any errors.
[ The Problem ]
Okay, let's consider this option on makedumpfile side. I'll test it and
provide a test package by next week.
Cascardo.
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Eoan)
Importance: Undecided => High
** Changed in:
Reported upstream as
https://github.com/solus-project/brisk-menu/issues/117 (deprecated)
https://github.com/getsolus/brisk-menu/issues/8
** Bug watch added: github.com/solus-project/brisk-menu/issues #117
https://github.com/solus-project/brisk-menu/issues/117
** Bug watch added:
** Description changed:
[ Impact ]
The DKMS package fails to install on kernels based on 5.0; specifically
noticed in the Bionic HWE Edge kernel.
[ Test Case ]
Install the v4l2loopback-dkms package with a 5.0 kernel. The package
should install without any errors.
+
+ [
Public bug reported:
Can you disable cntlm from logging every connection to the systemd
journal log?
I did not see an option to turn it off the excess logging.
Thanks!
** Affects: cntlm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
--- Comment From mranw...@us.ibm.com 2019-05-10 17:33 EDT---
>From the opal-utils package can you try: sudo opal-gard list? I think if
>there's something there you can use opal-gard show to get more details.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The linux-image-4.15.0-49-generic (currently in bionic-proposed) can be
made to crash in a kvm guest with memory pressure. The reproducer used
is to attempt to run netbeans with openjdk-8-jre installed as the only
jvm. It will fail to run, and when it fails, it also causes
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.5
---
ubuntu-release-upgrader (1:19.10.5) eoan; urgency=medium
* DistUpgrade/DistUpgradeViewNonInteractive.py: when responding to a
conffile prompt with "n" use bytes not a string. (LP: #1796193)
*
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815123
Title:
Hardware test stress-ng-cpu-long bind failed
To manage notifications about
List of commits needed to enable ARCH_CAPABILITIES:
Kernel:
commit 2bdb76c015df7125783d8394d6339d181cb5bc30
Author: Xiaoyao Li
Date: Fri Mar 8 15:57:20 2019 +0800
kvm/x86: Move MSR_IA32_ARCH_CAPABILITIES to array emulated_msrs
QEMU:
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8
** Changed in: sosreport (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828467
Title:
[sru] remove juju-db stop/start service interactions
To manage
To elaborate more I seen the following in the console output of a job
which upgrades from bionic to cosmic:
Setting up ubuntu-release-upgrader-core (1:18.10.11.6) ...
Configuration file '/etc/update-manager/release-upgrades'
==> Modified (by you or by a script) since installation.
==> Package
I marked Trusty as 'Won't Fix' as it reached EOL.
** Description changed:
[Impact]
The juju plugin will stop and start the juju-db service during data
collection.
sosreport should not impact running services, or attempt to recover them.
This has been reported upstream[0] and will
I marked Trusty as 'Won't Fix' in it reached EOL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828467
Title:
[sru] remove juju-db stop/start service interactions
To manage notifications about
Well I'm fairly certain this issue, DistUpgradeViewNonInteractive not
being non-interactive, is contributing to automatic upgrade testing so
I'll be SRU'ing this change everywhere.
** Summary changed:
- unattended do-release-upgrade asks about /etc/cron.daily/apt-compat
+
And I guess the solution is in deleting "exit 1" on line 120 of bionic
ppa-purge script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828625
Title:
Can't purge if apt-get update fails (18.04)
To
Public bug reported:
I want to purge buggy ppa that makes apt-get update to report error, but
I can't because apt-get update reports error. It's a circle.
I can remember a good times when ppa-purge didn't call for apt-get
update at all (or that was "add-apt-repository", don't remember...). And
** Description changed:
- I'm trying to do some automated testing that involved upgrading a system
- from xenial to bionic, so I need it to not ask for user input.
+ [Impact]
+ The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard
to automate upgrade testing.
+
+ [Test
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command. Results was as you predicted. The pactl outputs before
and after appear below.
Here's the before output:
Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner
What magic is required to get into safe graphic mode from the Disco live
USB? (normal boot on that version fails in the same way)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828568
Title:
Ubuntu
Hello Zhixin, or anyone else affected,
Accepted neutron into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neutron/2:13.0.2-0ubuntu3.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
This is a follow on from https://bugs.launchpad.net/ubuntu/+source
/cloud-init/+bug/1802073 + its fix in: https://git.launchpad.net/cloud-
init/commit/?id=0bb4c74e
After a clean launch of Ubuntu 18.04.2 on a t3.small AWS EC2 instance,
in a VPC in the eu-west-1 region, we can
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~rbalint/livecd-rootfs/+git/livecd-rootfs/+merge/367293
** Merge proposal linked:
https://code.launchpad.net/~rbalint/livecd-rootfs/+git/livecd-rootfs/+merge/367294
--
You received this bug notification because you are a member of
Hello folks,
revisiting. Rejoice! Progress has been made.
*
https://source.winehq.org/git/wine.git/commitdiff/2aa494686133bf4c4b6b054a45bf1d1d429acdc5
("mspatcha: Add functions to API header file.")
*
https://source.winehq.org/git/wine.git/commitdiff/8695a6986ef2b7cae7c1f3247fec8e8e14de1971
** Changed in: xfce4-session
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/1766765
Title:
xflock4 fails if light-locker installed in /usr/local/bin
To
Public bug reported:
Hello.
update-notifier runs too often on a Ubuntu. According to sources
(update-notifier.c) utility check updates every 10 minutes:
// the timeout (in sec) when a further activity from dpkg/apt
// causes the applet to "ungray"
#define TIMEOUT_APT_RUN 600 /* 600 sec */
As
same problem here. don't know where this is coming from but it maybe
related to this:
https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f
my system (inxi -Fxz):
System:Host: Work Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: Xfce 4.12.3 (Gtk
I have committed a tiny "Community support" page, which I think can be
considered to address this bug:
https://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-
docs/trunk/revision/72/ubuntu-help/C/community-support.page
The page will be added to the "Get more help" section of the desktop
guide.
**
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
nautilus. This problem was most recently seen with package version
1:3.26.4-0ubuntu7.2, the problem page at
https://errors.ubuntu.com/problem/b602a0d844bdf5a495f5843d042e2f2b9dbb58d0
contains
** Changed in: ubuntu-power-systems
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/1828597
Title:
KDump boot fails with nr_cpus=1
To manage notifications about this
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823836
Title:
dpdk app is
I confirmed that if we compress the kernel (as Seth's patch does), the
5.0 kernel would boot fine on the HP m400[*]. I chatted w/ apw about
this and we agreed that a respin isn't necessary because LP showed that
there is no current linux-hwe-edge package in bionic, and therefore
introducing one
Removed symbolic links:
/usr/share/pykaraoke/fonts/DejaVuSans.ttf
/usr/share/pykaraoke/fonts/DejaVuSansCondensed.ttf
/usr/share/pykaraoke/fonts/DejaVuSansCondensed-Bold.ttf
Copyed instead fonts in /usr/share/pykaraoke/fonts/
Works fine.
** Package changed: linux (Ubuntu) => pykaraoke (Ubuntu)
A patched version of the ubuntu neutron package has been uploaded to the
cosmic unapproved queue [1] where it is awaiting SRU team review.
[1]
https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1_text=neutron
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pcs (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/1826045
Title:
Well ok but those are currently deleted downstream anyway by
https://github.com/tianon/docker-brew-ubuntu-core/blob/master/update.sh#L91.
Do you want to submit a patch there and then we can patch it here too? In
the mean time I still would like to release this change.
On Fri, 10 May 2019, 19:30
Reviewed: https://review.opendev.org/658404
Committed:
https://git.openstack.org/cgit/openstack/charm-nova-compute/commit/?id=d33fa57b40994483cf88f338a4d000e06aaf6cc5
Submitter: Zuul
Branch:stable/19.04
commit d33fa57b40994483cf88f338a4d000e06aaf6cc5
Author: Corey Bryant
Date: Thu May 9
** Changed in: calamares
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/1826628
Title:
Lubuntu fails to install when disk/RAM sizes equal minimum
requirements
** Changed in: charm-nova-compute
Milestone: None => 19.04
** Changed in: charm-nova-compute
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/1828259
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/1828632
Title:
bionic i386 kernel crashes in memory
This is now processed, and heartbeat is showing as a universe package:
heartbeat | 1:3.0.6-9| disco | source, amd64, arm64, armhf,
i386, ppc64el, s390x
heartbeat | 1:3.0.6-9ubuntu1 | eoan/universe | source, amd64, arm64, armhf,
i386, ppc64el, s390x
Also confirmed showing in
It seems the security team was no longer assigned, but we knew this was
coming so I performed the security team MIR.
I reviewed xdg-dbus-proxy 0.1.1-1 as checked into eoan. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
xdg-dbus-proxy is a "filtering
Public bug reported:
Encountered when upgrading from cosmic to disco with ubuntu-mate-desktop
installed.
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: libvlc-bin 3.0.6-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion:
Public bug reported:
Several sane backends provide the option --scan-area to guarantee the
scan is correctly aligned, even if the scan area with automatic document
feeder (ADF) is right-aligned in contrast to the flatbed of the same
device, which is normally left-aligned.
Currently SimpleScan
--- Comment From leona...@ibm.com 2019-05-10 19:54 EDT---
Hello Juerg,
As this complete list was suggested by Paul, I think he may be the best
person to show the context of the patch series.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, i forgot to report back. Thank you for asking.
No, i got my SSD replaced by a new one and now it is all good.
Seems like it has been a hardware-related problem.
Am 10.05.2019 um 17:26 schrieb Kai-Heng Feng:
> Do you still see this bug?
>
--
You received this bug notification because you
On Fri, May 10, 2019 at 08:13:47PM -, Paul Larson wrote:
> For the xenial->bionic question, I had already implemented the
> workaround mentioned here to use Dpkg::Options::="--force-confdef"
> across all upgrade tests, which has been working fine. I can remove the
> workaround and try it if
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827441
Title:
ubuntu-release-upgrader crashed with configparser.NoOptionError: No
option 'devrelease'
** Attachment added: "(adding attachments to illustrate)"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262991/+files/VID_20190509_224648.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for your bug report, the issue looks like an upsream one
though, maybe you could report it to them on
https://gitlab.gnome.org/GNOME/gvfs/issues ?
** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu)
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
--
You received this
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1828358/+attachment/5262987/+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/1828358
apport information
** Tags added: apport-collected
** Description changed:
Having enabled fractional scaling on X11, I have a lot of issues with
returning to a hw-suspended session, re-login screen becomes a black rectangle,
and windows are being resized and there are black rectangular
** Attachment added: "(adding attachments to illustrate)"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262989/+files/MVIMG_20190509_110046.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "(adding attachments to illustrate)"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262990/+files/MVIMG_20190510_225124.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1828358/+attachment/5262986/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
https://bugs.launchpad.net/bugs/1828358/+attachment/5262988/+files/modified.conffile..etc.apport.crashdb.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The before file was attached to the last comment. Here's the after file
from pactl.
** Attachment added: "postforce"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce
--
You received this bug notification because you are a member of
** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/ubuntu-release-
upgrader/disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796193
Title:
DistUpgradeViewNonInteractive crashes / requires
Trent, Thanks that does work. Now on to seeing how to addd the txt
attributes for scanner features and such, hopefully this too is
attainable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828516
Does this kernel supports Killer 1435, 1435s and 1535 wireless cards ?
>> linux-image-generic-hwe-18.04 = 4.18.0.17.67
Or support for this wifi cards available in 5.x kernel, please specify.
Note:- As per killer networking, they haven't mentioned about 18.04
Does any of the linux-firmware supports these killer wifi driver ?
http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/
Issue:- Intermittently reconnection / sometime freezing issue. Mostly
seeing this in home network.
--
You received this bug notification because you are a member
.debdiff attached to this comment.
To fix this, I've backported this patch:
https://github.com/umlaeute/v4l2loopback/commit/afe0b233070d7ca5d6df83c5f2723d276dcd287d.patch
No context adjustments were required.
[ Testing ]
I tested this install process for both 4.15.0-49-generic and
Public bug reported:
Ubuntu 18.04.2 Ceph deployment.
Ceph OSD devices utilizing LVM volumes pointing to udev-based physical devices.
LVM module is supposed to create PVs from devices using the links in
/dev/disk/by-dname/ folder that are created by udev.
However on reboot it happens (not
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.5
---
ubuntu-release-upgrader (1:19.10.5) eoan; urgency=medium
* DistUpgrade/DistUpgradeViewNonInteractive.py: when responding to a
conffile prompt with "n" use bytes not a string. (LP: #1796193)
*
In discussing this with Tyler Hicks, he noted that is a somewhat similar
i386 PTI failure report:
https://lore.kernel.org/lkml/14206a19d597881b2490eb3fea47ee97be17ca93.ca...@sympatico.ca/
and that the response to it needs fixes from the tip/x86/mm branch. Is
it possible that the bionic PTI i386
** Description changed:
+ NOTE: This SRU template was added 2019-05-10 after the original report
+ was opened and was fixed for Disco. I'm adding this because this problem
+ is affecting the Bionic HWE Edge kernel this SRU cycle. -connork
+
+ [Impact]
+
+ * The DKMS package fails to install on
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828639
Title:
package libvlc-bin 3.0.6-1 failed to install/upgrade: 90.8592:triggers
looping, abandoned
To
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
mc. This problem was most recently seen with package version 3:4.8.21-1, the
problem page at
https://errors.ubuntu.com/problem/e64af00a2e85e4cc01804ca4b41cea18270e4eab
contains more details,
** Description changed:
[Impact]
The juju plugin will stop and start the juju-db service during data
collection.
sosreport should not impact running services, or attempt to recover them.
This has been reported upstream[0] and will be fixed by the juju 2.x
refactor[1]
This is
This is still verification-done; has not changed in releases: this SRU
is a backport that includes the same upstream patch as what was
previously cherry-picked in the previous round of SRUs; hence it
appearing again in changelog.
** Tags removed: verification-needed verification-needed-bionic
tags adjusted - thx David
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823836
Title:
dpdk app is reporting: net_mlx5: probe of PCI device aborted
after encountering an error: Unknown error
** Also affects: pcs (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: pcs (Ubuntu Disco)
Status: New => Confirmed
** Changed in: pcs (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: pcs (Ubuntu Disco)
Importance: Undecided => High
** Changed
Thanks Tom. I will check whether I have multiple Ubuntu releases on
that computer and if so may submit a separate bug report as suggested.
John Bell
On 5/10/19 1:20 PM, Tom Reynolds wrote:
> https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt
> seems to suggest you have
Unfortunately, this bug occurred to me again in Kubuntu 18.04 / KDE
Plasma 5.12.7 when setting language to English and region to
Netherlands. Locale is then set to en_NL.UTF-8 which is invalid, causing
rendering issues in konsole, screen, for example.
--
You received this bug notification
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- Azure: Return static fallback address as if failed to find
Eduardo is taking a look at this package for the security team and
pointed out that it is doing a setuid to user 'nobody'.
This isn't a safe design. User nobody is strictly for NFS's use and must
not be used by any running processes on the system.
This service probably needs its own user
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/367301
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
--
You received this bug
1 - 100 of 455 matches
Mail list logo
