Bug 1089596

(gdb) 
Thread 1 (Thread 0x7fd7b9ccb880 (LWP 7016)):
#0  0x00007fd7b864d979 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x00007fd7b864f088 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x00007fd7b9cf2dc3 in log_assert (text=<optimized out>, file=0x7fd7b9d01596 "src/login/logind-session.c", line=515, func=0x7fd7b9d01f60 <__PRETTY_FUNCTION__.9895> "session_start_scope", 
    format=format@entry=0x7fd7b9d06338 "Assertion '%s' failed at %s:%u, function %s(). Aborting.") at src/shared/log.c:716
        buffer = "Assertion 's->user->slice' failed at src/login/logind-session.c:515, function session_start_scope(). Aborting.", '\000' <repeats 1937 times>
#3  0x00007fd7b9cf3390 in log_assert_failed (text=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>) at src/shared/log.c:721
No locals.
#4  0x00007fd7b9ce5882 in session_start_scope (s=0x7fd7b9f85250) at src/login/logind-session.c:515
        error = {name = 0x7fd7b9f85250 "0\300\367\271\327\177", message = 0x0, dummy1 = 0, dummy2 = 0, dummy3 = 0, dummy4 = 0, dummy5 = 0, padding1 = 0x7fd7b869844c <malloc+92>}
        r = <optimized out>
#5  session_start (s=s@entry=0x7fd7b9f85250) at src/login/logind-session.c:569
        r = <optimized out>
        __PRETTY_FUNCTION__ = "session_start"
        __func__ = "session_start"
#6  0x00007fd7b9cde43e in bus_manager_create_session (message=0x7fd7b9f821d0, m=<optimized out>) at src/login/logind-dbus.c:643
        remote_host = 0x7fd7b9f83e14 "dhcp-11-50.nay.redhat.com"
        iter = {dummy1 = 0x7fd7b9f821d0, dummy2 = 0x7fd700600000, dummy3 = 3120044652, dummy4 = 32727, dummy5 = -1174920744, dummy6 = 32727, dummy7 = 160, dummy8 = 32727, dummy9 = -1174920672, 
          dummy10 = 32727, dummy11 = 77, pad1 = 0, pad2 = -1186476800, pad3 = 0x7fd7b947d8f8}
        vtnr = 0
        display = 0x7fd7b9f83e00 ""
        remote_user = 0x7fd7b9f83e0c ""
        uid = 0
        audit_id = 5
        id = 0x7fd7b9f83640 "5"
        user = 0x7fd7b9f84420
        seat = 0x0
        b = <optimized out>
        r = 0
        tty = 0x7fd7b9f83df8 ""
        service = 0x7fd7b9f83dcc "sshd"
        c = SESSION_USER
        class = 0x7fd7b9f83de0 "user"
        cseat = 0x7fd7b9f83dec ""
        session = 0x7fd7b9f85250
        t = SESSION_TTY
        type = 0x7fd7b9f83dd8 "tty"
        remote = 1
        leader = 8422
#7  manager_message_handler (connection=0x7fd7b9f7ec30, message=0x7fd7b9f821d0, userdata=<optimized out>) at src/login/logind-dbus.c:1725
---Type <return> to continue, or q <return> to quit---        m = <optimized out>
        error = {name = 0x0, message = 0x0, dummy1 = 1, dummy2 = 0, dummy3 = 0, dummy4 = 1, dummy5 = 1, padding1 = 0x7fd7b9f7ee10}
        reply = 0x0
        r = <optimized out>
        __PRETTY_FUNCTION__ = "manager_message_handler"
#8  0x00007fd7b9254e66 in _dbus_object_tree_dispatch_and_unlock () from /lib64/libdbus-1.so.3
No symbol table info available.
#9  0x00007fd7b9247a31 in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
No symbol table info available.
#10 0x00007fd7b9cd9ef7 in manager_run (m=m@entry=0x7fd7b9f7c030) at src/login/logind.c:1172
        event = {events = 4294967295, data = {ptr = 0xffffffff, fd = -1, u32 = 4294967295, u64 = 4294967295}}
        n = <optimized out>
        msec = -1
        __PRETTY_FUNCTION__ = "manager_run"
        __func__ = "manager_run"
#11 0x00007fd7b9cd765a in main (argc=<optimized out>, argv=<optimized out>) at src/login/logind.c:1307
        m = 0x7fd7b9f7c030
        r = 0
        __func__ = "main"
(gdb) quit
[root@localhost ccpp-2014-04-18-01:02:40-7016]#

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

systemd received SIGABRT because it tried to create session for user which doesn't have slice created. This is weird. I've ever seen this crash before nor there is a record about it on abrtd retrace server.

Can you explain in more detail what are the circumstances when crash happens. Did you change pam configuration in any way?

(In reply to Michal Sekletar from comment #4)
> systemd received SIGABRT because it tried to create session for user which
> doesn't have slice created. This is weird. I've ever seen this crash before
> nor there is a record about it on abrtd retrace server.
> 
> Can you explain in more detail what are the circumstances when crash
> happens. Did you change pam configuration in any way?

I didn't touched pam at all,

what I tried before reboot is to make gdm auto logon:

cat /etc/gdm/custom.conf
# GDM configuration storage

[daemon]
AutomaticLoginEnable=True
AutomaticLogin=root
TimedLoginEnable=true
TimedLogin=root
TimedLoginDelay=10

[security]

[xdmcp]

[greeter]

[chooser]

[debug]

nothing else except above cfg changing.

*** This bug has been marked as a duplicate of bug 1205062 ***