Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#57450 - systemd-237 makes rsync segfault

Attached to Project: Arch Linux
Opened by Radek Podgorny (rpodgorny) - Friday, 09 February 2018, 22:10 GMT
Last edited by Dave Reisner (falconindy) - Monday, 12 February 2018, 19:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


after upgrading to systemd-237.0-2 rsync starts to dump core (on incomming connections):

Feb 09 23:04:05 orion systemd-coredump[31393]: Process 31258 (rsync) of user 1013 dumped core.

Stack trace of thread 31258:
#0 0x00007f6335fd2860 raise (
#1 0x00007f6335fd3ec9 abort (
#2 0x00007f633570264e n/a (
#3 0x00007f633571262f n/a (
#4 0x00007f633571aa7f n/a (
#5 0x00007f633571bd5a n/a (
#6 0x00007f633571c30d n/a (
#7 0x00007f6335701850 _nss_systemd_getpwnam_r (
#8 0x00007f6336060b2f getpwnam_r@@GLIBC_2.2.5 (
#9 0x00007f63360604c9 getpwnam (
#10 0x000055c76ca46796 n/a (rsync)
#11 0x000055c76ca46b25 n/a (rsync)
#12 0x000055c76ca47167 n/a (rsync)
#13 0x000055c76ca158f3 n/a (rsync)
#14 0x000055c76ca1c660 n/a (rsync)
#15 0x000055c76ca4142e n/a (rsync)
#16 0x000055c76ca248d8 n/a (rsync)
#17 0x000055c76ca310dd n/a (rsync)
#18 0x000055c76ca3179d n/a (rsync)
#19 0x000055c76ca13ba9 n/a (rsync)
#20 0x00007f6335fbef4a __libc_start_main (
#21 0x000055c76ca13c6a n/a (rsync)

i have no idea what may be wrong but downgrade to systemd-236.81-1 fixes the issue. yes, i've tried restart after systemd upgrade.
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 12 February 2018, 19:29 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#57388 
Comment by Dave Reisner (falconindy) - Saturday, 10 February 2018, 02:36 GMT
That's an abort, not a segfault, which means there's an assertion failure in the logs as well. My guess is this is already fixed in systemd-237.31-1, as well ( FS#57388 ).
Comment by Radek Podgorny (rpodgorny) - Monday, 12 February 2018, 19:27 GMT
hmmm, so it looks like the aborts are gone with 237.31... ;-)