Version-Release number of selected component: systemd-222-8.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: link_entry_into_array.lto_priv.144 executable: /usr/lib/systemd/systemd-journald global_pid: 15007 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 link_entry_into_array.lto_priv.144 at src/journal/journal-file.c:1190 #1 link_entry_into_array_plus_one at src/journal/journal-file.c:1260 #2 journal_file_link_entry_item at src/journal/journal-file.c:1284 #3 journal_file_link_entry at src/journal/journal-file.c:1325 #4 journal_file_append_entry_internal.constprop.119 at src/journal/journal-file.c:1368 #5 journal_file_append_entry.constprop.111 at src/journal/journal-file.c:1450 #6 write_to_journal at src/journal/journald-server.c:513 #7 dispatch_message_real.lto_priv.238 at src/journal/journald-server.c:820 #8 server_dispatch_message at src/journal/journald-server.c:918 #9 server_process_syslog_message at src/journal/journald-syslog.c:377
Created attachment 1089407 [details] File: backtrace
Created attachment 1089408 [details] File: cgroup
Created attachment 1089409 [details] File: core_backtrace
Created attachment 1089410 [details] File: dso_list
Created attachment 1089411 [details] File: environ
Created attachment 1089412 [details] File: limits
Created attachment 1089413 [details] File: maps
Created attachment 1089414 [details] File: mountinfo
Created attachment 1089415 [details] File: open_fds
Created attachment 1089416 [details] File: proc_pid_status
Another user experienced a similar problem: working with Firefox, Nemo, qbittorrent. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: link_entry_into_array.lto_priv.144 executable: /usr/lib/systemd/systemd-journald global_pid: 579 kernel: 4.2.8-300.fc23.x86_64 package: systemd-222-10.fc23 reason: systemd-journald killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
*** This bug has been marked as a duplicate of bug 1300212 ***