Red Hat Bugzilla – Bug 864758
mount_afp crashing on libgcryprt
Last modified: 2013-07-31 22:40:01 EDT
When trying to use mount_afp, it segfaults, which appears to be caused by libgcrypt.
Version-Release number of selected component (if applicable):
Executing mount_afp on a networked AFP server requiring a username and password, ie:
mount_afp "afp://$user:$password@$IP/$Volume" /mnt/AFP
Steps to Reproduce:
1. Run a mount_afp command like above
2. Observe /var/log/messages
Network volume being mounted properly
My messages file produces the following output when above mention command is ran:
Oct 10 13:56:10 crapple : Starting up AFPFS version 0.8.1
Oct 10 13:56:11 crapple : Libgcrypt warning: missing initialization - please fix the application
Oct 10 13:56:11 crapple kernel: [190377.391105] afpfsd general protection ip:371be0cb55 sp:7fff9fdd2100 error:0 in libafpclient.so.0.0.0[371be00000+1e000]
Oct 10 13:56:11 crapple abrt: Saved core dump of pid 10500 (/usr/bin/afpfsd) to /var/spool/abrt/ccpp-2012-10-10-13:56:11-10500 (9248768 bytes)
Oct 10 13:56:11 crapple abrtd: Directory 'ccpp-2012-10-10-13:56:11-10500' creation detected
Oct 10 13:56:11 crapple abrtd: Generating backtrace
Oct 10 13:56:11 crapple abrtd: Duplicate: core backtrace
Oct 10 13:56:11 crapple abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2012-10-10-13:33:51-10110
Oct 10 13:56:11 crapple abrtd: Corrupted or bad directory '/var/spool/abrt/ccpp-2012-10-10-13:56:11-10500', deleting
Forgot to say, this was the output of mount_afp:
The afpfs daemon does not appear to be running for uid 0, let me start it for you
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.