Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (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/1881
** 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/1883598
Title:
efi: Restrict efivar_ssdt_load when the kernel is locke
Hi Jeff
the 18.04 worked fine ,so we are facing issue of UEFI+20.04 only on 20.04 on
this server S3260 M4.
Let me know is this workaround recommended of below steps/
Usually whenever a OS is installed in UEFI mode, after the OS install, boot
loader will automatically create a boot entry mappin
Public bug reported:
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor= Product=0003 Version=
N:
@Kai, ideally the kernel fix would resolve the issue, unsure which
userspace workqround is better
--
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/1878351
Title:
System shutdown directly b
You have been subscribed to a public bug:
I have a dual monitor setup - primary screen is the internal display
(laptop), secondary screen is an external monitor connected via VGA out.
I have been using Night Light screen tinting since 19.10. The schedule is set
to Sunset to Sunrise.
it turns on
@Sebastien
I doubt that kernel fix can really solve the problem. If a use press the
power button twice very quickly, it perhaps to run into the same
problem. I think we still have to debounce or adjust the original commit
of https://bugzilla.gnome.org/show_bug.cgi?id=688076.
Recently, a lot of de
I'm quite surprised and still skeptical as to whether it was resolved in
some other package. But the kernel you say fixed it is in official
updates now so that's good enough for me.
** Package changed: gnome-settings-daemon (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: T
We are having the same bug (I believe) after upgrading from kernel
linux-image-4.4.0-178-generic to linux-image-4.4.0-184-generic.
We have around 100 VMs there are affected. For now, we have rolled back
to the previous kernel. I am not sure why but not all VMs are affected,
from what I have found,
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1856387
Title:
Freezing on boot since kernel 4.15.0-72-generic re
A debounce delay just doesn't sound right.
If a user press the power button twice and the kernel dutifully reports
two events, why a debounce is required when there are _actual_ two
events?
If there's a race between gsd and gnome-session, proper ordering should
be imposed, instead of adding a del
** Tags added: sru-20200608
--
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/1845860
Title:
test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is
required, but is missing or
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1882930
Title:
focal/linux-raspi: Upstream raspberrypi patchs
if gnome-session handle those two events, then it goes to prepare_shutdown
which is current result.
If the original implementation of
https://bugzilla.gnome.org/show_bug.cgi?id=688076 is correct, then it is
expected result, and we accept it.
Unless the commit of https://bugzilla.gnome.org/show_
gnome-session did handle those two events, and it goes to prepare_shutdown
which is current result.
If the original implementation of
https://bugzilla.gnome.org/show_bug.cgi?id=688076 is correct, then it is
expected result, and we accept it.
Unless the commit of https://bugzilla.gnome.org/show_
Public bug reported:
[Impact]
On HP Thunderbolt Dock, unusable SPDIF can be selected as output from
PulseAudio.
[Fix]
Disable IEC958 (SPDIF) through ALSA UCM.
[Test]
With the UCM applied, `pactl` and audio panel in gnome-control-center no longer
have SPDIF option.
[Regression Potential]
Low.
Public bug reported:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $
Reproducible.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883676
Title:
ZFS performance drops suddenly
Status
I don't seem to have this problem on Ubuntu 18.04, 5.4.0-37 hwe-edge
kernel. I don't seem to have this problem on Ubuntu 20.04 live session
either. At least. speedtest can't reproduce the issue. Even tried
rebooting from Windows. Those who have the problem and dual boot, could
you try upgrading you
You have been subscribed to a public bug:
The servers will be running fine for some time and suddenly will freeze.
It won't even respond to ping requests. We have to reboot the servers
again to bring it back online but it won't be stable and will not
respond again.
** Affects: linux (Ubuntu)
It was a regression though yes, I am not sure in which package.
Previously it was working as intended. But I noticed the buggy behavior
some time beginning of June and hence the initial bug report.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
** 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/1883681
Title:
System freezes on specific kernel
Status in linux package in Ubuntu:
New
Bu
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 1883681
and then change the status of the bug to 'Confirmed'.
If, due to the nature
debdiff for Groovy
** Also affects: alsa-lib (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: alsa-lib (Ubuntu Focal)
Importance: Undecided
Status: New
** Patch added: "alsa-lib_1.2.2-2.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1
debdiff for Focal
** Patch added: "alsa-lib_1.2.2-2.1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+attachment/5384335/+files/alsa-lib_1.2.2-2.1ubuntu1.debdiff
** Tags added: oem-priority originate-from-1880102 stella
--
You received this bug notification
We had the same behaviour like Dennis!
Kernel Panic after aprox. 4 our on kernel 4.4.0-184
Unbound installed as well with version 1.5.8
Unfortunately i have no crashdump by hand, but our panic was "same" as Dennis
with ipv6 messages.
--
You received this bug notification because you are a member
** 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/1879973
Title:
There is no sound from the built-in speakers and does
apport information
** Tags added: apport-collected xenial
** Description changed:
- The servers will be running fine for some time and suddenly will freeze.
- It won't even respond to ping requests. We have to reboot the servers
- again to bring it back online but it won't be stable and will not
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384339/+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/1883681
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384344/+files/UdevDb.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/1883681
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384343/+files/ProcModules.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
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384340/+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
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384342/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384345/+files/WifiSyslog.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/bug
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1883681/+attachment/5384338/+files/CurrentDmesg.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/1883681/+attachment/5384341/+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
Please mark this as fixed. Not a bug
Issue fixed.
Bydefault 18.04 marked incorrect disk for the boot loader installation
which caused the machine not boot properly. Due to this EFI mounts from
secondary disk causing the booting issue.
Marked the correct disk during installation by choosing bootl
Please mark this bug as fixed. This is not a bug
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1882195
Title:
Dell Ali
I can confirm that we experienced the same problem on one VM after upgrade from
4.4.0-179-generic to 4.4.0-184-generic last weekend. Since the rollback to the
last working kernel this VM is running stable for over 25h now.
Ubound Version 1.5.8 is also installed and running on this VM
Don't have a
Didn't see this on E-AWS 5.3.0-1024.26 ARM64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1847982
Title:
memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E
Stat
Didn't see this on E-AWS (5.3.0-1024.26) with those instances mentioned
in comment #1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1855817
Title:
signal06 from ubuntu_ltp_syscalls
Didn't see this on Eoan GCP as well. Closing this.
5.3.0-1027.29-gcp
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Although its recognised by the terminal and is enabled in settings the
touchpad still doesnt work, Output of xinput in terminal
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave p
Could you try a similar fix?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/comments/3
--
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/1861610
Title:
'Elan touchpad' not de
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/1883696
Title:
Elantech ETPS/2 Touchpad not w
While bysecting (I hope to complete tomorrow) I found a workaround (that
works for me on Acer 720P).
I always had tpm_tis.force=1 on the kernel command line.
Now I added tpm_tis.interrupts=0.
Wakes fine now with linux 5.6.0.
Full command line:
Kernel command line: BOOT_IMAGE=/@boot/vmlinuz-5.6.0
(In reply to Ferry Toth from comment #41)
> While bysecting (I hope to complete tomorrow) I found a workaround (that
> works for me on Acer 720P).
>
> I always had tpm_tis.force=1 on the kernel command line.
> Now I added tpm_tis.interrupts=0.
>
> Wakes fine now with linux 5.6.0.
First of all, t
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
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.
https://bugs.launchpad.net/bugs/1875456
Title:
Azure diagnostic/serviceability impr
Changing to confirmed as requested in comment #2.
** 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/1883681
Title:
Syst
Same thing here. In my case, the computer keeps booting into emergency mode,
with output like in #5, and some additional ACPI errors.
I changed COMPRESS to gzip as described in #47, but not back to lz4.
Now the computer keeps booting into emergency mode with the message "/dev/sda2
clean" (which i
The issue can't be reproduced anymore.
** Changed in: linux-signed-azure (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1858495
@Ian,
Did you add dtoverlay=vc4-fkms-v3d in the config.txt?
This is the log on my board, looks like there is no error so far:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1027-raspi2 #29++v3dv2 SMP Mon Jun 15 22:26:13 CST 2020
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ubuntu:~$ dmesg | grep drm
The attachment "alsa-lib_1.2.2-2.3.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,
"If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to
COMPRESS=gzip
then the error is fixing."
Just changed it on a fresh install of 20.04 and the problem is still
happening.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks for you fast reply.
This is the same behaviour from bug: 1880580, that I wrote.
I have updated and can only continue verify on the latest 20.04, not 18.04
anymore.
This is what I have done so far now.
I tried you suggested solution. I first had to remove /etc/zfs/zpool.cache in
order to
I think I'm having the same issue as well, though due to a mysteriously
broken 5.4.0 kernel (all of them in fact won't pass 'loading ramdisk'
before system restart) I'm running version 4.15.0 on 20.04LTS whether or
not that could be it I don't know. Apologies, I'm not a software person.
--
You re
ok after adding that line to the config.txt it works, but GNOME is
glitching with multiple windows open, thats another issue though.
--
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/18
** Changed in: rtkit (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to ma
I just installed the ubuntu-desktop, and run glxinfo -B, it indicates
the v3d is used, and run glxgears, it could run without any crash, looks
like the v3d driver is more stable than before.
And I already backported all v3d patches from rpi-5.4.x to ubuntu 5.3
kernel. I have no idea how to fix the
Doing more testing, and now that I see this "feature" disabled, I don't
think it always turned off the monitor. Looks like half of the time
linux-image-5.4.0-33-generic failed to turn it off, but it still did NOT
hang the entire system like linux-image-5.4.0-37-generic does.
Monitor details
$ sud
i dont have an idea, all i did to check was glxinfo | grep renderer
--
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/1850876
Title:
CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eo
Thanks fcole90.
Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-
oem-5.6/+bug/1881120
--
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/1877849
Title:
conflicting pac
window glitching does not happen in XFCE, seems like a GNOME problem
--
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/1850876
Title:
CONFIG_DRＭ_V3D is disabled for linux-raspi2 of e
Hi Arthur, good news - there are currently Bionic and Xenial AMIs with
the fix! I've tried the following AMIs, and they have the fix:
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200610 -
ami-025201fa53cf4d031
ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20200610 -
ami-0a0d
Yes, I think it is related to dual booting and the source of the problem
might be indeed in the Windows driver leaving a setting on the card that
the fw and driver in linux cannot cope with. Rebooting to linux from
Windows causes a lot of trouble, but rebooting from linux to linux
solves it. (Maybe
Public bug reported:
I am not able to get my wireless device to connect to an AP using WPA2
(personal). I can create an SSID with no security, and it can connect
with no issues.
03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602
802.11ac Wireless LAN SoC [14e4:43ba] (rev
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/1883746
Title:
brcmfmac won't connect to wpa2
** Summary changed:
- brcmfmac won't connect to wpa2
+ brcmfmac with 14e4:43ba won't connect to wpa2
--
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/1883746
Title:
brcmfmac with 14e4:43b
--- Comment From naynj...@ibm.com 2020-06-16 13:03 EDT---
Hi,
I followed the steps from link -
https://wiki.ubuntu.com/Testing/EnableProposed
And have installed kernel:
5.4.0-38-generic for testing.
I am looking now for the key. I am not able to find one in this link -
https://launchpad.
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
I tried to reproduce the issue with the latest 4.15.0-1089 kernel and
the virtual machine started without issues.
This bug might be the same as the one that was reported in bug 1881072,
which was fixed in -1089.
Do you mind validating this issue again now with the 4.15.0-1089?
--
You received t
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.1
---
zfs-linux (0.8.3-1ubuntu12.1) focal; urgency=medium
* Backport AES-GCM performance accelleration (LP: #1881107)
- backport of upstream zfs commit 31b160f0a6c673c8f926233af2ed6d5354808393
("ICP: Improve AES-G
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
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/1883774
Title:
wifi not working
Status in li
Public bug reported:
please help
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
U
** 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
+
Right, the debouncer doesn't seem ideal. I'm not convinced either by
upstream reply that forcing shutdown on another press is by design, imho
we should try to convince them that it is wrong
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Hi, since 'proposed' belongs to the official archives
(archive.ubuntu.com/ubuntu) and packages from proposed are just located in a
special area there (we call it the proposed 'pocket'), kernels and other
packages from there that are signed, are signed with the standard and common
key.
Only a si
It worked! Thanks a lot! <3
--
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/1734147
Title:
corrupted BIOS due to Intel SPI bug in kernel
Status in Linux:
Unknown
Status in linux packag
When using a large directory with large names, I noticed a 50% increase
in the time it took to readdir the entire directory. With small names,
the increase did not seem noticeable enough. Tested on a VM with bionic,
no SMAP involved. Compared before memchr and after memchr. Need to
compare before a
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+attachment/5384527/+files/lspci-vnvn.log
--
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
Public bug reported:
Com o kernel: 5.4.0.37
Gnome: 3.36
Versão: 20.04 LTS
Network Manager: 1.22.10
A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/
options rt2800pci nohwcrypt = 1
Não resolvido
Connect for a period and then disconnect. Leaving the connection
unstable.
Sus
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+attachment/5384526/+files/version.log
--
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/188
The autopkgtests regressions are unrelated to this SRU.
Sure enough: the patch is for arm64 only, but the archs failing are
i386, ppc64el, and s390x.
The "regressions" also happen with the version in -updates, in the same
way as in -proposed.
makedumpfile [eoan/i386] [1]
Version
** Description changed:
- With kernel: 5.4.0.37
- Gnome: 3.36
- Version: 20.04 LTS
+ Com o kernel: 5.4.0.37
+ Gnome: 3.36
+ Versão: 20.04 LTS
Network Manager: 1.22.10
- The configuration that I tried em rt2800pci.conf em /etc/modprobe.d/
- options rt2800pci nohwcrypt=1
- Not solved
+ A con
Also, ppc64/s390 are being tracked here:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663
It's a common issue, and difficult to debug (if we run tests locally, we can't
reproduce and they succeeed).
Regarding i386, we should remove tests for i386 in Eoan and Focal.
Cheers,
G
I can confirm this happens whenever sch_fq is used, regardless of the
hardware/driver. This seems to be caused by kernel 4.4.0-180 adding a
backport of upstream commit:
695b4ec0f0a9 ("pkt_sched: fq: use proper locking in fq_dump_stats()")
This commit was pulled in as part of upstream stable 4.4.2
Hey Guilherme,
Thanks for the pointers and confirming these are not regressions, but
known issues. :)
--
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/1869465
Title:
Kdump-Tools: M
#17 looks like correct behavours. I also noticed #13 said battery was
acting without problems anymore. Is it still the case or did you have
problems when running #17?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
You're very welcome mfo, thanks for following this SRU in order to get
that released soon =)
--
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/1869465
Title:
Kdump-Tools: Makedumpfil
I'm having this issue in a fresh install of Ubuntu 20.04 with an Intel
NIC and the IGC driver.
https://askubuntu.com/questions/1244745/ubuntu-20-04-intel-network-
connectivity-issue-bug-in-igc
Should I submit new logfiles? Start a new bug?
--
You received this bug notification because you are a
--- Comment From naynj...@ibm.com 2020-06-16 17:36 EDT---
Thanks. I have PPA keys as those versions we tested last time.
I do not have common or standard key. Can you please share the tar or path for
that ?
Thanks & Regards,
- Nayna
--
You received this bug notification because you are
--- Comment From naynj...@ibm.com 2020-06-16 17:51 EDT---
To be specific.
sudo apt-key list
shows:
ubuntu@ltc-wspoon13:/$ apt-key list
/etc/apt/trusted.gpg.d/canonical-kernel-team_ubuntu_bootstrap.gpg
-
pub rsa1024 2010-12-
Hi,
Each signed object is published on in the repository under
/$suite/main/signed/$src-$arch. I.e. the linux in focal proposed signed
artefacts can be found at:
http://ports.ubuntu.com/dists/focal-proposed/main/signed/linux-ppc64el/
I.e. http://ports.ubuntu.com/dists/focal-proposed/main/signed/
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
OK, if there is no other problems, I will submit the SRU to ubuntu
kernel to enable the V3D driver.
thx.
--
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/1850876
Title:
CONFIG_DRＭ_
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encou
1 - 100 of 121 matches
Mail list logo
