[Bug 1175850] MicroOS Desktop can't reboot?
https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c7 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |kubic-bugs@opensuse.org Component|MicroOS |Basesystem Assignee|kubic-bugs@opensuse.org |screening-team-bugs@suse.de Flags|needinfo?(mike@flingtoad.co | |m) | Severity|Major |Normal --- Comment #7 from Fabian Vogt <fvogt@suse.com> --- The last few lines are: Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: About to execute: /usr/bin/journalctl --smart-relinquish-var Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: Forked /usr/bin/journalctl as 2027 Nov 13 12:29:00 AP17L systemd[1]: systemd-journal-flush.service: Changed exited -> stop Nov 13 12:29:00 AP17L systemd[1]: Stopping Flush Journal to Persistent Storage... Nov 13 12:29:00 AP17L systemd[2027]: systemd-journal-flush.service: Executing: /usr/bin/journalctl --smart-relinquish-var Nov 13 12:29:00 AP17L systemd[1]: systemd-journald.service: Got notification message from PID 674 (FDSTORE=1) Nov 13 12:29:00 AP17L systemd[1]: systemd-journald.service: Added fd 21 (n/a) to fd store. So it seems like systemd-journald.service doesn't reach stopped for some reason. Reassigning to systemd, to provide some ideas. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com