** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1836031
Title:
[SRU][B/B-OEM]Fix resume failure on some TPM chips
To m
Hi guys,
upstream maintainer here :)
I saw a few comments above related to libnozzle test suite not being
executed. Due to the nature of libnozzle, the test suite has to be
executed as root unfortunately. The ioctl required to manage tap devices
are privileged only.
The test suite detects if run
The test result on AMD64:
startup='Tue Jul 9 14:23:18 2019'
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP
prctl04.c:125: PASS: prctl(PR_SET_SECCOMP) sets SECCOMP_MODE_STRICT succeed
prctl04.c:197: PASS: SECCOMP_MODE_STRICT doesn't
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1767992
Title:
Linux md raid-10 freezes during resync
To manage notifi
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: New =>
Public bug reported:
This failure was only spotted on PowerPC (node "modoc"), it has passed
with AMD64 / i386, entirely skipped on ARM64.
startup='Mon Jul 15 22:48:25 2019'
tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
prctl04.c:213: INFO: kernel support PR_GET/SET_SECCOMP
prctl04.c:12
@Dmitriis - I'd expect this testing and verification is on you as you
have done so before, so give it a go once you have some time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833299
Title:
lasso
Does kernel parameter "i8042.nomux=1" help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836474
Title:
dell touchpad not working
To manage notifications about this bug go to:
https://bugs.launchp
I could see this failing on Trusty ARM64 Moonshot node, but not the ppc64le
node "modoc":
startup='Tue Jul 9 07:45:17 2019'
tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop0'
tst_mkfs.c:90: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.42.9 (4-Feb-2014)
tst_test.
Upstream stable 4.4.181 had many brcmfmac updates. From the trace
suspicious seems:
brcmfmac: revise handling events in receive path
commit 9c349892ccc90c6de2baaa69cc78449f58082273 upstream.
which has a fixup upstream that sounds like the issue:
commit 31143e2933d1675c4c1ba6ce125cdd9587
I can also confirm that the issue still exists, but only if I run perf top as
root or with sudo.
Running perf top it as regular user is fine - even w/o the patches packages!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Patch added:
"0001-UBUNTU-SAUCE-i2c-designware-add-G3-3590-into-i2c-qui.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1836836/+attachment/5277555/+files/0001-UBUNTU-SAUCE-i2c-designware-add-G3-3590-into-i2c-qui.patch
--
You received this bug notification because you
** Patch added:
"0001-UBUNTU-SAUCE-i2c-designware-add-G3-3590-into-i2c-qui.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1836836/+attachment/5277554/+files/0001-UBUNTU-SAUCE-i2c-designware-add-G3-3590-into-i2c-qui.patch
--
You received this bug notification because you
Public bug reported:
[Impact]
Wake up from runtime suspend, Goodix doesn't report correct Tap event by
tapping it the first time, so if you double tap the touchpad, the system
only got one tap.
[Fix]
Adding one missing platform which uses Goodix touchpad IC to the i2c
designware quirk list.
[Tes
Disco MP review is approved.
Still waiting on Bionic.
Other tests are now complete and freed up the machine, I'll prep the
test results that we need along these uploads now ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
hmm I never hit send on this, it is actually a bit older ...
Changes in Debian accepted.
Bionic branch ready and building in the PPA [1] as well now.
Testing will start after build is complete.
MPs already ready for review at [2][3].
[1]:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-18363
I have HP Spectre X360 13" 2019 Model, and have the same problem.
After the touch pen/stylus is detected, finger touch stops working. Is
there any workaround or command to get it working again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
https://lists.ubuntu.com/archives/kernel-team/2019-July/102298.html
https://lists.ubuntu.com/archives/kernel-team/2019-July/102299.html
** Description changed:
+ SRU Justification:
+
+ [Impact]
+ Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to
+ pair BT LE HID devices on re
2 patches were skipped because they were already applied:
0002-mm-page_idle.c-fix-oops-because-end_pfn-is-larger-th.patch
0036-KVM-X86-Fix-scan-ioapic-use-before-initialization.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Applied patches:
* fs/binfmt_flat.c: make load_flat_shared_library() work
* scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()
* tracing: Silence GCC 9 array bounds warning
* gcc-9: silence 'address-of-packed-member' warning
* usb: chipidea: udc: workaround for endpoint conflict issue
* Inp
Applied patches:
* Linux 4.4.184
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836667
Title:
Xenial update: 4.4.184 upstream stable release
To manage notifications about this bug go to:
https://b
All patches from this updated were already applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836665
Title:
Xenial update: 4.4.182 upstream stable release
To manage notifications about this bu
Applied patches:
* fs/fat/file.c: issue flush after the writeback of FAT
* sysctl: return -EINVAL if val violates minmax
* ipc: prevent lockup on alloc_msg and free_msg
* hugetlbfs: on restore reserve error path retain subpool reservation
* mm/cma.c: fix crash on CMA allocation if bitmap allocatio
One patch was skipped as it was already present:
0039-Revert-Bluetooth-Align-minimum-encryption-key-size-f.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
Xenial update: 4.4.183
Applied patches:
* Linux 4.4.182
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836665
Title:
Xenial update: 4.4.182 upstream stable release
To manage notifications about this bug go to:
https://b
All patches from this updated were already applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836667
Title:
Xenial update: 4.4.184 upstream stable release
To manage notifications about this bu
Yes, please test hwe-edge kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818974
Title:
Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
To manage notifications about this bug go
[Expired for puppet (Ubuntu) because there has been no activity for 60
days.]
** Changed in: puppet (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829316
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
We long since stopped using lxdm, so invalidating.
** Changed in: lubuntu-artwork (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/666590
Title:
lxdm theme n
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-lts-xenial (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtkhash (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/1831323
Title:
Gt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mate-menus (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/1831323
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (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/1811248
Title:
s
Thank you, Warren. So I think I can begin to send a patch to the series
don't have REL0450 ibt-17-16-1.sfi, so that owners of the same devices
don't have to manually download again.
For polluted /lib/firmware, I think I would restore what it was and copy
only ibt-17-16-1.sfi to keep Bluetooth work
On Google, GCP this appears to fail across all of our tested instances.
Looks like that the cause is from the following due to the following
07/16 06:52:00 DEBUG| utils:0153| [stdout] [16] Test trace_printk from module
[UNRESOLVED]
07/16 06:52:05 DEBUG| utils:0153| [stdout] [21] ftrace - funct
On GCP trace_printk module can't be found which triggers exit_unresolved
/home/jenkins/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
+ rmmod trace-printk
rmmod: ERROR: Module trace_printk is not currently loaded
+ :
+ modprobe tra
Failure on Trusty:
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial
stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.4VEzBBYPcp -smp 1
# -initrd /tmp/tmp.Ef5R8Mt7p5
enabling ap
Thanks for the bug report.
Please tell us what version of Ubuntu you are using. Then please report
the problem to the BlueZ developers at:
https://bugzilla.kernel.org (Product: Drivers, Component: Bluetooth)
and then tell us the new bug ID.
** Changed in: bluez (Ubuntu)
Status: New =>
** Attachment added: "dmesg output after reverting to rel0450 of
ibt-17-16-1.sfi"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836467/+attachment/5277544/+files/dmesg3.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK - after installing the rel0450 version, shutting down for 5 minutes and
rebooting, Bluetooth is still working for me. Here's the new md5sum
b24eceb411cf63695aac8e0b6d9f1743 /lib/firmware/intel/ibt-17-16-1.sfi
I'll upload the latest output of dmesg | egrep -i "blue|firm", in case
that helps.
Public bug reported:
Greetings wise Ubuntu community,
I'm having a video playback issue with Kodi 2:17.6+dfsg1-2ubuntu1 on
Ubuntu 18.04.2 LTS.
Everything was running fine until yesterday when I decided to apply the latest
Ubuntu updates.
When I try to play a video with Kodi it immediately crash
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Before we debug anything here, one of your packages is broken, which
might be relevant:
libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
It should be version 19. To fix this please run:
sudo apt update
sudo apt full-upgrade
If that doesn't fix it then download and install the missing package:
https
Oh, you said that downgrade was a workaround.
So in that case this sounds like a bug in libgl1-mesa-
dri_19.0.2-1ubuntu1.1~18.04.1_amd64.deb
** Tags added: regression-update
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Sta
Public bug reported:
[Impact]
The Snap Store changed the names of some of the sections. This means that these
are no longer mapped to the XDG categories used in GNOME Software. See
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279
[Test Case]
1. Open GNOME Software
2. Go to graph
The md5sum of what is current installed and working is:
5740378bfc048108341a204b83ca97c7 /lib/firmware/intel/ibt-17-16-1.sfi
Which is the same md5sum as the rel0472 version you link to above, so
yes, that does seem to be working.
I've downloaded the rel0450 version now, I'll install it, and leav
Next time the freeze happens, please:
1. Tell us if the mouse pointer still moves?
2. Reboot, log in again and run:
journalctl -b-1 > prevboot.txt
and send us the resulting file 'prevboot.txt'.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Inco
** Also affects: plymouth (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685794
T
** Changed in: linux-firmware (Ubuntu)
Status: In Progress => 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/1835879
Title:
Intel Wireless-AC 9462/9560 not supported on ICL
To m
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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 se
** Summary changed:
- ubuntu_kernel_tests ftrace fails on disco, linux-azure
+ ubuntu_kernel_tests ftrace fails
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834930
Title:
linux-aws: 4.15.0-1044.46 -proposed tracker
To manage notifications about this bug go to:
https
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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 se
** Summary changed:
- ipmitool failed: Could not open device at /dev/ipmi0 : No such file or
directory
+ ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such
file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834886
Title:
linux-aws: 5.0.0-1011.12 -proposed tracker
To manage notifications about this bug go to:
https:
I consider this a regression from 16.04 to 18.04. However, installing
from eoan on 18.04 resolved this set of issues for me:
https://packages.ubuntu.com/eoan/amd64/libxpresent1/download
It would be great to get this into other versions as it seems like a
trivial fix.
--
You received this bug no
Public bug reported:
This bug affects the python-acme package in all released versions of
Ubuntu.
The python-acme package will no longer work with Let’s Encrypt’s
“ACMEv2” endpoint which is their RFC 8555 compliant endpoint starting
November 1st. See https://community.letsencrypt.org/t/acme-v2-sc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libxpresent (Ubuntu Disco)
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/1801071
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libxpresent (Ubuntu Bionic)
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/1801071
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Public bug reported:
Happened while setting up new Ubuntu Installation on an UP Board SBC
following the steps in the wiki linked here: https://wiki.up-
community.org/Ubuntu
One step was not performed properly. On removing the generic installed
kernel, a warning message came up for one of the pack
** 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/1836821
Title:
package linux-image-4.15.0-54-generic (not installed) failed to
install/upgrade: subprocess insta
Fixed in -proposed:
(Reading database ... 21788 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.10_amd64.deb ...
Unpacking base-files (9.4ubuntu4.10) over (9.4ubuntu4.8) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-up
** Changed in: dkms (Ubuntu Disco)
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/1828948
Title:
OBSOLETE_BY in DKMS.CONF does not work
To manage notifications about
I went to try again and get the log ... and with today's build it is
working. Let me try on the other machine that I was seeing this with and
then I will close the bug.
(The one thing I noticed is that I needed to restart the computer before
it worked, while I could swear it used to work as soon a
** Changed in: qt4-x11 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836444
Title:
Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main)
To
** Package changed: ctdb (Debian) => samba (Debian)
** Bug watch removed: Samba Bugzilla #13860
https://bugzilla.samba.org/show_bug.cgi?id=13860
** Bug watch removed: Samba Bugzilla #13984
https://bugzilla.samba.org/show_bug.cgi?id=13984
** Bug watch removed: Samba Bugzilla #13985
https
** Changed in: dpkg (Ubuntu Cosmic)
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/1828639
Title:
Unlooping all the trigger loops!
To manage notifications about
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 1836816
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: gconf (Ubuntu)
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/1834211
Title:
[SRU] gconf FTBFS in Bionic
To manage notifications about this bug go to:
** No longer affects: ubiquity (Ubuntu)
** Changed in: partman-basicfilesystems (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770093
Title:
Ubiquity crashe
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1836816
[Impact]
There are a number of races in nf_conntrack when multiple packets are
sent from the same origin to the same destination at the same time,
where there is no pre-existing confirmed conntrack entry, in a NAT
environment.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836742
Title:
Please enable CONFIG_PMIC_OPREGION and it's components to resolve
All autopkgtests for the newly accepted dpkg (1.19.0.5ubuntu5.1) for cosmic
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#cosmic
-
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836797
Title:
VDPAU decoders don't work with some files
To manage notifications about this bug go to:
https://bugs.launchpad.net
I can confirm that the SCHED_STACK_END_CHECK config option has been
enabled in the linux-kvm kernel 4.4.0-1052.59 for xenial, 4.15.0-1039.39
for bionic, and 5.0.0-1011.12 for disco. Thanks!
** Tags added: verification-done-bionic verification-done-disco
verification-failed-xenial
** Tags removed:
This issue affects only kernels after 4.17 and before 5.2, hence it's
fixed on Bionic and Eoan, and won't be fixed in Cosmic (4.18) since it
is EOL.
Patches submitted to kernel-team ML: https://lists.ubuntu.com/archives
/kernel-team/2019-July/102287.html
Cheers,
Guilherme
--
You received this
** Description changed:
- TBD
+ [Impact]
+
+ * During raid0 error path testing, by removing one member of the array,
+ we've noticed after kernel 4.18 we can trigger a crash depending if
+ there's I/O in-flight during the array removal. When debugging the
+ issue, a second problem was found, that
Because it is an SRU regression (apache2 2.4.34-1ubuntu2.2 introduced
the same change to cosmic that apache2 2.4.29-1ubuntu4.7 did for
bionic), I would accept a fix for cosmic for expedited SRU verification
despite the EOL being in 2 days time.
--
You received this bug notification because you ar
** Description changed:
[Impact]
* LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version
6.2.5 is currently in Eoan.
For a list of fixed bugs compared to 6.2.4 see:
https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs
https://wik
I can confirm that the PAGE_POISONING, PAGE_POISONING_NO_SANITY, and
PAGE_POISONING_ZERO config options are set in the linux-kvm
5.0.0-1011.12 kernel in disco proposed. Thanks!
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I suddenly realized cosmic is EOL. I'll let the sru team weigh in if
this fix can still be published for cosmic or not.
** Changed in: apache2 (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: apache2 (Ubuntu Cosmic)
Importance: Undecided => Critical
** Changed in: apache2 (Ubu
linux-kvm is currently 5.0.0-1010.11 in disco, looks like this bug got
left behind. Closing.
** Changed in: linux-kvm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-kvm (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because
This bug was fixed in the package grub2 - 2.04-1ubuntu1
---
grub2 (2.04-1ubuntu1) eoan; urgency=medium
* Merge against Debian; remaining changes:
- debian/control: Update Vcs fields for code location on Ubuntu.
- debian/control: Breaks shim (<< 13).
- debian/patches/linu
This bug was fixed in the package grub2 - 2.04-1ubuntu1
---
grub2 (2.04-1ubuntu1) eoan; urgency=medium
* Merge against Debian; remaining changes:
- debian/control: Update Vcs fields for code location on Ubuntu.
- debian/control: Breaks shim (<< 13).
- debian/patches/linu
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
5.0.0-1011.12 linux-kvm kernel in disco-proposed. Thanks!
** Tags added: verifiction-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => 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/1824981
Title:
cifs set_oplock buffer overflow in strcat
To manage notific
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of
I've switched in the meantime to Ubuntu (Gnome), thus I cannot update
the bug. If there's no other Lubuntu user being able to help out feel
free to close the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I can confirm that the CONFIG_LOCK_DOWN_KERNEL config is enabled in the
4.15.0-1039.39 linux-kvm kernel in bionic-proposed. Thanks!
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
All autopkgtests for the newly accepted dpkg (1.19.6ubuntu1.1) for disco have
finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco
--
Y
All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.3) for disco
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco
All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.3) for disco
have finished running.
There have been regressions in tests triggered by the package. Please visit the
sru report page and investigate the failures.
https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco
Public bug reported:
Hello everyone,
We are currently developing a device that contains two HID services.
That device, as it is right now, is properly functioning on Windows & Android.
However, when pairing the device on Linux running bluez 5.50 we do get
segfaults (see attached files).
Our blue
** Changed in: linux-firmware (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Cosmic)
Status: In Progress => Won't Fix
** Changed in: linux-firmware (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notif
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/apache2/+git/apache2/+merge/370222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836329
Title:
Regression running
** Also affects: linux (Ubuntu Eoan)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Ff-series)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a mem
Lukasz, I do not see any problems with this package, neither on the
https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic
page nor on
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html
which are the regressions actually caused?
--
You re
1 - 100 of 438 matches
Mail list logo
