Public bug reported:
$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
Laptop model: Lenovo-IdeaPad-S145-15IIL
Touchpad not working since I installed Ubuntu 20.04. This is the first
time I installed ubuntu on this computer.
$ xinput list
⎡ Virtual core pointer
So this is still a problem with kernel 5.14 without a working
straightforward solution. This is becoming frustrating since this issue
is now 4 months old.
@TuxInvader: I tried your repository (ppa:tuxinvader/lts-mainline) with
5.14, but something went very wrong - after booting with this kernel, m
Hi, another update.
I've shutdown the System 200 times by guess. And the System go Powerless
3 times.
Linux Kernel 5.14 has the same problem.
See Below.
** Description changed:
Hi, i upgraded my System. Before I had a Ryzen 3200G.
Now I have an Ryzen 5700G.
Both systems running on an Li
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1940513/+attachment/5523028/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1940513/+attachment/5523029/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Hi Royi,
please disable secure boot from BIOS and try this kernel.
thx.
On 9/5/21 2:15 PM, Royi Klein wrote:
> @Hui Wang:
>
> I get:
> error: /boot/vmlinuz-5.11.0-33-generic has invalid signature.
> Loading initial ramdisk ...
> error: you need to load the kernel first.
>
> Did you use the modul
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-intel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-intel (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.
This bug was fixed in the package plymouth - 0.9.5git20210406-0ubuntu1
---
plymouth (0.9.5git20210406-0ubuntu1) impish; urgency=medium
* New upstream snapshot 20210406 (commit e55447500fa9) taken on
2021-08-31 (upstream is unchanged since April) to get the latest bug
fixes,
Now 5.13.4 also fails to boot while 5.13.13 is OK. Obviously some fail
code has been backported from 5.14 to 5.13.14.
** Summary changed:
- Kernel 5.14.0/1 fails to boot
+ Kernel 5.14.0/1/5.13.4 fails to boot
** Summary changed:
- Kernel 5.14.0/1/5.13.4 fails to boot
+ Kernel 5.14.0/1/5.13.14 f
Same issue on Dell Latitude 5500 when hitting the F8 key for choosing
the display.
--
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/1878718
Title:
HP ZBook 15 G6 display key (Fn+F1) autore
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (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/187
Seems like it is one of these commits -
https://cgit.freedesktop.org/drm/drm/tag/?h=drm-fixes-2021-08-27
I just looked at changelog for 5.13.14 and those 3 commits were also
added.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
I don't know if it is important...?
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.3
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules:
Public bug reported:
/usr/lib/zfs-linux/trim, which is run on the first Sunday of every month
via an entry in /etc/cron.d/zfsutils-linux, outputs the following
message if a pool has no devices that support TRIM:
cannot trim: no devices in pool support trim operations
When this occurs via the
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1942713
Title:
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
failed to build
Same with 20.04 et nv390 (proprétaire, testé).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't write to /etc/xorg
Status in nvidia-settings
Installing xserver-xorg-dev fixed the error !
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't write to /etc/xorg
Status in nvidia-settings
@Colin To be clear this is the same bug I originally hit and opened the
launchpad for, it just doesn't quite match with what most people saw in
the upstream bugs. But it seemed to get fixed anyway for a while, and
has regressed again somehow.
Same exception as from the original description and oth
@nvrmndr #76
steps in #57 still work for 5.14 ;-)
anyway i did make some changes in my private tool, so can be published and is
here:
https://github.com/k3dar/kumk
you can simply install 5.14 via: sudo kumk install 5.14
--
You received this bug notification because you are a member of Kernel
Sorry those links in comment #29 would only have worked on 24 August.
Try these instead:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-
tip/2021-09-04/amd64/linux-image-
unsigned-5.14.0-051400drmtip20210904-generic_5.14.0-051400drmtip20210904.202109040225_amd64.deb
https://kernel.ubuntu.com/
I did confirmed it's fixed by using 5.13 from -proposed
(5.13.0-1011-oem)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
--
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/1927076
Title:
IPv6 TCP in reuseport_bpf_cpu from ubunt
[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
[Expired for MAAS because there has been no activity for 60 days.]
** Changed in: maas
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/bugs/1916610
Title:
** Changed in: ubuntu-power-systems
Status: Incomplete => 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/1927076
Title:
IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_
Steps to solution:
1. Plug in USB Wifi device
2. lsusb
3. check for line similar to:
Bus 001 Device 057: ID 0bda:f179 Realtek Semiconductor Corp
4. using your favorite search engine, look for: "0bda:f179" (or whatever ID you
see in the above line.
Hopefully this will point you to a downloadable /
** Tags added: nouveau radeon
** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this b
Thanks for the bug report.
You seem to be using the old (not recommended) Xorg graphics drivers
called 'nouveau' and 'radeon'. They have been replaced by the newer
driver 'modesetting'. So if you are writing a Xorg config file be sure
to use the latter.
Please also note the nouveau kernel driver
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/1942738
Title:
XOrg / nouveau - hard lockups
This machine is a frankenstien to help debug the issues with my main
workstation. I need to upgrade but dual GPU is horribly broken on across
all flavors and even non-Ubuntu/Debian distros.
I was explicitly testing how the system functions with no xorg.conf
between 2 separate GPU's. Yes the nVidia
31 matches
Mail list logo
