Public bug reported:
Fails to push update.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.11.0-19-generic 6.11.0-19.19~24.04.1
ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd
I think I see the problem and AFAICT commit 0a46ef234756dca is just
making the latent deadlock easier to hit. The problem is shown by these
two stacktraces from your dmesg:
Task 1
[ 247.045575] __wait_on_freeing_inode+0xba/0x140
[ 247.045584] find_inode_fast+0xa4/0xe0
[ 247.045588] iget_lock
Yeah, I'm already watching it because when you narrowed down the range
to 6.9-6.10 I started suspecting this commit :) I'll try to reproduce to
debug what's going on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Public bug reported:
The linux-signatures-nvidia-6.8.0-22-generic package only contains
nvidia drivers as new as nvidia-driver-450 despite the current
additional drivers in Software & Updates having nvidia-driver-550 as the
tested topmost choice.
** Affects: linux-restricted-signatures (Ubuntu)
can you supply any more boot logs?
ie: are you getting the same "You must load the kernel first" error as in
https://bugs.launchpad.net/maas/+bug/2044169?
I suspect this is a broken/malformed image
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification becau
Yeah, i have this bug since forever, occurs randomly when opening steam.
It will load the steam window but not all the content inside then
freeze.
Ubuntu 22.04
Kernel: 6.2.0-37-generic
Amdgpu Mesa 23.3.0 - kisak-mesa PPA (LLVM 15.0.7)
A crash from today
Dec 8 15:31:33 H-Linux steam.desktop[207
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039991
Title:
UBSAN: array-index-out-of-bounds in /build/lin
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712652/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712648/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712651/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712650/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712649/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712646/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712647/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712644/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712645/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https:
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712643/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712642/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712640/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712639/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712641/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712638/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712637/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2039991/+attachment/5712636/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/203
apport information
** Tags added: apport-collected
** Description changed:
Everything works fine, this error shows up in the boot log.
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
VGA compatible controller: Advanced Micro Devic
Public bug reported:
Everything works fine, this error shows up in the boot log.
Description:Ubuntu 22.04.3 LTS
Release:22.04
Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde
PRO [Radeon HD 7750/8740 / R7 250E]
d
The nvidia support is still messed up under 6.2.0-26 for those using
secure boot. In previous iterations of the nvidia drivers and kernels,
one could always count on the linux-signatures-nvidia-6.2.0-26-generic
and linux-modules-nvidia-535-6.2.0-26-generic to use pre-signed kernel
modules rather th
After many false starts, the following similar RedHat bug report, gave
me a hint to a workaround that suppresses the CSR_RESET errors in
iwlwifi.
https://bugzilla.redhat.com/show_bug.cgi?id=2138790
Bug 2138790 - No WiFi on T16 Intel Gen 12th Alder Lake Wifi 6E AX 211
[NEEDINFO]
This bug report c
Upgrading the BIOS to capture the USB 2.0 fixes significantly reduced
the occurance of this bug but unfortunately doesn't totally eliminate
it. I should note that the Ubuntu 22.04 LTS kernels initially suffered
from this bug to a small degree but that by 22.04.1 LTS, the issue was
extremely rare. I
It appears that this is fixable with a BIOS update on the Gigabyte X570
UD v1.1 motherboard. Upgrading from the F32 stable BIOS release to the
F34 stable BIOS release captures the following change from the F33g beta
BIOS release...
3. Fix USB 2.0 devices stability and compatibility
which makes se
Unfortunately, this bug has gotten worse under 5.19.0-23.24 despite the
options hack. On a cold boot, about half the time the iwlwifi driver
shows the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Apparently the options workaround doesn't completely eliminate the bug.
It still occurs around five percent of the time when booting kinetic.
--
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/
Looking through the various bug reports against iwlwifi in bugzilla
related to iwlwifi driver initialization failures and previous
workarounds, I added...
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options iwlwifi uapsd_disable=1
to /etc/modprobe.d/iwlwifi.conf. Tentatively, this
Public bug reported:
A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu
22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of
the time. When this occurs, the kern.log shows...
Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0:
CSR_RESE
I attempted the upgrade again today. Running 5.15.0-43 I have no issues.
Battery or Power it seems to resume reliably.
Running on a Thinkpad X260
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Public bug reported:
Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
similar models with Realtek ALC294.
No solution works. Audio is not muted, tried adding snd-hda arguments -
no dice.
This has been reported numerous times, when will a fix finally be rolled
out?!
ProblemType
Followed https://wiki.ubuntu.com/DebuggingKernelSuspend
All of the modes are working except 'none'.
dmesg has these hash matches lines:
[ 11.920467] PM: Magic number: 1:0:0
[ 11.920512] memory memory48: hash matches
Saw a few lines online that this might be bios related, updated from
1.21
** Attachment added: "screenshot of the rendering artifact in cheese under
22.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png
--
You received this bug notification because you are a member of Kernel
Pac
I also can confirm that the warnings...
(cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late ():
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be
Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src !
xvimagesink' displays the webcam image fine.
--
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/1967843
Title:
cheese display c
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577390/+files/Dependencies.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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577392/+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: "lspci.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577393/+files/lspci.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/bugs/1967843
apport information
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577394/+files/lsusb.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/bugs/1967843
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577391/+files/ProcCpuinfo.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
apport information
** Tags added: apport-collected
** Description changed:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175): cheese-WAR
Public bug reported:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being
dropped.: ../li
I'm having this issue when launching a game using steam proton. When launching
the Stationeers game it wants to read from dvd-rw drive and once every 3-4
launches the game will also freeze the whole system. I'm guessing this is the
reason for the freeze since this would be the last error in logs
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1917709
Title:
Ubuntu tries to read blu-ray when boot from ssd and g
Edit: Please close this bug -- it is a duplicate of an upstream issue in
dxvk (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) and not
the kernel per se (although that makes life worse by clearing out vram
and hard-resetting the gpu once the crash occurs, which X and DMs have
no way to reco
Edit -- it transpires that, despite what I said, the magic <0 to <=0
change hasn't been made on the main branch of mesa's git repo yet. I've
successfully compiled a local copy (with meson & ninja) and am running
it in a separate root to avoid clobbering the system libraries using
LD_LIBRARY_PATH an
Public bug reported:
Hi there,
I am experiencing, at random, the AMD-GPU "fences timed out!" bug
reported previously as being either a kernel issue
(https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa
(https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The
later was apparent
The changes made to linux-firmware 1.201.1 on impish has destablized use
of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual
Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware
1.201.1, no wifi is available under Gnome in about 80-90% of the boots.
Under the pri
_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jack 1388 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 6 12:09:55 2021
InstallationDate: Installed on 2021
COMMAND
/dev/snd/controlC0: jack 1388 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 6 12:09:55 2021
InstallationDate: Installed on 2021-07-06 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
M
should be fixed by upcoming 5.4.120
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-
rc.git/commit/?h=linux-5.4.y&id=ec60172af2c6f7c4a59a22fc1ba68729ea3a2e4d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jack 1374 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 13 08:48:31 2021
InstallationDate: Installed on 2021-03-10 (2 days ago)
InstallationMedia: Ubuntu 20.10
I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.
--
You received this bug notification because you are a member of Kernel
Packages, wh
This problem report is related to 1910588. I am running kernel 5.8.0-36
now and found that the dd command I was using to test zfs raidz1
performance worked the last time I tried. dd now provides speed
measurement skewed by arc though (2.0GB/s).
I have run memtest86 on this machine recently. Four p
Public bug reported:
I reported what I believe to be the same problem yesterday with kernel
-34 but running the rsync command to create a backup.
I can cause the system to hang with the following commands:
dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k
cp Win10_20H2_v2_English_x64.iso
Public bug reported:
I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
requiring machine reset; no response from mouse or keyboard. No response
to ping from a windows machine. All drive activity stops. The hang
occurs with the backup drive connected via sata and via usb3 (adapte
This offending package for bug is proving very difficult to pin down. I
have tried to sequentially regress all the packages that the recovery
kernel boot are likely to use back to their eoan versions on a 20.04
installation. In each case, I reinstalled the kernels afterwards to
insure that the init
This issue extends to the daily desktop cd image for focal. When booted
from a usb memory stick and the safe graphics (which uses nomodeset) is
selected from grub, the screen remains black and never completes
booting. This issue doesn't exist with the current 19.10 cd images which
boot without issu
I have been able to eliminate the focal 5.4.0-26-generic kernel packages
as the origin of this bug. Manually installing those onto an
installation of Ubuntu 19.10, produced a fully functional boot. More
importantly the recovery mode boot from grub worked fine. So the problem
under 20.04 would appea
This problem doesn't exist for current Ubuntu 19.10 under its
5.3.0-46-generic kernel. The recovery mode boots fine on the same
hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
Oddly, so far I have not found a Ubuntu mainline kernel build that
doesn't show the problem.
5.3.18-050318-generic
5.4.0-050400-generic
5.4.25-050425-generic
5.4.28-050428-generic
5.6.6-050606-generic
all produce the hang at loading the ramdisk when booting the recovery
kernel with the default us
Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel
packages on Ubuntu 18.04 produces the same bug of nomodeset preventing
the recovery dialog from appearing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ub
If I remove 'nomodeset' from the grub kernel options for the recovery
kernel under 20.04, the hang in booting at loading the ramdisk is
eliminated. The recovery dialog appears as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Public bug reported:
On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery
mode from grub hangs on loading of the ramdisk with the Recovery Menu
dialog never appearing. This problem doesn't exist for a fresh install
of Ubuntu 18.04 updated to the current package updates. In that
This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...
1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo up
Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-driv
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launc
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.
--
You received this
With reference to post#50, it turns out my problems were caused by the
5.3 kernel not handling the nvidia gpu usb-c driver properly.
I could fix using:
sudo sh -c 'echo "blacklist ucsi_ccg # Fix suspend freeze bug" >>
/etc/modprobe.d/blacklist.conf'
See: https://bugs.launchpad.net/ubuntu/+source
Public bug reported:
The most recent kernel updates resulted in...
ii linux-image-5.4.0-24-generic 5.4.0-24.28
amd64Signed kernel image generic
ii linux-image-generic5.4.0.24.29
amd64
Today I upgraded from Linux Mint 19.2 to 19.3 (Tricia) and ran into the same
issue.
The PC suspends correctly, on resume I see the Mint logo, then after some
seconds the machine reboots.
There's nothing obvious in the logs between suspend and the reboot.
I don't have an option in UEFI to disab
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1865197
Title:
trusty/linux-azure: 4.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1863274
Title:
eoan/linux-azure: 5.3.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1863285
Title:
bionic/linux-azure: 5.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1863344
Title:
xenial/linux-azure: 4.
I'm seeing this problem on linux 5.3.0-40-generic but with a different
error log:
[ 98.743076] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
43.2.23.17
[ 98.743079] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
[ 98.743080] iwlwifi :00:14.3: Found debug configu
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1862818
Title:
xenial/linux-azure: 4.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1862398
Title:
eoan/linux-azure: 5.3.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1862405
Title:
bionic/linux-azure: 5.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1862239
Title:
bionic/linux-azure: 5.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1858533
Title:
bionic/linux-azure: 5.
Testing complete
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1859798
Title:
xeni
Testing complete
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1859820
Title:
eoan
Testing complete
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1859797
Title:
trus
Hi all,
Noticed this in my Ubuntu 19.04 dmesg:
[2.094782] platform eisa.0: Probing EISA bus 0
[2.094783] platform eisa.0: EISA: Cannot allocate resource for mainboard
[2.094784] platform eisa.0: Cannot allocate resource for EISA slot 1
[2.094785] platform eisa.0: Cannot allocate re
On my Disco Dingo see this also, though it doesn't seem to have any
negative effect.
kernel: 5.0.0-16-generic
secureboot: Secure boot could not be determined (mode 0)
[2.243394] Loaded X.509 cert 'Build time autogenerated kernel key: ...'
[2.267416] Couldn't get size: 0x80
For me ant_sel=0 "zero!" was the magic key. Took me a week of messing
around until I realized one cannot only select 1 or 2 but also 0. Try
out with these:
sudo modprobe -r rtl8723be
sudo modprobe rtl8723be ant_sel=0
iwlist scan | egrep -i 'ssid|quality'
sudo modprobe -r rtl8723be
sudo modprobe r
This problem still exists for me on debian testing with 4.19.0-1-amd64
#1 SMP Debian 4.19.12-1
Only if I put my laptop directly next to a device emitting a wifi
network I am able to connect. Few meters away it already becomes
unusable. ant_sel=1 makes it worse. ant_sel=2 not better.
Detailed info
I'm also experiencing this bug with the latest debian testing release:
Linux lemon 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
In reality, it is a typical issue with Broadcom arrange connectors in Ubuntu.
An alleviation is that Ubuntu gives extra drivers explicitly to Broadcom
connectors. Be that as it may, the issue is that to introduce extra drivers in
Ubuntu you will require a system association. On the off chance th
FWIW mine appears to have hung during a hidden (invisible to me) step
where it was attempting to set a MOK. I had to first kill the existing
dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh
to #!/bin/bash (I was getting a local variable error), then manually run
/usr/bin/perl
Hey folks, just piping in that I am also having this problem. I am on
an encrypted disk, and the build of the kernel modules just hangs.
Please let me know if there is anything I can provide to assist in
debugging.
Note that there appear to be two other related / duplicate bugs: 1769327
and 17756
Public bug reported:
sound says dummy output, but it doesn’t appear to be detecting any
hardware
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-151-generic 3.13.0-151.201
ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39
Uname: Linux 3.13.0-151-generic x8
I'm happy to create a new bug report for this, however before I do I
wanted to follow up here first. I've been working on a bionic VM
template this week and the issue has resurfaced. Client (18.04) reboots
daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later,
the CIFS mount poin
this bug seems fixed for me since updating E7470 BIOS to v1.18.5, which
was released 12/22/17 here:
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=ND42N&lwp=rt
as this leaves us with 0 affected users, I think this bug can be closed.
--
You received this bug notificati
1 - 100 of 173 matches
Mail list logo
