Not an issue, found that I was using the wrong GPU driver for my hardware,
when I fixed that it fixed the shutdown issue as well as some graphics issues.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts,
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
I could not find what was going wrong with update-grub2, it showed it
doing the right thing but did not alter the boot screen. I purged grub and
all it's configuration from my workstation then re-installed, now it is
working again.
I installed 4.15.18 and systemctl reboot is not getting
Actually there was petiboot which I never did get successfully working.
Wanted to be able to kexec-boot because the BIOS in this old Mac is so very
painfully slow.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell
Grub and Grub2 are installed, no others, not lilo, etc. I do not know
WHERE it is finding 5.0.9 at, no remnants in the boot, modules, initramfs
directories.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell
Does the system have boot loader other than GRUB installed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl reboot system reaches
Well I've managed to screw up my machine massively and don't know how
to get it back to a sane state.
I deleted what I thought were all traces of 5.0.9 that I had
compiled and re-ran update-grub2, then I installed:
rw-r--r-- 1 nanook rmtonly 10877978 Apr 22 23:20
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl
I'm going to need a bit of help with respect to where to find old
canonical kernel packages so I can find at what point it broke exactly.
I did compile 5.0.9 from kernel.org source and it does reboot properly
so I do know for certain that it is a kernel issue.
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type
Yes. It has been an issue for a while. It was a problem with 16.04,
16.10, fixed in 17.04, 17.10, 18.04, broken again in 18.10 and 19.04. Since
I installed the development release I thought I'd try to get to the bottom
of it this time around.
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Title:
When I type systemctl
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1824893
Sorry, which faulty units are those?
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site:
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
I've added the last 250 lines of the log, if that's not enough let me
know. Once it says it's reached target reboot the next thing it does is
send a kill signal to all processes, including journalctl so there is not
much useful information beyond that point. Also I can not switch virtual
** 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
Touch seeded packages, which is subscribed to
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
