Clarification: this bug ist not about wrong battery Level measurements
(Nobody reported that), it's about users being unable to disable
notifications. The notification is shown even when in DND mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: hwe-next
Assignee: (unassigned) => Jesse Sung (wenchien)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18972
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
If I understood correctly this bug was invalidated as a Linux bug only,
not as a GNOME issue. As a GNOME (or more specifically as "gnome-
settings-daemon package") it is not only valid, but its priority is set
to high. It makes sense to me.
--
You received this bug notification because you are a
I sponsored the procps changes to Groovy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886112
Title:
Enabling DMESG_RESTRICT in Groovy Onward
Status in linux package in Ubuntu:
Fix
Public bug reported:
Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2
Most of the subcommands for /sbin/ip are documented in a manpage with a name of
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at
"ip-address(8)".
However, ip tuntap seems to be
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897329
Title:
Synaptics TouchPad not showing
Public bug reported:
Synaptics TouchPad not showing in ubuntu cat /proc/bus/input/devices
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-48-generic 5.4.0-48.52
ProcVersionSignature: User Name 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2
mp_irqdomain_activate from arch/x86/kernel/apic/io_apic.c will use the
chip_data that is set by the commit referred by Stefan ("XEN uses
irqdesc::irq_data_common::handler_data to store a per interrupt XEN data
pointer which contains XEN specific information.").
>From drivers/xen/events/events_base
last one you sent with the commit? It is working.
On Fri, 25 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> can you give kernel in #24 a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
> a
Information updates: the patch is now queued in 5.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894667
Title:
[HP 635] Radeon 6310 brightness control does not work
Status in linux
It would be nice to understand what is going on here. Currently on 19.10
and have not upgraded to 20.04 yet... because of this very same bug! It
took so long to get rid of the last time around. Many months.
Should also do a regression test here back on 19.10 too? It seems I can
install both the la
@jcline-physics,
can you give kernel in #24 a try?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896482
Title:
acpi event detection crashes
Status in linux package in Ubuntu:
In Pr
I've also run into this issue on Pop!_OS 20.04 LTS; Nvidia driver
450.66; Linux kernel 5.4.0-7642-generic; GeForce GTX 1080 8GB; mutter
3.36.4; GNOME Shell 3.36.4.
I'm running two monitors: NS-PMG278 (144Hz DP connection) + Dell U2719D
(60Hz DP connection), both at 1440x2560.
I'm getting the exac
So I can confirm the behavior with a local Xen Server and a HVM Xenial
guest. While the current proposed 4.4 kernel crashes while setting up
the acpi interrupt, this does not happen with a 4.15 kernel from
proposed on a Bionic HVM guest. Still I was able to get the 4.4 kernel
to boot by reverting t
After a lot of tests on AWS with generic and AWS kernels and on non-AWS
bare-metal systems with the AWS and generic kernels I discovered that
one gets I/O throttling on AWS instances regardless of using ZFS or not.
I ran a really simple test writing and reading to the raw device and
found the *sam
qat_c62x does not need blacklisting.
intel_qat does.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897188
Title:
Ceph Full Disk Encryption will cause timeouts.
Status in linux packag
Public bug reported:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to some
access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwif
There are two Mints on my desktop on different HDs 19.1 and 19.3 (I
tried the last but I didn't like it too much - longer booting, worse and
harder interface settings). I guess bootloader defines kernel version to
run. Bootloader from 19.3 run 4.15.0-112 kernel in LM 19.1, recent
kernel for that mo
Just installed a new system and the bug is still there, leading me straight
back to this bug report for the 'fix'.
I was really hoping that this bug would have been addressed in 20.04.1.
Not sure why no one from the dev team is picking this up to rectify it.
--
You received this bug notification
Hi Petar,
I just asked for a double-check of -26 and -28 as you've done.
Thanks, and sorry if that wasn't clear.
The difference in the source code is just for reference purposes,
you don't have to act on it -- the available packages/builds are
already with (-28) and without (-26) it.
Your test d
Hi Mauricio,
I don't understand what you are asking me to do...
You are showing me a small difference in the source code, but I am testing
binaries. And between them is the whole complicated build process.
Since I kept the kernels 5.4.0-26 & 5.4.0-28 I re-tested again.
5.4.0-26 boots with and
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896725
Title:
xenial 4.4.0-191-generic in -proposed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1897284
Public bug reported:
At random times I get two bluetooth indicators on the bottom of the
screen instead of one.
See the screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generi
Hi Petar,
Thanks for the bisection, but it seems something is a bit off.
The only change between 5.4.0-26 and -28 is a patch for s390x,
which is a different architecture, nothing to do with amd64,
and no common files are changed.
Could you please review the dis_ucode_ldr parameter is what
you ex
thanks a lot Alex
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
> The patch in #23 requires three precedent patches. See SRU.log file for
> more details.
>
> Note it is rebased Ub
My pc also could not find/see my NVME device after ubuntu update. As a result
it could not boot to the system.
The following is the Nvme storage:
```
~$ sudo nvme list
Node Model
/dev/nvme0n1 INTEL SSDPEKKW512G8
```
Problem has been resol
** Changed in: linux-aws (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1896604
Title:
Groovy kernel (5.8.0-1004-aws) creates broken /dev
I can confirm the same bug also for 5.4.0-45 and for 5.4.0-48 and also a
workaround. In kernel 5.4.0-45 it is happening only one out of 3-4 times
directly on boot. In all the other 2 kernels (5.4.0-47 and 5.4.0-48) it
is happening on each cold boot.
Workaround: after first cold boot from the login
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897227
Title:
Remove NVMe suspend-to-idle workaround
Status i
Just some additional data without any final conclusion. Talking to Sean,
the affected instance type seem to be all Xen based. The provided
stacktrace backs this. In the past that could have been a mix of
paravirtualized (PV) and hardware virtualized (HVM). But since
spectre/meltdown I expect that t
Public bug reported:
[Impact]
We already have correct NVMe suspend-to-idle implementation, we can
remove workaround we carried in Ubuntu kernel.
[Fix]
Revert unnecessary no D3 quirks we used as workaround.
[Test]
After the revert, both NVMe still use native power saving mechanism as
intended.
[
33 matches
Mail list logo
