apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379667/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379663/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379665/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379662/+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/1881699
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379668/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379670/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379664/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379672/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379666/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379669/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379661/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379671/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379660/+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/1881699
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379658/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
After a fresh boot and login, there is no analog output. Only HDMI and
bluetooth are available.
It becomes available when I kill pulseaudio with 'pulseaudio -k' but the
sound indicator only shows 'dummy' output and
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379659/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379657/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379656/+files/CRDA.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/1881699
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 1881699
and then change the status of the bug to 'Confirmed'.
If, due to the
The kernel team are tracking a couple of 'sof' audio issues that relate
to 10th gen Intel systems. Also there seems to be a kernel crash in i2c
code that might relate to audio.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
@Miguel,
Thanks for the report of this issue. This is a known issue/limitation
that the USB peripheral driver is not in sync of the Hotkey LED status.
The Hotkey LED should connect to the audio codec by GPIO.
We will check with the Desktop team to see if we can do some improvement
in the future.
Please note that the following patches have been skipped as they were already
applied to xenial/linux:
*Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6"
*net: ipv6: add net argument to ip6_dst_lookup_flow
*net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Patches:
https://lists.ubuntu.com/archives/kernel-team/2020-June/110635.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1881525
Title:
in kernel amdgpu failed with W5500
Thanks for the update Zakhar, but do we still have other sources that
can help us to fix this one? I wonder. Thank you again.
Marco Blakey
https://andwebtraffic.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can confirm it, Im using Linux Mint 19.3 cinnamon with an AMD/GPU
radeon vega mobile gtx8, and everytime I install the kernel, the laptop
can't seem to shutdown or reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: ubuntu => linux (Ubuntu)
** Tags removed: tocuhpad
** Tags added: focal touchpad
--
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/1881534
Title:
Touchpad not working
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 1881534
and then change the status of the bug to 'Confirmed'.
If, due to the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
The touchpad on my Lenovo Thinkbook is not being detected at all. I have
attached the devices list. I also tried installing ubuntu 20.04 and even
in the latest version touchpad is not detected.
** Affects: linux (Ubuntu)
Importance: Undecided
this bug is still not solved in 20.04
--
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/1670041
Title:
Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
1535)
@kaifengheng
--
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/1881213
Title:
System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
Status in linux package in Ubuntu:
Cover letter for the patchset: https://lists.ubuntu.com/archives/kernel-
team/2020-June/110613.html
--
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/1880032
Title:
[linux-azure]
The following patches weren't necessary because they were already
applied via upstream stable updates:
f2c33ccacb2d PCI/PM: Always return devices to D0 when thawing
Via https://bugs.launchpad.net/bugs/1858427
2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume()
Via
** Package changed: ubiquity (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/1881676
Title:
HyperX Cloud Alpha microphone not detected
Status in linux package
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
You have been subscribed to a public bug:
When using the HyperX AMP, the microphone is not detected. This is a
known issue with the mainline kernel, however was patched in release
5.7.0. This occurs on Ubuntu 20.04 LTS.
https://lkml.org/lkml/2020/4/4/197
ProblemType: Bug
DistroRelease: Ubuntu
Confirm affecting Ubuntu 20.04:
---
Processing triggers for initramfs-tools (0.136ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic
W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module
amdgpu
W: Possible missing firmware
Testing PPA:
https://launchpad.net/~shanelin/+archive/ubuntu/linux-firmware-amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1881525
Title:
in kernel amdgpu failed with
Patches submitted to the SRU cycle:
https://lists.ubuntu.com/archives/kernel-team/2020-June/110609.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110610.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110611.html
The 5.3 and 5.4 kernels already contain those patches. The only kernel
left without those fixes is the 4.15 kernel.
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Eoan)
Importance: Undecided
Status: New
**
Dear Sirs,
Please feel free to close out this Bug.
The Solution as mentioned above was to run with the 4.15.0 Nucleus.
The problem was probably caused by the fact that my Computer System was 10+
years old
and so it couldn't support the new HWE code in the 5.x Series.
Thank you everyone who took
Dear Sir,
I wish to thank you for your suggestion about using a different
and older Nucleus.
I didn't understand initially about the difference between the
4.x and 5.x Versions.
After I did research on them, I installed the 4.15.0 release.
It has been running perfectly for the past week so I
** Changed in: linux (Ubuntu)
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/1880049
Title:
Using Lakka with Intel GVT-g freezes the host system
I tested 5.7.0-050700-generic, and the system didn't crash. I'm able to
use Lakka from QEMU most of the times. Once, a GPU hang happened, but I
was able to restart LightDM to fix it.
The attached file is the card0/error after the GPU hang.
** Attachment added: "card0/error"
This still happens on a fresh Focal install using linux-
image-5.4.0-26-generic version 5.4.0-26.30
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: bionic
** Tags added: focal
--
You received this bug notification because you are a member of
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/1881675
Title:
iwlwifi Microcode SW Error
Public bug reported:
Sometimes, this bug happens and keep logging as long as I do not not
shut down the computer. Internet becomes irresponsive, and the whole
computer is slowed. It will keep logging until saturating the hard
drive. I had to format the hard drive and reinstall to be able to use
** Changed in: snapd
Status: New => Incomplete
--
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/1879630
Title:
No sound output from HDMI audio
Status in snapd:
Incomplete
Status
Thanks Vic. I see from logs that the HDA codec is an ALC 233, which
happens to be the same Realtek HDA codec I have in my Lenovo Thinkcentre
machine that's running UC20 20200529.3. Unfortunately my Thinkcentre
doesn't have any HDMI ports, but I was able to send sound through one of
the
I looked at this again. The GPU does scale down sometimes. But still the
power consumption has without any doubt degraded a lot between 51 and 53
minor versions. The difference is immediately seen by either by looking
at powertop or the power consumption or expected battery time in freshly
booted
I tried all 4.16 (1 to 18), none of them work. Should I bisect from
4.16-rc7 to 4.17 or to 4.16.1?
--
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/1879276
Title:
Esata port is dead after
Verified by code inspection on Bionic (4.15.0-102) and Xenial
(4.4.0-180). I don't have a system with Skylake available; there's an
user that experienced this and I'm waiting on his test, as soon as he
responds, I'll comment here. But marking as verifying anyway based on
the code lookup, we need
Public bug reported:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline commits
are:
64caea53e07f ("HID: hyperv: Add a module description
I can also confirm that using these 4 commands sound works perfectly
fine on UX533FTC. It seems that the only last 2 commands are needed to
be executed in sequence, but using all 4 commands works fine too (or
maybe I can't tell the difference? lol).
hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
@ Jeremie Tamburini (jeremie2)
Thks mate. It works perfectly.
Did exactly as you said and now my sound card is back on.
--
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/1864871
Title:
For me just usual reboot is enough. I reboot the notebook, start some
application that plays sound and then execute the commands below. And
everything works as a charm on my UX534FTC.
About reset - try also "alsa force-reload" and maybe the following
command:
hda-verb /dev/snd/hwC0D0 0x51 0x7ff
Nice. One more thing - if you can't get sound to work, then you need to:
1. Completely shutdown the laptop
2. Unplug charger
3. Wait few seconds
4. (optional) plug charger back
5. power on and apply commands. Sound works.
Is there something else we are missing? Like power reset command or
I found it! I found the magic sequence!!!
srgk@zen~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b
[sudo] password for srgk:
nid = 0x20, verb = 0x500, param = 0x1b
value = 0x0
srgk@zen:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b
nid = 0x20, verb = 0x477, param = 0x4a4b
value = 0x0
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Similar problem with:
- Ubuntu 20.04 LTS
- Fujitsu LifeBook A530
- $ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
THE PROBLEM:
No sound. Gnome audio system settings shows "Dummy Audio" as output device.
Trying with
*** This bug is a duplicate of bug 1879559 ***
https://bugs.launchpad.net/bugs/1879559
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Dumped all the coefficients when the sound is working and without any
distortions: http://alsa-
project.org/db/?f=79b20740c9abbd7427f166208b5a6a2e6449a174.
NOTE: Dumping coefficients can be enabled via
echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef
--
You received this bug
Gentle bump to raise visibility. In more information is needed please
let me know.
Thank you!
--
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/1875199
Title:
[NUC8CCHK][HDA-Intel - HDA
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (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.
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz
[...]
03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop
objects [FAIL]
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 1881643
and then change the status of the bug to 'Confirmed'.
If, due to the
Alsa-info time:
- Ubuntu Live CD in VM after power cycle:
http://alsa-project.org/db/?f=a3bb092b7964d28cc8a206d0619172472653b48b
- Ubuntu Live CD in VM after Windows VM was started:
http://alsa-project.org/db/?f=316d1051a370a045a3e14d2fc456c6d06fd34ae4
--
You received this bug notification
The strange thing is that built-in microphones ARE actually working on
my notebook out of the box. At the least sound meter IS moving for
internal microphones in the settings. And I also found out another bug
when the topic starter has internal microphones working perfectly fine:
BTW I'm glad that those commands helped you. And good job in command
dissection here!
--
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/1850439
Title:
No sound on ASUS UX534FT
Status in
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (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.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
A bit background on how I figured out those 2 commands. So let's say you
have 6 commands in total:
A command
B command
C command
D command
E command
F command
Start executing commands one by one, from top to bottom (do NOT resort
them). Let's assume your sound starts to work after command E. So
For me (Asus UX533FTC) sound works fine when I execute those 2 commands
after boot.
However, when I was testing all those commands, sound did not always
worked. These steps fixed it (run either after or before commands, or
even right after boot):
1. Go to pavucontrol --> configuration
2. Change
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/1881638
Title:
touchpad not appearing in
so what is the state of this with ubuntu server 20.20 ?
I added “dtoverlay=dwc2,dr_mode=peripheral“ to
/boot/firmware/usercfg.txt but also never seeing the USB-C ethernet show
up when connected to my Ubuntu 18.04 laptop. Then again I might be
missing the equivalent of “modules-load=dwc2” as noted
Public bug reported:
touchpad has been frozen for ~1 hour. Doesn't appear when checking
xinput --list or other lists of hardware connected to the computer.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-33-generic 5.4.0-33.37
ProcVersionSignature: Ubuntu
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=206459
Importance: Unknown
Status: Unknown
--
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/1860284
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
Public bug reported:
Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing
CONFIG_NLS_ASCII in the arm64 kernel build options.
This option is enabled on the other kernel builds but somehow was overlooked on
arm64 appears to affect our ability to access logs via
Public bug reported:
Hey there!
I am encountering a bug in Bluetooth menu in drop down menu at top right
corner.
Whenever i turn off my Bluetooth there is no option to turn on there. It
shows two option turn off and Bluetooth setting. After I open setting
and try to turn it on from there it
Another, shorter sample with warning (?) audio clip (play from terminal
when there is nothing more to do).
** Attachment added: "Sound sample - noisy sound from speakers 2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379388/+files/noisy_sound_notification.m4a
--
Here is the behaviour on my UX534FTC:
1. Power cycle.
2. Execute two commands from the Erikas' comment.
3. Start youtube video with sound.
Actual result: No sound from speakers.
4. Execute two commands again while the video is playing.
Actual result: Sound appears with the same quality as in my
The sound has a strange digital whistle (?) in it. This whistle be head
clearly with higher-pitch sounds.
** Attachment added: "Sound sample - noisy sound from speakers"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379380/+files/noisy_sound_speech_sample.m4a
--
Headphones are not working - there is nothing beyond some "alien" sounds
from headphones' speakers.
** Attachment added: "Alien noises from headphones"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379389/+files/headphone_not_working.m4a
--
You received this bug
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1881623
Title:
USB support missing in initrd
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
-
** Description changed:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
Public bug reported:
when using a gadget.yaml like:
volumes:
pi4-system-boot:
schema: mbr
bootloader: u-boot
structure:
- type: 0C
filesystem: vfat
filesystem-label: system-boot
size: 512M
content:
- source: boot-assets/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** No longer affects: apparmor (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
--
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/1645037
Title:
apparmor_parser hangs indefinitely
It looks like it doesn't happen with 5.7.0-050700rc7-generic. I cannot
be 100% sure as it happened randomly. I have got, however, something
suspiciously similar that has never happened before. It has happened
several times already, as randomly as when I got a kernel panic before.
Screen hangs for
Pinged in #ubuntu-kernel today for an update. It'd be good to have
groovy signed soon so we can then roll this out to focal users.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: apparmor (Ubuntu Xenial)
** No longer affects: apparmor (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
These seem to be bare minimum of commands to get audio working on my
Asus Zenbook UX533FTC:
hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf
hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74
For anyone wondering where to get "hda-verb" utility - install "alsa-
tools".
--
You received this bug notification
can confirm its effecting my 20.04 install as well
--
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/1873325
Title:
update-initramfs complains of missing amdgpu firmware files
Status in
Add me to the list of those having this issue, but also have a partial
fix. I am running a Thinkpad P50 with Nvidia display adapter. 18.04
was great, never any issues with suspend or resume. I upgraded to 20.04
a couple of weeks ago and immediately began encountering the reboot on
resume issue.
I apologize for the slow reply, a lot of stuff has been going on, and I
hit a snag. The device in question no longer boots reliably. I have not
been able to confirm, but I believe that the internal wifi chip is
failing, and when the device loads the wifi driver in the boot process
it crashes. If I
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/1881600
Title:
Touch Pad not detected on
1 - 100 of 127 matches
Mail list logo
