chpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> please reopen if this is still an issue
>
> ** Changed in: systemd (Ubuntu)
> Status: Confirmed =>
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
Tried the most recent proposed kernel, 5.2.0-8 today, still gets stuck at the
target reboot reached.
Not a huge deal at this point as the magic-sys-request is working so I can at
least force the reboot from the keyboard at that point.
--
You received this bug notification because you are a
om
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> Does the system have boot loader other than GRUB installed?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
y-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> Does the system have boot loader other than GRUB installed?
>
> --
> You rec
y-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> Does the system have boot loader other than GRUB installed?
>
> --
> You rec
Does the system have boot loader other than GRUB installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl reboot system reaches Target Reboot but then
does
: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 23 Apr 2019, Kai-Heng Feng wrote:
> Date: Tue, 23 Apr 2019 05:12:05 -
> From: Kai-Heng Feng
> Reply-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I
Prebuilt binaries can be found here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl reboot system reaches Target
, Kai-Heng Feng wrote:
> Date: Mon, 22 Apr 2019 02:50:57 -
> From: Kai-Heng Feng
> Reply-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot
If this doesn't happen to v4.15, please run a kernel bisection to find
the regression commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl reboot system
:
> Date: Thu, 18 Apr 2019 09:38:13 -
> From: Kai-Heng Feng
> Reply-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> It c
It can be a kernel bug. Do you see this issue if the system boots under
kernel v4.18?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl reboot system reaches Target
Yes, I've deleted the failing packages, game servers, debomatic, etc,
or in one case masked it so systemd should not try to run it.
On Tue, April 16, 2019 11:27 pm, Sebastien Bacher wrote:
> see
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachmen
>
see
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256102/+files/SystemdFailedUnits.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type
://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 16 Apr 2019, Sebastien Bacher wrote:
> Date: Tue, 16 Apr 2019 14:23:23 -
> From: Sebastien Bacher
> Reply-To: Bug 1824893 <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I
Thanks, I don't see anything obvious in the log, setting as New again
for now (would be good to see if removing the faulty units pointed in
the previous comment makes a difference though)
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
** Attachment added: "Last 250 lines of journalctl log for shutdown"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256268/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
>
> Thank you for your bug report. Could you attach your journalctl log from
> that shutdown to the bug?
>
> The log on
> https://launchpadlibr
Thank you for your bug report. Could you attach your journalctl log from
that shutdown to the bug?
The log on
https://launchpadlibrarian.net/419441276/SystemdFailedUnits.txt also
shows that some systemd unit are failing on your system, maybe one of
those is creating the issue...
(also when it's
21 matches
Mail list logo
