RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
don't know
I locked screen then after +-12hours I unlock screen and it happens

Version-Release number of selected component:
systemd-208-20.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/lib/systemd/systemd-logind
crash_function: log_assert
executable:     /usr/lib/systemd/systemd-logind
kernel:         3.10.0-229.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 log_assert at src/shared/log.c:716
 #3 log_assert_failed at src/shared/log.c:721
 #4 session_start_scope at src/login/logind-session.c:515
 #5 session_start at src/login/logind-session.c:569
 #6 bus_manager_create_session at src/login/logind-dbus.c:643
 #7 manager_message_handler at src/login/logind-dbus.c:1725
 #8 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
 #10 manager_run at src/login/logind.c:1172

Potential duplicate: bug 1075491

Created attachment 1005677 [details]
File: backtrace

Created attachment 1005678 [details]
File: cgroup

Created attachment 1005679 [details]
File: core_backtrace

Created attachment 1005680 [details]
File: dso_list

Created attachment 1005681 [details]
File: environ

Created attachment 1005682 [details]
File: limits

Created attachment 1005683 [details]
File: machineid

Created attachment 1005684 [details]
File: maps

Created attachment 1005685 [details]
File: open_fds

Created attachment 1005686 [details]
File: proc_pid_status

Created attachment 1005687 [details]
File: var_log_messages

Created attachment 1005688 [details]
File: sosreport.tar.xz

I thinks that this is the same that pops up in rhel abrt quite often, but we weren't able to find the culprit.

At least this should be fixed by the rebase.

*** Bug 1089596 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2092.html