the issue there doesn't have anything to do with the desktop login
screen though and there seems to be no real/concrete bug, best to use
discourse for discussions and suggestions, closing this ticket
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Low
** Changed in: gdm3 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1843652
Title:
The bootmenu for zfs based Ubuntu does partly not work
Status in gdm3 package in Ubuntu:
Invalid
Bug description:
I had a triple boot since April:
- Ubuntu 19.04 on ext4
- Ubuntu Mate 19.04 on zfs
- Xubuntu 19.04 on zfs
Each zfs based system is stored completely in its own dataset, all folders
are in that dataset; var; usr; home and all others.
I have upgraded all systems to 19.10 and it went reasonably well, but I
produced a few bug reports for some minor errors or typical transition
problems. I did reinstall Ubuntu 19.10 on ext4 to solve one of those transition
issues.
All systems work fine now and I can boot all from Linux 5.2.
Since the Software-Updater does not work anymore, I had to do the updates
using apt in the terminal, but I created two snapshots for both zfs systems one
190908 and one 190911.
After running update-grub and grub-install those snapshots appear in the boot
menu, hurrah!
However except the main Linux 5.2 one for each OS, none of the menu entries
is working:
- The memory test ends up with a blank screen and nothing seems to happen.
That entry has been added by the main zfs based system;
- The history entries tell me "wrong dnode type" and "the correct kernel must
be loaded first" and then it returns to the boot menu;
- The advanced entries
Both Linux 5.2 and 5.0 recovery modes stop after loading the RAM disk. The
system hangs, but the disk light blinks each 5 seconds.
Linux 5.0 normal mode says: it will not load due an incompatibility with the
datapool. That happens because I decided to upgrade the datapool itself.
In the release notes you need a strong warning about the consequences of
updating the datapool!! Also during upgrading dual or multi boot systems. I did
run into problems with it; even when I initially only updated the pool with the
data and left the pool with systems and VMs unchanged.
The last pool (systems and VMs) has been updated, when I completed the
upgrade of the systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1843652/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
