[Bug 1175850] New: MicroOS Desktop can't reboot?
From what I can tell, 4-6 only happen when running the X session for KDE. If you run the Wayland session, 4-6 work but the others still don't. I haven't
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Bug ID: 1175850 Summary: MicroOS Desktop can't reboot? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: mike@flingtoad.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- On a default install of MicroOS Desktop (KDE) (ALPHA) 20200824-0, there is no obvious way to reboot the machine after install packaged with transactional-update. Here's what I've tried. 1. 'transactional-update reboot' (notifies rebootmgrctl that a reboot is requested, but 'rebootmgrctl status' seems to be waiting for the scheduled maintenance time. 2. 'rebootmgrctl reboot now' does not seem to do anything. 3. 'rebootmgrctl reboot fast' does not seem to do anything. 4. Click "Leave" -> "Restart" from KDE menu does not seem to do anything. 5. Click "Leave" -> "Shutdown" from KDE menu does not seem to do anything. 6. Click "Leave" -> "Shutdown" from KDE menu does not seem to do anything. 7. 'systemctl reboot' drops to a non-graphical target with login prompt, but doesn't continue with a reboot. 8. 'shutdown -r now' drops to a non-graphical target with login prompt, but doesn't continue with a reboot. 9. 'shutdown -h now' complains about not being able to unmount /etc, but eventually does halt. 10. 'systemctl reboot' to drop to term and the ctrl-alt-delete several times does eventually reboot tried Wayland (Full). Other notes and observations: 1. I don't think the X session is starting the org.kde.ksmserver, but it does get started for Wayland. 2. I'm using full-disk encryption. 3. No matter how I exit the KDE session, it never saved my display configuration. I have to reconfigure the displays each time. Perhaps another bug report for this one. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c1 --- Comment #1 from Mike Oliver <mike@flingtoad.com> --- I removed 'quiet' from the kernel boot parameters and can now see that the reboot is actually hanging on "A stop job is running for Cryptography Setup for cr_var (xmin x2, no limit). So I believe the reboot methods were triggering a reboot, but it was just hanging at this point, but since it was 'quiet' it just looks like a normal non-graphical login prompt. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c4 --- Comment #4 from Mike Oliver <mike@flingtoad.com> --- I was unable to reproduce this issue in a VM. It reboots just fine. I still need to get a chance to try it on my physical hardware again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c5 Arek P. <ahhhrrreeecccek2710@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahhhrrreeecccek2710@gmail.c | |om --- Comment #5 from Arek P. <ahhhrrreeecccek2710@gmail.com> --- Created attachment 843582 --> http://bugzilla.opensuse.org/attachment.cgi?id=843582&action=edit Logs -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c6 --- Comment #6 from Arek P. <ahhhrrreeecccek2710@gmail.com> --- I have the same issue... https://forums.opensuse.org/showthread.php/547237-MicroOS-Tumbleweed-Transac... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Arek P. <ahhhrrreeecccek2710@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Arek P. <ahhhrrreeecccek2710@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c8 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #8 from Andrei Borzenkov <arvidjaar@gmail.com> --- (In reply to Fabian Vogt from comment #7)
So it seems like systemd-journald.service doesn't reach stopped for some reason.
We do not really know it if journald stopped writing into /var. To capture what happens after that serial or net console is needed together with systemd.log_target=console. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c9 --- Comment #9 from Andrei Borzenkov <arvidjaar@gmail.com> --- Created attachment 843606 --> http://bugzilla.opensuse.org/attachment.cgi?id=843606&action=edit Hung systemd-cryptsetup stack strace (In reply to Fabian Vogt from comment #7)
So it seems like systemd-journald.service doesn't reach stopped for some reason.
nope. I can reproduce it using TW in QEMU installed with transnational desktop and separate /var partition. For some reasons it happens only with Plymouth disabled. I checked that systemd-journald correctly relinquishes /var and /var is unmounted. But systemd-cryptsetup hangs. I attach full log from systemd debug shell; most interesting part is stack trace. (gdb) bt #0 __semtimedop (semid=4, sops=sops@entry=0x7ffe1a874a62, nsops=nsops@entry=1, timeout=timeout@entry=0x0) at ../sysdeps/unix/sysv/linux/semtimedop.c:33 #1 0x00007fd0ebf2da4b in semop (semid=<optimized out>, sops=sops@entry=0x7ffe1a874a62, nsops=nsops@entry=1) at ../sysdeps/unix/sysv/linux/semop.c:29 #2 0x00007fd0ebac4bbd in _udev_wait (cookie=223200190, nowait=nowait@entry=0x7ffe1a874a94) at libdm-common.c:2768 #3 0x00007fd0ebac4cf8 in dm_udev_wait (cookie=<optimized out>) at libdm-common.c:2787 #4 0x00007fd0ec04afe7 in _dm_remove.constprop.0 (name=name@entry=0x7ffe1a875efe "cr_var", deferred=deferred@entry=0, udev_wait=1) at lib/libdevmapper.c:1022 #5 0x00007fd0ec0217da in dm_remove_device (cd=0x557d701ae950, name=0x7ffe1a875efe "cr_var", flags=<optimized out>) at lib/libdevmapper.c:1155 #6 0x00007fd0ec009dce in crypt_deactivate_by_name (cd=0x557d701ae950, name=0x7ffe1a875efe "cr_var", flags=0) at lib/setup.c:4510 #7 0x0000557d6fa9f286 in run (argc=3, argv=0x7ffe1a875258) at ../src/cryptsetup/cryptsetup.c:1037 #8 0x0000557d6fa9d656 in main (argc=<optimized out>, argv=<optimized out>) at ../src/cryptsetup/cryptsetup.c:1047 This appears to be fundamental problem with any device-mapper command that survives udevd. Quick glance at cryptsetup does not offer any possibility to disable udev integration for specific invocation - it is hard-coded. But that is just one of possible consumers of device-mapper, so is the wrong place to fix it in any way. I do not claim to understand what device-mapper does or waits for. Cc lvm2 maintainers ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |deanraccoon@gmail.com, | |ghe@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 http://bugzilla.opensuse.org/show_bug.cgi?id=1175850#c10 --- Comment #10 from Andrei Borzenkov <arvidjaar@gmail.com> --- Workaround is mkdir -p /etc/systemd/system/systemd-cryptsetup@.service.d cat > /etc/systemd/system/systemd-cryptsetup@.service.d/stop-before-udevd.conf << EOF [Unit] After=systemd-udevd.service EOF systemctl daemon-reload But seriously, this is just wack-a-mole. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Seiji Hiwatari <info@ebner-markus.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |info@ebner-markus.de -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com