[Bug 1222909] New: Feedback to prototype image openSUSE-Aeon.x86_64.raw.xz
https://bugzilla.suse.com/show_bug.cgi?id=1222909 Bug ID: 1222909 Summary: Feedback to prototype image openSUSE-Aeon.x86_64.raw.xz Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown@suse.com Reporter: happymab.dev@outlook.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:124.0) Gecko/20100101 Firefox/124.0 Build Identifier: Feedback openSUSE Aeon prototype Installation - Download image from https://download.opensuse.org/repositories/devel:/microos:/aeon:/installer/a... - $> xz -d openSUSE-Aeon.x86_64.raw.xz - $> qemu-img convert openSUSE-Aeon.x86_64.raw -O qcow2 openSUSE-Aeon.x86_64.qcow2 - $> qemu-img resize openSUSE-Aeon.x86_64.qcow2 +20G - Open Gnome Boxes and add a new VM using 'Install from file', 6 GB RAM - Run the VM Observations - On the first boot the system got stuck at a dark gray screen (graphical, mouse pointer is there and can be moved) - Restart after 10 min - System boots into configuration (language, keyboard, etc) - Aeon Firstboot runs without problems (installs Firefox, Calculator, etc) Impressions - Partitioning: - 2MB BIOS boot - required? - 4.2GB /boot/efi - quite large - Podman and distrobox are not installed - Personally I would prefer to have the following packages installed: zsh nano (and starship, but that's probably too specific) - No Grub: how can one boot a previous snapshot in case something breaks, e.g. caused by an update? - Automatic rollback does not always work in my experience... Log entries that stud out Apr 16 21:50:46 localhost.localdomain systemd[2015]: app-gnome-xdg\x2duser\x2ddirs-2186.scope: PID 2186 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-xdg\x2duser\x2dd> Apr 16 21:50:46 localhost.localdomain systemd[2015]: app-gnome-xdg\x2duser\x2ddirs-2186.scope: No PIDs left to attach to the scope's control group, refusing. Apr 16 21:50:46 localhost.localdomain systemd[2015]: app-gnome-xdg\x2duser\x2ddirs-2186.scope: Failed with result 'resources'. Apr 16 21:50:46 localhost.localdomain systemd[2015]: Failed to start Application launched by gnome-session-binary. Reproducible: Always Steps to Reproduce: - Download image from https://download.opensuse.org/repositories/devel:/microos:/aeon:/installer/a... - $> xz -d openSUSE-Aeon.x86_64.raw.xz - $> qemu-img convert openSUSE-Aeon.x86_64.raw -O qcow2 openSUSE-Aeon.x86_64.qcow2 - $> qemu-img resize openSUSE-Aeon.x86_64.qcow2 +20G - Open Gnome Boxes and add a new VM using 'Install from file', 6 GB RAM - Run the VM Actual Results: - On the first boot the system got stuck at a dark gray screen (graphical, mouse pointer is there and can be moved) - Restart after 10 min - System boots into configuration (language, keyboard, etc) - Aeon Firstboot runs without problems (installs Firefox, Calculator, etc) Expected Results: The system should boot into the configuration dialog on the first boot Installation in Gnome Box that is installed as a flatpak. Host system is a Dell laptop running openSUSE Aeon. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222909 https://bugzilla.suse.com/show_bug.cgi?id=1222909#c1 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #1 from Richard Brown <rbrown@suse.com> --- Feedback to your AWESOME feedback First boot hanging was probably the result of trying to resize the Rootfile system to be larger than 40GB when your test system had less..that's fine, tik will stop that in the future. Please retest with 40GB :) - The GPT 2MB partition is required, yes - The 4GB EFI partition is large by design - every kernel/initrd for every snapshot needs to fit in there. - Podman and distrobox will be installed in images now - No grub is intentional, it's a systemd-boot image. The boot menu should appear if pressing a button (space works nicely for me). I may make the boot menu appear all teh time, but that's a guaranteed boot slowdown I want to avoid Those log entries are weird..I'll try to recreate :) Please feel free to retest https://download.opensuse.org/repositories/devel:/microos:/aeon:/installer/a... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222909 https://bugzilla.suse.com/show_bug.cgi?id=1222909#c2 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Richard Brown <rbrown@suse.com> --- All issues expected to be addressed in RC2 images -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com