Confirming that it’s fixed on the same machine with 550.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2061079
Title:
GTK-ngl (new default backend) rendering
** 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
** 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/remo
The issue is in zfs-linux, where the merge from debian
http://launchpadlibrarian.net/535966758/zfs-
linux_2.0.2-1ubuntu5_2.0.3-8ubuntu1.diff.gz once again reverted some of
the fixes and rolled back the patch to an earlier version. The fix was
already reverted erronously in hirsute during the
** 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
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
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:
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
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
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
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.
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
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
--
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
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
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
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
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:
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"
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
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=
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
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
** 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
** 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
$ ./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
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 &
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
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
** 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 =>
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
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
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
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
** 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
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
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
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
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.
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
** 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
** 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
** 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
** 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
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
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
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
47 matches
Mail list logo
