Unfortunately the stack trace isn't particularly useful. If you can
reproduce this, it would be helpful if you could install systemd-dbg and
look at the generated stack trace then?
This crashes in:
bool logind_wall_tty_filter(const char *tty, void *userdata) {
Manager *m = userdata;
assert(m);
if (!startswith(tty, "/dev/"))
return true;
return !streq(tty + 5, m->scheduled_shutdown_tty);
}
startswith() does a strlen() and a strncmp(), so I don't think it's that
as it would already segfault in strlen(). m is also not NULL (due to the
assert), so I figure it's the m->scheduled_shutdown_tty that is NULL.
I'll dig through the code to see where this is being set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553040
Title:
systemd-logind crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1553040/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
