[Bug 1233149] New: System got stuck in "setting up" screen on first boot
https://bugzilla.suse.com/show_bug.cgi?id=1233149 Bug ID: 1233149 Summary: System got stuck in "setting up" screen on first boot Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown@suse.com Reporter: lzcoder@proton.me QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878470 --> https://bugzilla.suse.com/attachment.cgi?id=878470&action=edit journalctl -p crit After installing the system with 20241106 image, it got stuck at the “setting up” screen on first boot. In my case I waited more than 30 minutes (in previous installations I didn't have to wait that long) and after waiting I restarted my system and everything seems to work correctly. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c1 Dutovas <suse.disk414@passmail.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse.disk414@passmail.net --- Comment #1 from Dutovas <suse.disk414@passmail.net> --- I have the same issues, and it rendered my PC useless. I was stuck "Please wait.. setting up your computer.. this may take a few minutes" for over an hour, then I decided to try and restart my PC, after which my installation would just get to the black screen and stay like that indefinitely, so I can't really use my PC. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c2 Balazs <kisskovacsattila@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kisskovacsattila@gmail.com --- Comment #2 from Balazs <kisskovacsattila@gmail.com> --- Same here. Look at this: https://www.reddit.com/r/AeonDesktop/comments/1gms3sf/aeon_desktop_rc3_stuck... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c3 Joe Braddock <jmbraddock@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmbraddock@gmail.com --- Comment #3 from Joe Braddock <jmbraddock@gmail.com> --- I experienced this on a Dell Inspiron laptop. Like Luan Adao, I waited, actually overnight, but upon restarting, it still didn't work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c4 --- Comment #4 from Balazs <kisskovacsattila@gmail.com> --- I found a temporary solution: 1. boot with "autorelabel=1" kernel parameter 2. reboot, boot with "systemd-unit=emergency.target init=/bin/sh" 3. change root password 4. reboot Now it works, but I have low resolution (1024x768) on my FHD monitor :D -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c5 Enrico Badalamento <rodeo_duft.0v@icloud.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodeo_duft.0v@icloud.com --- Comment #5 from Enrico Badalamento <rodeo_duft.0v@icloud.com> --- Hi, same issue by me. ThinkPad X13 g3 AMD. After clean install RC3 (format ssd) system stays stuck on first boot. About a month ago I installed RC3, two weeks later came Lenovo Firmware Update, then after every reboot I had to enter Recovery Key (sdbootutil --ask-pin update-predictions didnt help). So I decided yesterday to reinstall, but can´t boot becase of this issue. Please wait.. setting up your computer.. this may take a few minutes 12.094660] dracut-pre-pivot[1223]: /sbin/setfiles: conflicting specifications for /etc/dbus-1/session.conf and /etc, using system_u :object_r:etc_t:s0. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c6 --- Comment #6 from Enrico Badalamento <rodeo_duft.0v@icloud.com> --- ThinkPad X13 G3 --> I did UEFI Bios reset do factory defaults, nothing has changed, after clean install it still stuck on first boot ... Brand new ThinkPad X13 G4 AMD, Aeon is the first OS on it, downloaded RC3 from 24.11. but same Issue, it stucks on first boot, with exact the same message ... Please wait ... dracut-pre-pivot ... If I install with the same USB-Stick Asus Expertbook B5 Intel 13th., there is no problem, the installation goes smoothly. Even if I reinstall the Asus several times in a row (clean install-format ssd), there is no error, everything runs perfectly. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c7 Christian Gast <cookehlicious@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cookehlicious@gmail.com --- Comment #7 from Christian Gast <cookehlicious@gmail.com> --- Same problem on my HP Elite X2 1012 G2, I had Aeon installed on that before without issues. Also same problem on my main PC (Gigabyte Mainboard, AMD CPU and GPU). The PC had Tumbleweed installed before, I just wanted to switch to Aeon since I like it so much on my Notebook. My HP Elitebook 855 G7 currently runs Aeon without any problems. I tried to install to the other machines with the same usb drive I used for the Elitebook but it didn't work. Tried another usb driver, same error. I really hope this can be fixed since Aeon is so rock solid and smooth. Cheers and thanks for all your hard work! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 Martin Torres <emtorres@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emtorres@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c8 Ilya Stolyarov <ila.embsys@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ila.embsys@gmail.com --- Comment #8 from Ilya Stolyarov <ila.embsys@gmail.com> --- I have tried to install Aeon Desktop and got stuck on the same issue. The system shows "please wait" message indefinitely. After taking some time to recognise the issue I concluded that this message probably shows when the system doesn't have an internet connection. My guessing is based on a log information where shown that some health-checker service failed to check some conditions "Health check failed!" and then after the message "Machine didn't come up correctly, stopping services" probably everything even display manager are going to stop. And the failed condition is rmpdb checking: "ERROR: "/usr/libexec/health-checker/rpmdb-consistency.sh check" failed". And the reason of that is "Error message: Could not resolve host: download.opensuse.org" that is fully expected if no internet connection established. To prove that guessing I set the additional kernel parameter like "systemd-unit=emergency init=/bin/bash" then booted to shell and disabled booting of healthcheck service by "systemctl disable health-checker.service". After that and rebooting, the installation window is showed on the screen. So I could open Wi-Fi menu and connect to a network. Then I rebooted back to shell and enabled health-checker.service back. After that system starts to boot up to the installation window as should probably because the connection settings is remembered now. systemd[1]: Starting MicroOS Health Checker... health-checker[1939]: Clearing GRUB flag health-checker[1941]: /usr/sbin/health-checker: line 144: grub2-editenv: command not found health-checker[1939]: Starting health check health-checker[2007]: active health-checker[2016]: Error building the cache: health-checker[2016]: [repo-oss|http://download.opensuse.org/tumbleweed/repo/oss/] Failed to retrieve new repository met> health-checker[2016]: History: health-checker[2016]: - [|] Error trying to read from 'http://download.opensuse.org/tumbleweed/repo/oss/' health-checker[2016]: - Download (curl) error for 'http://download.opensuse.org/tumbleweed/repo/oss/content': health-checker[2016]: Error code: Connection failed health-checker[2016]: Error message: Could not resolve host: download.opensuse.org health-checker[2016]: Warning: Skipping repository 'openSUSE-Tumbleweed-Oss' because of the above error. health-checker[2016]: Some of the repositories have not been refreshed because of an error. health-checker[2166]: root: ERROR: "/usr/libexec/health-checker/rpmdb-consistency.sh check" failed health-checker[1939]: Health check failed! root[2171]: Machine didn't come up correctly, stopping services health-checker[2171]: root: Machine didn't come up correctly, stopping services systemctl[2174]: Failed to stop crio.service: Unit crio.service not loaded. systemctl[2177]: Job for systemd-logind.service canceled. systemctl[2212]: Failed to stop rebootmgr.service: Unit rebootmgr.service not loaded. health-checker[2213]: Usage: /usr/libexec/health-checker/rpmdb-consistency.sh {check|stop} systemd[1]: health-checker.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: health-checker.service: Failed with result 'exit-code'. systemd[1]: Failed to start MicroOS Health Checker. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1233149 https://bugzilla.suse.com/show_bug.cgi?id=1233149#c9 --- Comment #9 from Luan Adão <lzcoder@proton.me> --- This bug has been resolved for me with the latest images -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com