Yep, it is a problem as of late!
On the up side, things could not be better on my end!!!
wayland on xfce is shaping up nicely, not perfect but credit where credit is do. 
I find it funny that some of the best buntu’s I have ever used are always a .10 series.
So far I just can’t break this one (zfs-root) of course I’m still waiting for an apparmor or grub update to wreck my whole world. 
(hint hint)
For me it started getting good with 24.04. Since that release Samba network has been a breeze and getting better with each release. Much more than that in addition.
It’s kind of fun seeing different outcomes for a version release, I had issue after issue on 24.04.
24.04.1 got better and continues thru 25.10.
I’ll make Hay while I can. 
I would say that your experience as described is in line with what I was thinking at the time. 24.04 was just a new beginning, Plucky and Questing are where that thinking was heading. I just know that I was ok with it. What differences we experience could boil down to what our primary activity is and was.
I just upgraded from Kubuntu 25.04 to 25.10. No issues so far. Also just built the latest github version of hyprland on Kubuntu Questing.
Just installed the latest Plucky ISO. Had success with both default and extended install. I started with a new partition table with 1gig fat32 efi partition, 34gig ext4 /, and rest ext4 /home. Also note that if you start with a new partition subiquity will create the boot partition automatically when your choose your desired boot drive at the bottom of the display.
I will test todays Questing ISO when I get one of those round things.
Questing ISO 5/10 extended install fails, curtin install. Default install = success.
Questing ISO 5/11 extended install fails (curtin fail reported). Default install = success. Right now if I want an extended install I would install an extended Plucky and then upgrade to Questing (as a work-around).
The best way is to use the Default install and then install the meta-package ubuntu-desktop that installs all the difference packages
Well! Install Plucky Extended from (USB3) ISO. = 13min. Full upgrade Plucky to Questing 25min. Total = 38min and thats on 4GLte mountain internet. It would take me more time than that to download LibreOffice alone. I think this operation depends on personal circumstances. If I was on my son’s fios internet 1Gig in 3sec I would do it your way.
I did a Lubuntu Plucky to Questing upgrade that took about 25 minutes.
Waiting for newest updates to see what develops.
5-11-2025 Xubuntu Dailey!
lsblk -o NAME,FSTYPE,TYPE,MOUNTPOINT | grep crypt && sudo lvscan
└─vda3 crypto_LUKS part
└─dm_crypt-0 LVM2_member crypt
ACTIVE '/dev/ubuntu-vg/ubuntu-lv' [22.98 GiB] inherit
All Good! I went lvm2/ext4 for a quick change.
EDIT: I forgot say if your haveing problems on the installer, and it shows activity but just continues, Press the arrow for the slide show a few times.
For Ubuntu devs that also update packages in Debian: The Ubuntu 25.10 Questing Quokka will be available as a Salsa CI release in about a week once Docker tags for Question are public: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/603
Salsa CI has been Ubuntu-compatible for almost a year now, and it is easy to use Salsa CI to check that packaging changes don’t regress anything testable in Ubuntu.
Will Questing ship Linux 6.16?
If you have an account on launchpad please subscribe mu bug 2110195
thanks
I had a person ask in support for 25.04 Kubuntu on ZFS-root encrypted.
I just can not in good faith recommend my current post here, but I had to try.
Outcome
OS: Kubuntu x86_64
VERSION_ID="25.10"
VERSION="25.10 (Questing Quokka)"
Host: 82JW (Legion 5 15ACH6)
Kernel: Linux 6.14.0-15-generic
Uptime: 3 mins
Packages: 2475 (dpkg)
Shell: bash 5.2.37
Display (AUOD1ED): 1920x1080 @ 120 Hz in 16"
DE: KDE Plasma 6.3.5
WM: KWin (X11)
WM Theme: plastik
Theme: Breeze (Dark) [Qt], cachyos-nord [GTK2/3/4]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (24px)
Terminal: konsole 25.4.1
CPU: AMD Ryzen 5 5600H (12) @ 4.28 GHz
GPU 1: NVIDIA GeForce RTX 3050 Ti Mobile [Discrete]
GPU 2: AMD Radeon Vega Series / Radeon Vega Mobile Series [Integrated]
Memory: 3.64 GiB / 13.50 GiB (27%)
Swap: 0 B / 4.00 GiB (0%)
Disk (/): 7.90 GiB / 418.29 GiB (2%) - zfs
Disk (/run/keystore/rpool): 28.00 KiB / 3.73 MiB (1%) - ext4
Disk (/tank): 509.32 GiB / 693.26 GiB (73%) - zfs
Battery (L20C4PC0): 75% [AC Connected]
Locale: en_US.UTF-8
lsblk -o NAME,FSTYPE,TYPE,MOUNTPOINT | grep crypt
│ └─dm_crypt-0 swap crypt [SWAP]
zd0 crypto_LUKS disk
└─keystore-rpool ext4 crypt /run/keystore/rpool
That was a 3 hour ordeal! And I still have to clean this up a bit.
lsblk -o NAME,FSTYPE,TYPE,MOUNTPOINT
NAME FSTYPE TYPE MOUNTPOINT
sda disk
├─sda1 linux_raid_member part
├─sda2 linux_raid_member part
├─sda3 ext4 part
└─sda4 ext4 part
sdb disk
└─sdb1 zfs_member part
sdc disk
├─sdc1 vfat part /boot/efi
├─sdc2 zfs_member part
├─sdc3 part
│ └─dm_crypt-0 swap crypt [SWAP]
└─sdc4 zfs_member part
sdd disk
├─sdd1 exfat part
└─sdd2 vfat part
sde disk
sdf disk
zd0 crypto_LUKS disk
└─keystore-rpool ext4 crypt /run/keystore/rpool
nvme0n1 disk
├─nvme0n1p1 vfat part
└─nvme0n1p2 zfs_member part
nvme1n1 disk
├─nvme1n1p1 vfat part
└─nvme1n1p2 btrfs part
Qousting 5/13 extended install Fail. Curtin install fail. Reported to Launchpad.
Problem reporting issue about ubuntu-desktop-bootstrap:
When install fails i see a window saying: “something went wrong” and suggesting to report the issue. I click on “report the issue” and see a message “the collected information is sent to tracking system” but no bug number.
If I open a terminal and enter “ubuntu-bug ubuntu-desktop-bootstrap” i have a similar result but no bug number.
Is it possible to fix this behavior so that we have a bug to follow on lauchpad? who/how should I ask for the change? Thank you.
the proof that the mechanism doesn’t work is on the page
where most bugs are ‘incomplete’
They’re incomplete because they’re awaiting logs and information, which can be obtained when attempting the install again.
Bug reporting isn’t about “This happened, fix it.” It’s about helping in the fix process. If you’re willing to report a bug, you should be willing to help fix it with the required information.