Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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#33748 - [bftpd] segfault when a client tries to connect
Attached to Project:
Arch Linux
Opened by John (skeov) - Thursday, 07 February 2013, 11:34 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 19 January 2014, 20:06 GMT
Opened by John (skeov) - Thursday, 07 February 2013, 11:34 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 19 January 2014, 20:06 GMT
|
DetailsWhat the title says. Probably caused by a glibc update.
Logs: Feb 07 13:24:05 myhost kernel: bftpd[765]: segfault at 0 ip 00007f6e2145a57a sp 00007fffbefd9548 error 4 in libc-2.17.so[7f6e21330000+1a4000] Feb 07 13:24:05 myhost systemd-coredump[766]: Process 765 (bftpd) dumped core. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Sunday, 19 January 2014, 20:06 GMT
Reason for closing: Fixed
Sunday, 19 January 2014, 20:06 GMT
Reason for closing: Fixed
Comment by Jonathan Doman (jrmrjnck) -
Saturday, 14 September 2013, 23:43 GMT
I am still affected by this. Has bftpd been broken for 7 months? I only use bftpd now and then for small tasks, but I like its simplicity, so I hope this can be fixed.