Sorry,
PC crashes after beginning to collect infos. Firefox open / then a
windows of collect open too ... begin to collect and crashes !
I started on recovery mode to run dkpg repare and pc says ... repare symbolic
line "/user/bin/python"
I run "Resume" to continue starting and crashes too ...
HIE,
I Think that I found where is Bugs for this problem. I create an other bug and
please, can you close this one ?
I putt the new reference here later
Bugs came from ACPI and addresses.
I had to boot by typing "ACPI=off" and so, Ubuntu 18.10 may be installed.
Problem... No sensors of CPU,
On forum, I saw that Bugs is on AMD with NVidia GEForce 1050
My PC : GL753VD ASUS ROG / 8 Gb Ram / GEForce 1050 / Core I7 7700
Since 2 years now
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Public bug reported:
Always the same bug See advent bugs please
Bug on the last version ... I charge the last daily build of to day --->
Always the same bug
On Nvidia site : Existing a driver 415 Version... Not possible to try !
Crashes
ProblemType: Package
DistroRelease: Ubuntu 19.
Hie, Too much bugs to restart pc. Finally after format hard disk, impossible to
install Ubuntu 18.04...
My PC : ASUS ROG GL753VD. Notebook . Bios change version (307)... No
possibility to put a bootable usb on CSM mode... Only EFI permiss. To restart,
I put Ubuntu 16.04 EFI, then upgrade with u
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209024/+files/IwConfig.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/17
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209025/+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/1799718
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209021/+files/AlsaInfo.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/17
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209032/+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/1799718
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209026/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209030/+files/PulseList.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/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209028/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209029/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209023/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209022/+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/1799718
Ti
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209027/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209031/+files/RfKill.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/1799718
Seems to be crashed !
Something blocks apport information
--
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/1799718
Title:
Ubuntu 18.10 fr FAN always ON 5 400 rpm
Status in linux pack
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1799718/+attachment/5209033/+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
It's an ACPI bug !
I make a bad thing about AMD While trying to correct colour resize
So, on recovery mode... Cleaning remove all files.
I try to install 18.10 on UEFI mode ... crash
I try to install Ub 17.10 UEFI mode Crash
I try to install 16.04.5 UEFI mode crash too
PC says error A
Propriétés de la table ACPI
Signature ACPI APIC
Table de descriptionMultiple APIC Description Table
Adresse Mémoire -7A712800h
Longueur de la table188 octets
OEM ID _ASUS_
OEM Table IDNotebook
OEM Revision01072009h
Creator ID AMI
Creator Revision00010013h
There is a problem here...
UEFISystème compatible UEFI Microsoft
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Dev
For info,
I charged Linuxmint 17 and all things ok (except drivers of wifi and sound)
But videos, others functions ok
I join you attachement of screen capture then crash
** Attachment added: "screen ca"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799718/+attachment/5209739/+files/
** 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/1799718
Title:
Ubuntu 18.10 fr FAN always ON 5 400 rpm
Status in linu
IT'S A problem of
ACPI Error bad adress ! Already exist
SEE ATTACHMENT !!!
How can I correct this?
For info, the same problem on linuxmint 18 and 19...
It seems to be with Ubuntu 16... If you upgrade from 14 ... Its ok, if you
install new... Crashes
** Attachment added: "IMG_20181108_002
I am sorry but i miggred on ubuntu 13.10 and everything is alright
except my smartphone using USB.
Correct on ubuntu 13.04 and no works on ubuntu 13.10 (salamander). No
way on MTP or MSC.
Is there a service not updated? gvfs updated last week and always the
same problem.
Thanks.
Guy Roche
Your patch makes sense Richard and I think it will be a good upstream
candidates. In all approaches you proposed, this is my prefered one
because this is the most flexible IMHO.
Tell me when you get a chance to test it and maybe John, you can confirm
this fixes it for you?
--
You received this b
On an installed packaged system, the files are in different directories
(and don’t have the .in extension as they have been built with the
prefix replacement). Their names and locations are:
/lib/systemd/system/zfs-mount.service
/lib/systemd/system-generators/zfs-mount-generator
--
You received
Great to hear John! Thanks for confirming and thanks to Richard for the
patch.
I’m happy to SRU it to focal once it’s proposed upstream. (Keep me
posted Richard, you can drop a link here and I will monitor)
--
You received this bug notification because you are a member of Kernel
Packages, which
signed) => Didier Roche (didrocks)
--
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/1882975
Title:
crypttab not found error causes boot failure with changes in zfs-
initramfs_0.8.4-1ubuntu
The patch doesn’t fix all instances of the bug (see upstream report
linked above). I think we should clarify that before backporting it.
--
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/1
I will have a look (I don’t remember if the grub task is due to the
grub.cfg generation or to grub code itself), but TBH, this is low
priority on my list (downgrading the bug task priority as such, as this
is a multi-system corner-case)
** Changed in: systemd (Ubuntu)
Importance: Medium => Low
CPC are seeing this issue in _all_ minimal cloud images testing with LXD
snap version 4.2 or greater. This blocks promotion of all minimal cloud
download images and blocks build and publication of both daily and
release cloud images.
--
You received this bug notification because you are a member
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
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/1850130
Title:
zpools fail to import after reboot on fresh
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1867007
Title:
zfs-initramfs fails with multiple rpool on
Hey Balint. I just added the task post ZFS upload (the upload was
yesterday and I added the task this morning) so indeed, there is some
work needed, part of it being in systemd.
Basically, systemd isn’t capable of mounting datasets when pool names are
duplicated on a machine
zfs-mount-generator g
Thanks for your bug report! This is now fixed in zfs-linux
0.8.3-1ubuntu10 in focal.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packag
See my previous comment: this is only related to zfs-linux with the
version I mentioned. Also, we didnt’ make any change to grub for ZFS
since 26 February, and if you have an empty grub.cfg, this may be due to
other bugs, like multiple rpool/bpool, which isn’t what this one was
about. Ensure that y
This is probably because your bpool is not in the zfs cache file.
Either reinstall from the beta image which has a fix in the installer, or:
- clean up any files and directories (after unmounting /boot/grub and
/boot/efi) under /boot (not /boot itself)
- zpool import bpool
- zpool set cachefile=
Public bug reported:
As stated on bug #1876052, the default acceleration mode option is none
of the 3 nvidia settings option.
It’s displayed as "Performance mode" when you launch it for the first time,
however:
- default launch is Intel (so no performance mode)
- there is a "Use dedicated card"
Public bug reported:
Fresh install of 20.04 LTS with nvidia binary driver from our archive.
(dual Intel/Nvidia setup)
No setting change has been done. The card supports "On demand".
Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing
the same result:
- default launch -
Public bug reported:
Install zsys on a non ZFS system without the kernel module loaded leaded
to a segfault.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to z
Sorry Colin, this was ZSys and I targetted the wrong component when
filing batch-bugs for ZSys 0.5 upload.
Fixed in https://launchpad.net/ubuntu/+source/zsys/0.5.0.
** Package changed: zfs-linux (Ubuntu) => zsys (Ubuntu)
** Changed in: zsys (Ubuntu)
Status: Incomplete => Fix Released
--
We wrote on another bug report BertN45 to not upgrade your bpool. Only
power users will use zpool status command to list and we expect them to
know the implication.
I think I'll retarget this bug for preventing bpool upgrade.
** Summary changed:
- Confusing zpool status in Ubuntu 19.10 installed
Public bug reported:
As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: zsys (Ubuntu
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Changed in: grubzfs-testsuite (Ubuntu)
Status: New => Fi
Thanks Richard for digging in, the performance comparison and the valuable
upstream feedback and pointers.
Good catch about retrieving the master key written in old blocks with the
previous (fix) passphrase even if changed later on. It seems that trimming
could help. Do you think that we should
Public bug reported:
Following some debug of the docker.io package in universe, we (Canonical
CPC) discovered that the ubuntu-fan package from main and the netcat-
traditional package from universe were being installed.
This was due to the following dependency/recommends tree:
* docker.io (in un
It appears that a bug was already filed against netcat
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1780316
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1861704
Ti
One last thing: I think we should test this on rotational disk and
assess the performance impacts before pushing it as a default. This will
give us a good baseline to decide if this should be pushed or if we need
to add even more warnings on the ZFS install option.
--
You received this bug notifi
Thanks for testing the upgrade to 19.10. The only reason you would boot
with an older version of a kernel and zfs itself is due to your update
between 19.04 to 19.10 failed. Can you share the upgrade logs
/var/log/upgrade content and /var/log/dist-upgrade?
The weird part is that do-release-upgrade
The upgrade failed, in your logs, you have:
"/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.2.0-15-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=bf02ddd4-8d65-40d6-ab24-4fc8a5673dc6)
I: Set the RESUME variable to override this.
/etc
The issue seems to be related to a change in ZFS 0.8 initramfs script.
The initramfs script for ZFS does a normal ZFS import.
ZFS import now forces to export a pool before importing it back again on a
different system. This is a security feature to ensure the same pool isn't
imported on two diff
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
otherw
The meta-packages have been rolled back and the fix is in progress of
being applied and uploaded.
--
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/1779961
Title:
Boot delays with 4.15.0-24
Public bug reported:
Hi,
We're planning to share a new Cosmic minimal image for Azure including
the linux-azure custom kernel.
I have found boot speed increase from ~55s in non minimal image to over
6mins for minimal image.
I have gathered boot log, systemd logs and cloud-init logs for this
ins
** Attachment added: "cosmic minimal image with linux-azure 4.18.0.1002.2 (from
cosmic-proposed) boot log"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1795017/+attachment/5195337/+files/chohv4Va7Ahx7-vm-imagedebug-boot.log
--
You received this bug notification because you are
On request on IRC I have tried a new image with linux-azure
4.18.0.1002.2 from cosmic-proposed.
This too exhibited the slow boot
5min 19.070s (kernel) + 41.724s (userspace) = 6min 794ms
Full logs @ https://private-fileshare.canonical.com/~philroche/azure-
cosmic-20181001/
--
You received this
@kamalmostafa @mhcerri
I noticed that linux-azure 4.18.0.1003.3 was uploaded to cosmic-proposed
so I built a new test image.
For convenience I have imported your SSH keys to 'ssh
ubuntu@51.140.217.58'.
All logs and VHD etc. have been uploaded to https://private-
fileshare.canonical.com/~philroch
Myself and @kamalmostafa spoke and the issue is not obvious especially
as linux-azure is installed in the base image too which does not exhibit
the issue.
Although not obvious @kamalmostafa did suspect the issue to lie
somewhere with random number generation and a related package/kernel
patch.
On
Hey! Is this reproducible today? We made some performance improvements
on zsys since then.
Please also, use the apport hook to help debugging:
apport-collect -p zsys 1875767
** Changed in: zsys (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
Please run apport-collect to attach logs so that we can debug your setting.
@baling: why subscribing zsys to this bu? There is no mention of zsys being
used here, it seems directly a manual zfs setup.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification
Thanks for the confirmation :)
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomple
We will backport your patch to previous releases soon.
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils packa
** Description changed:
+ [Impact]
+
+ * Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
+ * The option is available on grub and will let you with a broken system,
partially cloned.
+
+ [Test Case]
+
+ * Boot
Can you try to reproduce an upgrade without your 40_custom file?
I don't think your pool manual upgrade has any link to this.
--
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/1843222
Ti
Public bug reported:
If /var/lib is a dataset not under /ROOT/, as proposed
in the ubuntu root on zfs upstream guide
(https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
with a race where some services, like systemd-random-seed are writing under
/var/lib, while zfs-mou
** Also affects: zfs
Importance: Undecided
Status: New
** Description changed:
- If /var/lib is a dataset not under /ROOT/, as proposed
- in the ubuntu root on zfs upstream guide
- (https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
- with a race where some
Marking the zfs-linux task as won't fix after looking more deeply about
cause/consequences of forcing -f on every boot:
- zfs 0.8, as told previously, tag with which system the pool was associated
with and refuse to import previously unexported pool, as they can still be
attached to any systems
Public bug reported:
There is a race between empty cache file for the mount generator and fstab
which contains /boot/grub.
With zfs on root, the generator is the only solution to avoid races. However in
0.8 it misses cache invalidation (when rollbacking or booting on other
datasets).
This is a
Public bug reported:
I have a problem similar to the bug #1599476, my system freezes when I
unplug my thunderbolt port if it is connected during startup.
What I have tested so far :
* If the thunderbolt is plugged at startup and I unplug it -> System freeze
* If the thunderbolt is not plugged at
The bug itself is fixed in the 4.11.0-041100rc5-generic kernel. But I
encounter regular freezes with this version of the kernel, and I have
ACPI related error messages.
Here are the ACPI messages from the dmesg :
[6.090510] ACPI Warning: \_SB.IETM._ART: Return Package type mismatch at
index
Public bug reported:
I can reproduce it approx on 2 of 3 trials.
1. Get the brightness up (not minimum) of the internal monitor
2. Have an external monitor plugged in in the VGA cable
3. unplug the external monitor
-> the brightness of the internal monitor is set to minimum
-> the fn keys to chan
Public bug reported:
autopilot intel saucy machine hw for the kernel guys
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-3-generic 3.11.0-3.7
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic i686
AlsaVersion: Advanced Linux Sound A
I'm on the latest kernel for 22.04 and I still can't get the wifi driver
to load I keep seeing the following:
[ 3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_gr
off" pid=522 comm="apparmor_parser"
[ 3.960935] iwlwifi
Public bug reported:
While testing the 6.5.0-6-generic proposed arm64 generic kernel I
encountered issues being able to use kdump.
After enabling -proposed and installing the -proposed 6.5.0-6 kernel and
rebooting I encountered the following:
`kdump-config show` shows `current state:Not read
I have confirmed that this issue with not being able to capture kernel
dump with a mantic arm64 kernel is not new. using the arm64 6.5 kernel
(6.5.0-5) in the release pocket I captured the following during test.
```
ubuntu@cloudimg:~$ sudo kdump-config show
DUMP_MODE: kdump
USE_KDUMP:
@xnox I have successfully verified that -proposed arm64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host. See
https://people.canonical.com/~philroche/20231003-mantic-minimal-
proposed-kernel/ for cloud-init logs, some debug output and test
I have also successfully verified that -proposed amd64 kernel
`6.5.0-7-generic` results in successful network configuration when
tested using qemu on an amd64 host with older hardware (ThinkPad T460
with 6th gen intel i5 which is the same hardware which we were able to
reproduce the issue on previo
Public bug reported:
Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing
a regression in our cloud image tests. The test runs the following:
```
lxd init --auto --storage-backend dir
lxc launch ubuntu-daily:mantic mantic
lxc info mantic
lxc exec mantic -- cloud-init status --
cloud minimized and non minimized images have now been tested with
6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite
which was failing and which is the test suite which prompted this whole
thread. +1
--
You received this bug notification because you are a member of Kernel
Packa
https://bugs.launchpad.net/cloud-images/+bug/2038894 is a related bug to
track specifically the introduction of listening port 5353
--
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/2032933
T
Public bug reported:
* Canonical Public Cloud discovered that `chronyc -c sources` now fails with
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in
linux-azure and linux-gcp kernels (6.8.0-1005.5)
* Disabling AppArmor (`sudo systemctl stop apparmor`) completely results i
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrony (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecid
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
** Changed in: snapd (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux-aws (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu Noble)
Status: New => Fix Released
**
** Also affects: linux-gcp (Ubuntu Noble)
Importance: Undecided
Status: New
--
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/2063315
Title:
Suspend & Resume functionality bro
Ack on both. Simple configuration files, simple packaging and build
system. All good +1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-topology-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1862776
Title:
[MIR] alsa-ucm-conf & a
$ ./change-override -c main -S alsa-ucm-conf
Override component to main
alsa-ucm-conf 1.2.2-1 in focal: universe/misc -> main
alsa-ucm-conf 1.2.2-1 in focal amd64: universe/libs/optional/100% -> main
alsa-ucm-conf 1.2.2-1 in focal arm64: universe/libs/optional/100% -> main
alsa-ucm-conf 1.2.2-1 in
** Changed in: zsys (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
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/1875767
Title:
When operating install/removal w
** Changed in: grub2 (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
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/1867007
Title:
zfs-initramfs fails with multi
Public bug reported:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O normalization=formD
-O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubuntu_123456/var
** Description changed:
-
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubun
** Description changed:
# zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
# zfs create rpool/ROOT -o canmount=off -o mountpoint=none
# zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
# zfs create rpool/ROOT/ubuntu_
** Description changed:
- # zpool create -o ashift=12 -O atime=off -O canmount=off -O
normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2
- # zfs create rpool/ROOT -o canmount=off -o mountpoint=none
- # zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/
- # zfs create rpool/ROOT/ubuntu_
** Bug watch added: Github Issue Tracker for ZFS #8833
https://github.com/zfsonlinux/zfs/issues/8833
** Also affects: zfs via
https://github.com/zfsonlinux/zfs/issues/8833
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Public bug reported:
[3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_gr
off" pid=522 comm="apparmor_parser"
[3.960935] iwlwifi :00:14.3: CSR_RESET = 0x10
[3.960965] iwlwifi :00:14.3: Host monitor b
This has been going on for a while but since the last linux firmware
update the ax201 card is not working at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2008706
Tit
Can we get a confirmation if this issue will be fixed at some point or
can we get a workaround ?
--
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/1874241
Title:
iwlwifi intel ax20
Public bug reported:
We in the Canonical Public Cloud team have received report from our
colleagues in Google regarding a potential performance regression with
the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
performed using the linux-gkeop and linux-gkeop-5.15 kernels.
I have v
1 - 100 of 156 matches
Mail list logo
