Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 648644 - sys-apps/systemd-9999 - systemd dumps core when I try to boot, in spite of the fixes I have below
Summary: sys-apps/systemd-9999 - systemd dumps core when I try to boot, in spite of th...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo systemd Team
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2018-02-24 00:31 UTC by cyrillic
Modified: 2018-03-11 20:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
triplequote.patch (triplequote.patch,670 bytes, patch)
2018-02-24 00:34 UTC, cyrillic
Details | Diff
systemd.patch (systemd.patch,578 bytes, patch)
2018-02-24 00:37 UTC, cyrillic
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description cyrillic 2018-02-24 00:31:23 UTC
sys-apps/systemd-9999 is currently broken

Reproducible: Always




Current systemd dumps core when I try to boot, in spite of the fixes I have below.
Comment 1 cyrillic 2018-02-24 00:34:01 UTC
Created attachment 520812 [details, diff]
triplequote.patch

This fixes a compile failure.
Comment 2 cyrillic 2018-02-24 00:37:20 UTC
Created attachment 520814 [details, diff]
systemd.patch

This fixes a warning from the ebuild.
Comment 3 cyrillic 2018-02-24 23:44:30 UTC
The fix from Comment 2 "s/path-kill/kill-path/" applies to systemd-237-r2.ebuild and systemd-236-r5.ebuild in addition to the -9999.ebuild

This does not have any effect on the booting issue I observed.
Comment 4 cyrillic 2018-02-25 00:11:24 UTC
For some reason, the compile failure I had in Comment 1 no longer happens, even though the file I am patching has not been altered by upstream in at least 3 months ... something fishy is going on here :-/
Comment 5 Larry the Git Cow gentoo-dev 2018-02-26 16:07:52 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf8cfc16eb832ce67174d822e51d4f9e37f371ff

commit cf8cfc16eb832ce67174d822e51d4f9e37f371ff
Author:     Mike Gilbert <floppym@gentoo.org>
AuthorDate: 2018-02-26 16:07:00 +0000
Commit:     Mike Gilbert <floppym@gentoo.org>
CommitDate: 2018-02-26 16:07:49 +0000

    sys-apps/systemd: fix kill-path option
    
    Bug: https://bugs.gentoo.org/648644
    Package-Manager: Portage-2.3.24_p18, Repoman-2.3.6_p99

 sys-apps/systemd/systemd-236-r5.ebuild | 2 +-
 sys-apps/systemd/systemd-237-r2.ebuild | 2 +-
 sys-apps/systemd/systemd-9999.ebuild   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)}
Comment 6 Mike Gilbert gentoo-dev 2018-02-26 16:10:42 UTC
There's not enough information in this report to do anything useful.
Comment 7 cyrillic 2018-02-28 00:43:12 UTC
Current systemd continues to not boot for me.
This is the message I get (copied by hand) :

systemd[1]: systemd 237 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP -LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
systemd[1]: Detected architecture x86-64.
systemd[1]: Caught <ABRT>, dumped core as pid 202.
systemd[1]: Freezing execution.

Systemd from 8 days ago boots fine.
I was hoping upstream would just fix it on their own.
I will try to bisect this if I have the time.
Comment 8 cyrillic 2018-03-11 20:07:12 UTC
I am not sure what upstream fixed, but systemd-238 and systemd-9999 are now booting correctly, so my original problem is no longer a problem.