Found on node baltar with 5.3.0 Bionic 5.3.0-40.32~18.04.1
** Tags added: 5.3 sru-20200127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842032
Title:
cpufreq_boost from kernel_misc in ubuntu_ltp
@kaihengfeng. I just tried the latest 5.6.0-050600rc1_but the problem is
still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861554
Title:
Radeon mobility HD3450 (RV620) heavy screen
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
** 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
SRU Bugs:
https://bugs.launchpad.net/ubuntu-kernel-
tests/+bugs?field.tag=sru-20200127+azure_combinator=ALL
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Version 1.3.4.20200120-1 was updated in Debian and migrated to testing
on January 31th.
Please sync that version to Focal, the current version in the archive is
from 2012!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Impact
==
Under most circumstances, the impact is minimal (a few extra redundant
comment lines in apt sources. However, if users are automating source
removal / addition on a machine (as in comment 11), there is the
potential to wind up with an
Here is an ACPI dump on a Dell Latitude 5590 with kernel 5.5.3.
** Attachment added: "ACPI dump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806437/+attachment/5327674/+files/acpi-dump.bin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
With mawk 1.3.4.20200120-1 being uploaded to Debian testing now I
suggest to mark this bug here as invalid and just sync the new mawk
version to Focal. There is a separate bug for just updating mawk
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114 Let's follow
up there...
** Changed
@joseph, unlinked your bug 1858810 from this one. Please move the
discussion there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853369
Title:
[19.10] Boot hangs at "loading initial ramdisk"
To
** Changed in: apport (Ubuntu Trusty)
Status: New => Fix Committed
** Changed in: apport (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been using the mainline kernel (5.4.5, specifically) for a few
weeks with no instability; I switched back to the -proposed kernel ~a
week ago and I've since seen this issue recur. The version I saw this
recur on was 5.4.0-13-generic (and I'm now on -14 as a result of the
forced reboot).
Is
I don't know what the way forward is to resolve this issue. While
upstream qemu has added some new CPU models, "Skylake-Client-noTSX-
IBRS", "Skylake-Server-noTSX-IBRS", etc, libvirt has not. If I do add
these to libvirt, we will need to carry them forward as a delta to
upstream possibly forever.
Public bug reported:
I'm using Ubuntu 19.10 64bit for my PC. For network/wifi I'm using TP-
Link wifi adapter.
My network works only when I do a fresh start (That is completely shutdown and
start).
But network connection fails to connect to my wifi on REBOOT(on system software
updates ,
So next step, @Joseph, I'll need the version of intel-microcode
currently installed on your system to determine to find out a working
revision for you.
** Changed in: intel-microcode (Ubuntu)
Status: New => In Progress
** Changed in: intel-microcode (Ubuntu)
Assignee: (unassigned) =>
Another possible duplicate in bug 1858810.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862751
Title:
Hard lockups using microcode releases 20191115 on Intel Whiskey Lake
To manage notifications
Based on comments #20 to #23 in bug 1853369, I think the root cause for
Joseph's device is a regression in intel-microcode package. While I
don't have enough info to determine whether bug 1853369 actually shares
the same root cause, the duplication relationship is removed so that I
can work on
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
A few attachments originally sent to bug 1853369:
* boot sequence photos:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853369/+attachment/5327640/+files/sequence.7z
which has last line "printk: bootconsole [efifb0] disabled" that
shares the same symptom as bug 1862751.
* microcode
I have the hardware. What do I need to do in order for this to be
accepted and pushed to the repositories?
And a side note is that this is fixed upstream, just upgrading to v0.7.2
will fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
The xenial/queens fix got tangled with some following SRU work but its
all now released.
** Changed in: cloud-archive/rocky
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4~cloud0
---
ceph (12.2.12-0ubuntu0.18.04.4~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium
.
[ Billy Olsen ]
* Do
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4~cloud0
---
ceph (12.2.12-0ubuntu0.18.04.4~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium
.
[ Billy Olsen ]
* Do
This bug was fixed in the package ceph - 12.2.12-0ubuntu0.18.04.4~cloud0
---
ceph (12.2.12-0ubuntu0.18.04.4~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
ceph (12.2.12-0ubuntu0.18.04.4) bionic; urgency=medium
.
[ Billy Olsen ]
* Do
This bug was fixed in the package ceph - 13.2.7-0ubuntu0.18.10.1~cloud0
---
ceph (13.2.7-0ubuntu0.18.10.1~cloud0) bionic; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive (LP: #1855859)
including fix for ceph-volume performance issues (LP: #1850754):
This bug was fixed in the package ceph - 13.2.7-0ubuntu0.18.10.1~cloud0
---
ceph (13.2.7-0ubuntu0.18.10.1~cloud0) bionic; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive (LP: #1855859)
including fix for ceph-volume performance issues (LP: #1850754):
** 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
-- swm properties --
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
The verification of the Stable Release Update for ceph has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
** 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
-- swm properties --
The only other Pi that I currently have is a 3B which does not have
802.11ac capabilities.
https://www.raspberrypi.org/documentation/faqs/#hardware
--
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: grub-installer (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/1862491
To be usable under sudo, the changes for this also require bug 1862948
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645404
Title:
Support Private PPAs
To manage notifications about this bug go
It certianly seems I do something wrong, but `apport-collect 1862962`
sends nothing to Launchpad. So I manually attach apport's file generated
for the package.
** Attachment added: "_usr_bin_anbox.log"
Ocata is a few days off EOL so marking bug task as won't fix.
** Changed in: cloud-archive/ocata
Status: Triaged => 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/1776375
Title:
I've committed this fix to the git repo for OVN for bionic, however
there is no point in uploading it without another fix or point release
as its related to package upgrade.
** Changed in: openvswitch (Ubuntu Bionic)
Assignee: (unassigned) => James Page (james-page)
** Description changed:
** Changed in: openvswitch (Ubuntu Cosmic)
Status: Triaged => 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/1823295
Title:
openvswitch-switch package upgrades restart daemons
I tested with a Dell D3100 dock and two monitors connected to the dock
via HDMI in addition to laptop built-in screen. I did this on Ubuntu
19.10 with the libmutter fix from eoan-proposed (libmutter-5-0 package
version 3.34.3-1ubuntu1~19.10.1).
I tried unplugging and hotplugging each HDMI cable
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378958
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1862947
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
A test package (including the above fix) is available on my PPA:
sudo add-apt-repository ppa:slashd/lp1794478
sudo apt-get update
@juergh given the Pi 3A+, 3B+, and 4B share the same wifi chipset (but
not the 3B) I'd expect similar behaviour across those three models, if
indeed the firmware is the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378958
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862947
Title:
crmsh
Public bug reported:
mymedia@freesia:~$ anbox session-manager
[ 2020-02-12 14:25:41] [session_manager.cpp:130@operator()] Failed to start as
either binder or ashmem kernel drivers are not loaded
mymedia@freesia:~$ ANBOX_LOG_LEVEL=debug anbox session-manager
[ 2020-02-12 14:25:45]
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378958
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1862947
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
5.3.0-40.32 - generic
Regression test CMPL, RTB.
57 / 60 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4,
ubuntu_xfstests_xfs
Issue to note in amd64:
ubuntu_bpf - test failed to build (bug 1862263)
ubuntu_kernel_selftests - test failed to build (bug 1862263)
** Changed in: bionic-backports
Status: In Progress => 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/1838607
Title:
vaultlocker service fails when some interface are DOWN with
** 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
-- swm properties --
** Changed in: cloud-archive/stein
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/1831986
Title:
fwaas_v2 - unable to associate port with firewall (PXC
*** This bug is a duplicate of bug 1859485 ***
https://bugs.launchpad.net/bugs/1859485
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1859485, so is being marked as such.
** Attachment added: "Ubuntu generated one"
https://bugs.launchpad.net/ubuntu/+source/emboss/+bug/1862960/+attachment/5327672/+files/ubuntu.svg
--
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
-- swm properties --
Same issue as reported in the Bug, with some diffs:
Laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. [SAME]
Distro: Linux Mint 19.3 MATE 64bit; base: Ubuntu 18.04 bionic.[UPDATE]
This happen trying any distro. I tried Ubuntu 18.04.3, ElementaryOS.
--
I'm also stuck with
Public bug reported:
The generated svg file is completely different in pepwheel from ubuntu and the
one from Gentoo. I am unsure if it is related with some patches we are applying
in gentoo... but in Gentoo I think only the plplot could be related:
** 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
-- swm properties --
** 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
-- swm properties --
Enabling nvidia card fails with
[ 263.394167] pci :01:00.0: can't change power state from D3cold to D0
(config space inaccessible)
Dell Precision 7530
Linux odysseus3 5.5.1-1-default #1 SMP Tue Feb 4 06:56:24 UTC 2020
(1d61c83) x86_64 x86_64 x86_64 GNU/Linux
Tumbleweed 20200209
** Attachment added: "glxinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327670/+files/glxinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862910
** Summary changed:
- Perform TestPlan
+ [SRU] shim 15+1552672080.a4a1fbe-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862171
Title:
[SRU] shim 15+1552672080.a4a1fbe-0ubuntu1
To manage
@Lee Thanks for tracking down the util-linux bug.
Since this is broken in 2.34 (eoan/focal); I'm thinking we should use
sysfs to find the parent via device name walking;
Given a kname (nvme0n1p1) of the target partition
# look up sysfs path from kname
% realpath /sys/class/block/nvme0n1p1
@Alberto
> I thought the installer would work similarly to what the desktop installer
> does with btrfs, where it creates subvolumes for / and /home in the root
> partition (as @ and @home).
>
> On my desktop, when I upgrade I just move @ out of the way (by renaming it)
> and the installer
** Attachment added: "lspci -k"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327669/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862910
*** This bug is a duplicate of bug 1831986 ***
https://bugs.launchpad.net/bugs/1831986
** This bug has been marked a duplicate of bug 1831986
fwaas_v2 - unable to associate port with firewall (PXC strict mode)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
1. Screenshot attached. I have been using two screens but to simplify
things I have confirmed that only having one makes no difference, so I
am sticking to that whilst testing.
2. I did already have show seconds set, I have now tried without and it
doesn't seem to make a difference
3. I thought
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-ff-incoming
** Also affects: util-linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Focal)
Importance: High
Status: Triaged
** Also
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378957
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862947
Title:
crmsh
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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
@matthew.ahrens you can paste that URL into any browser on any machine
and authorise it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862822
Title:
init_on_alloc=1 causes big performance
Public bug reported:
python3-flask-cache https://github.com/thadeusb/flask-cache is not
compatible with current "python3-flask", fails when instantiating a
cache in jinja2 module trying to import old style flask.ext.cache.
Successor https://github.com/sh4nks/flask-caching can be used as a
`backintime` is a nice piece of software, so maybe it's worth updating
the link to the new one (their github page or something)
Thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862937
Title:
** Changed in: linux-oem (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857541
Title:
[SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
** 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
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
This is now targeting 2.43 point release.
** Changed in: snapd
Milestone: None => 2.43.3
** Changed in: snapd
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- bionic/linux-aws-fips: -proposed tracker
+ bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel
** Tags added: 5.3 eoan sru-20200127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798358
Title:
failed to start KVM with uvtool on P8
To manage notifications about this bug go to:
I install the pi-bluetooth on ubuntu 19.10.1, after reboot, the
bluetooth works automatically.
So pi-bluetooth could hide this issue.
[ 24.924485] Bluetooth: BNEP socket layer initialized
ubuntu@ubuntu:~$ hcitool dev
Devices:
hci0B8:27:EB:24:02:02
--
You received this bug
** Patch added: "ltt-control_2.11.1-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ltt-control/+bug/1862936/+attachment/5327652/+files/ltt-control_2.11.1-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks! (re 'similar to'> yes, I had a typo :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862832
Title:
snapd and Ubuntu 20.04 nvidia triggers apparmor denials on 'sendmsg'
Public bug reported:
Installing vim-runtime for the vimtutor does not also install vim.
Running vimtutor then opens vi and presents the user with the default empty
page with no knowledge of how to exit vi.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: vim-runtime 2:8.1.0875-5ubuntu2
I tested raspbian on the RPI4B board, also could reproduce this problem.
steps of testing:
login the raspbian, sudo mv /usr/bin/hciattach /usr/bin/hciattach-bak
reboot
login, check the bluetooth is not up "hcitool dev"
run sudo hciattach-bak /dev/ttyAMA0 bcm43xx 921600 noflow
will timeout and
Public bug reported:
crmsh is currently the most tested cluster resource manager
configuration tool we have for Ubuntu (pcs being the second one, and
already scheduled for more tests in order to replace it in a near
future).
With that said, currently crmsh is found at -universe:
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862943
Title:
failing autopkgtests with new boost1.71
To manage notifications about this bug go to:
Public bug reported:
Open control center - settings - set background - select a solid color
is not possible also if stated in the help.
Change the desktop and lock screen backgrounds
You can change the image used for your backgrounds or set it to be a solid
color.
corrado@corrado-x5-ff-0104:~$
I can confirm that the bug still exits in kernel: 5.3.0-28-generic (in
my case with Linux Mint 19.3)
Sony Vaio product: VPCSE2J9E v: C60A4YXE
Intel Centrino Advanced-N 6230 [Rainbow Peak] driver: iwlwifi
I tried the workaround by @massimo-bacilieri (thanks!) manually and this
worked fine.
--
** Description changed:
Prerequisites:
* Ubuntu Bionic or Zorin OS 15
* chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64
* fcitx=1:4.2.9.6-1
* fcitx-unikey=0.2.4-1.1
Steps:
* Launch fcitx and chromium-browser.
* Focus input to a text box (e.g. omnibox, F12 console).
*
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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
Regression testing was successful.
==> ../test-results/bionic-train-proposed-default.tempest-results <==
Ran: 92 tests in 863.4399 sec.
- Passed: 84
- Skipped: 8
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 412.1228 sec.
==
Worker
Public bug reported:
crmsh is currently the most tested cluster resource manager
configuration tool we have for Ubuntu (pcs being the second one, and
already scheduled for more tests in order to replace it in a near
future).
With that said, currently crmsh is found at -universe:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
I've removed the link that I believe you meant, let me know if there are
any further problems or I did something wrong.
Thanks again for reporting this issue, and helping make Ubuntu and our
documentation
** Description changed:
failing autopkgtests with new boost1.71
python3-defaults currently needs ceph to become a candidate which needs
boost1.71 to become a candidate
boost1.71 is blocked on:
gyoto ppc64el
hilive arm64
yade arm64
I am opening this bug report to
Terrence Houlahan's fix also works for me on 18.04 Many thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531184
Title:
[SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Public bug reported:
failing autopkgtests with new boost1.71
python3-defaults currently needs ceph to become a candidate which needs
boost1.71 to become a candidate
boost1.71 is blocked on:
gyoto ppc64el
hilive arm64
yade arm64
I am opening this bug report to triange / fix these, however
** 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
-- swm properties --
** 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
-- swm properties --
** 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
-- swm properties --
301 - 400 of 573 matches
Mail list logo
