Description of problem: When this happens, the whole GNOME session is suddenly closed. Version-Release number of selected component: systemd-222-12.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: __memcpy_sse2_unaligned executable: /usr/lib/systemd/systemd-journald global_pid: 475 kernel: 4.3.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37 #1 memcpy at /usr/include/bits/string3.h:53 #2 journal_file_append_entry_internal.constprop.119 at src/journal/journal-file.c:1356 #3 journal_file_append_entry.constprop.111 at src/journal/journal-file.c:1450 #4 write_to_journal at src/journal/journald-server.c:513 #5 dispatch_message_real.lto_priv.238 at src/journal/journald-server.c:820 #6 server_dispatch_message at src/journal/journald-server.c:918 #7 stdout_stream_log at src/journal/journald-stream.c:266 #8 stdout_stream_line.lto_priv.169 at src/journal/journald-stream.c:364 #9 stdout_stream_scan at src/journal/journald-stream.c:394
Created attachment 1113392 [details] File: backtrace
Created attachment 1113393 [details] File: cgroup
Created attachment 1113394 [details] File: core_backtrace
Created attachment 1113395 [details] File: dso_list
Created attachment 1113396 [details] File: environ
Created attachment 1113397 [details] File: limits
Created attachment 1113398 [details] File: maps
Created attachment 1113399 [details] File: mountinfo
Created attachment 1113400 [details] File: namespaces
Created attachment 1113401 [details] File: open_fds
Created attachment 1113402 [details] File: proc_pid_status
Created attachment 1113403 [details] File: var_log_messages
Upstream said at https://github.com/systemd/systemd/issues/1015 that systemd 223 included some journal-related changes which might fix this bug. Would it be possible to update to that version, or to backport the changes?
Possible fix, https://github.com/systemd/systemd/commit/dade37d403f1b8c1d7bb2efbe2361f2a3e999613
I would be happy to test a package for a while if it can help.
To me, this looks like another duplicate of bug #1300212, but I'm going to backport the above patch anyway.
The patch mentioned in comment 14 is already present in F23. *** This bug has been marked as a duplicate of bug 1300212 ***
OK. It really looks like this timeout is a cause of trouble for many people...
You can check https://bodhi.fedoraproject.org/updates/FEDORA-2016-3d6ff41417, which contains a batch of fixes including the timeout increase.