Comment # 23 on bug 918158 from Ivan Topolsky

Created attachment 625769 [details]
systemd core dump (xz-compressed)

crash on systemd (210-25.15.2)

this time, I managed to manuually trigger it:

I noticed I still had consolekit lying around. While stoping it, systemd
crashed. 
(Some conflicts with the systemd-logind service that is supposed to handle the
same tasks and was running normally at the time ?)

Anyway, I'm going to remove the useless service.

I just find it strange that systemd segfaults, even given bogus input from
wrong services. I would expect it to at least to some sanity checks on its
input and handle corrupted input gracefully (error message, eventually restart.
no crash)


> Hm, the stack seems corrupted:

That's strange, I've always been able to run the backtrace to the end.

I don't have the debug symbols installed. So I have less information, but my
stack doesn't seem corrupted. Just travelling several symbols which are not
publicly exported and named.

Here's the current one:

> #0  0x00007f4d9333575b in raise () from /lib64/libpthread.so.0
> #1  0x000000000040d047 in ?? ()
> #2  <signal handler called>
> #3  0x000000000049c050 in ?? ()
> #4  0x000000000049c5e0 in ?? ()
> #5  0x000000000040f5d8 in ?? ()
> #6  0x0000000000413367 in ?? ()
> #7  0x000000000040bea6 in ?? ()
> #8  0x00007f4d92fa0b05 in __libc_start_main () from /lib64/libc.so.6
> #9  0x000000000040c5cc in ?? ()

I'm pretty sure that I'm running the stock version of most libraries.


I'll be looking if there are more unnecessary services laying around.
And if removing them makes the problems go away.

Strange that ConsoleKit didn't get removed during the past updates.