** Package changed: linux (Ubuntu) => ubuntu-mate
--
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/1942832
Title:
Ubuntu MATE 21.04 installation disables Install button.
Status in Ubuntu
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/1942832
Title:
Ubuntu MATE 21.04
We'll keep the bug open because the issue shouldn't ever happen out-of-
the-box. The next person to use the same laptop model will run into the
same problem.
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux-hwe-5.11 (Ubuntu)
Importance:
Public bug reported:
Downloaded Ubuntu MATE. Opened .iso with Disk Image Writer. Burned to
32GB SanDisk jump drive. Booted UEFI jump drive. Selected English(US).
Checked "install third-party..." Tried "Install alongside them".
Cancelled when installed chose the wrong drive to install to. Tried
Thanks. This solution worked for me.
The issue can be closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942828
Title:
[Huawei MateBook X] Display is corrupted in kernel
[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.
FYI, I was being hit by this and the issue disappeared once I updated
the firmware on those NICs to 14.31.1014. The problematic firmware
version I had was 14.26.1040. Not only did I see those errors, but I
actually saw traffic being dropped.
--
You received this bug notification because you
Public bug reported:
[Impact]
Realtek r8169 has abysmal network speed.
[Fix]
Disable ASPM L1.2 because the device takes a long time to exit from
L1.2.
[Test]
Use `iperf` to test network speed.
When ASPM L1.2 gets disabled, TX and RX and reach ~700Mbps and ~900Mbps
respectively.
[Where problems
This bug was fixed in the package llvm-toolchain-12 - 1:12.0.1-8
---
llvm-toolchain-12 (1:12.0.1-8) unstable; urgency=medium
* Add back CMAKE_EXTRA to build LLVM gold (Closes: #993664)
[ Gianfranco Costamagna ]
* Refresh symbols on riscv64
-- Sylvestre Ledru Sat, 04 Sep
Thanks for the bug report.
Please try adding kernel parameter:
i915.enable_psr=0
to /etc/default/grub in the GRUB_CMDLINE_LINUX_DEFAULT line and then
run:
sudo update-grub
and reboot.
Does that fix it? If not then please attach a video of the problem.
** Changed in: linux (Ubuntu)
description implies 5.8 HWE kernel worked; thus issue likely kernel
related
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1942828
You have been subscribed to a public bug:
display driver In the kernel 5.8.0-generic is work fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion:
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux
** Description changed:
[Impact]
- The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
- raw gso min size - 1 (expected to fail)
- tx: 1524
- rx: 1472
-
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Description changed:
+ [Impact]
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
+
+ raw gso min size - 1 (expected to fail)
+ tx: 1524
+ rx: 1472
+
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 1942500
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: ubuntu => linux (Ubuntu)
--
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/1942500
Title:
invalid symbol # in scripts/module.lds
Status in linux package in Ubuntu:
** Description changed:
[Impact]
* Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
* Unable to use LED colors
* Unable to mmap PCI resources
* Cherrypick dtb changes from meta-sifive 2021.08 release
You have been subscribed to a public bug:
Description:Ubuntu 18.04.5 LTS
Release:18.04
Kernel: 5.11.5-051105-generic
Bug : Building External Wifi Drivers Fail , tried multiple drivers ,
Error generated , below.
Resolution tried : copying module.lds.S to the running kernel, does not
** Description changed:
[Impact]
- * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
- * Unable to use LED colors
- * Unable to mmap PCI resources
+ * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
+ * Unable to use LED colors
+ *
Public bug reported:
[Impact]
* Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
* Unable to use LED colors
* Unable to mmap PCI resources
* Cherrypick dtb changes from meta-sifive 2021.08 release
https://github.com/sifive/meta-sifive/tree/2021.08/recipes-
Mine does not reboot but I still have logs in dmesg
226290.971074] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[226290.971078] Code: 30 26 de 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b
05 bb 6c 00 00 48 89 e5 48 8b 40 28 e8 ef 8f 62 de 84 c0 74 02 5d c3 <0f> 0b 5d
c3 0f 1f 44 00 00
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in
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:
- Linux 5.14 fails to boot
+ Linux 5.14/4.13.14 fails to boot
--
You received this bug notification because you are a member of Kernel
Packages, which is
@cascardo,
Good point, just tested it with 5.4 kernel and works fine with it too.
Thanks,
Jo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile not
Hi. Manvydas here. My bug was closed as a duplicate (#1938936). I can
confirm that Kai-Heng Feng's kernel has fixed this issue on my system as
well. Thank you very much!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in
The attachment "lp1942784_focal.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
"patch" tag,
Result: partial freeze of the screens. No mouse but keyboard ok. htop
running but unable to launch a new prompt or any other process.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5523256/+files/journalctl.log
--
You received
Not sufficient.
There is another BUG() hidden at line 398:
status = acpi_ex_resolve_operands(walk_state->opcode,
&(walk_state->operands[walk_state->num_operands - 1]), walk_state);
in `walk_state->operands[]` array referencing.
After adding same guard for walk_state->operands[]
if
Hey, @joalif.
Has this been tested with focal 5.4 kernel too?
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile not properly working
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile not properly working on focal with 5.11 kernel
Status in makedumpfile package in
Debdiff for Focal.
** Patch added: "lp1942784_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+attachment/5523255/+files/lp1942784_focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
This
Dear TuxInvader...
I have no idea why you do what you do but THANK YOU. I HAVE BEEN GOING
NUTS trying to get past the kernel bug for Ubuntu upgrades. WTF, they
call 20.04 an LTS but you cannot keep up with kernel security patches.
ARE YOU KIDDING?
YOU SAVED ME.
Hours and hours of install
This issue can be reproduced on P8 node entei with:
* F-5.4 (5.4.0-81-generic)
* F-5.11 (5.11.0-27-generic #29~20.04.1-Ubuntu)
* H-5.11 (5.11.0-31-generic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello Seth, or anyone else affected,
Accepted wireless-regdb into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Seth, or anyone else affected,
Accepted wireless-regdb into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~20.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Seth, or anyone else affected,
Accepted wireless-regdb into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/wireless-
regdb/2021.08.28-0ubuntu1~21.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Good. Please help me test the kernel in
https://people.canonical.com/~mschiu77/lp1940113/amd_3.2.140/. Thanks
--
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/1940113
Title:
Linux
It should be caused by the kbuild flag `-fcf-protection=none` and this
will not be applied for the UBUNTU release image.
--
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/1941773
Title:
Seems the issue affects devices from multiple manufacturers,
and various models. Maybe some "commonality" can be found
between them, to trigger disabling ASPM they cannot handle,
better than trying to enumerate them in kernel sources as
suggested in commit 956c6d4f20c5446727e0c912dd8f527f2dc7b779,
Public bug reported:
Ubuntu 18.04.5 LTS
The touchpad is not detected with or without the Logitech M705 mouse plugged in.
cat /proc/bus/input/devices
Outputs:
I: Bus=0019 Vendor= Product=0003 Version=
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S:
The security PPA where 5.11.0-27 was built has "build dbgsyms" checked
but not "publish dbgsyms" this seems odd, cause i would think it is
useful to have access to published security ppa dbgsymbols.
Removing debug symbols is not nice. However, surely we can make disk
space savings the other way.
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: linux-hwe-5.11 (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Test 5.13.0-1011-oem from -proposed. It doesn't containing the patch.
Check the git tree as well. It doesn't exist.
** Tags removed: verification-needed-focal
** Tags added: verification-failed-fo
** Tags removed: verification-failed-fo
** Tags added: verification-failed-focal
--
You received
** Attachment added: "error8.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939225/+attachment/5523214/+files/error8.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
** 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://bugs.launchpad.net/bugs/1938689
Title:
[SRU][H/OEM-5.10/OEM-5.13/U] Fix
@nvrmndr - Works for me :-)
Please open a bug on my github project if you want help debugging it.
--
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/1926938
Title:
Recent mainline packages
Well I'm less concerned with getting the old GPU to work (again just a
test system trying to debug dual GPU in general) as I am getting my NEW
GPU's on my workstation working in 21.04 and future releases. Right now
Dual GPU is horribly broken and it's spans tons huge swathes of the
system. My set
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-hwe-5.11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu.
I also wish older GPUs were still supported but Nvidia makes it tricky.
The open source "nouveau" driver is almost always buggy and the closed
source drivers only ever support GPUs for a limited number of years
(admittedly the Linux kernel driver model is to blame for that rather
than Nvidia but
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
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
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
** 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
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
56 matches
Mail list logo
