Red Hat Bugzilla – Bug 592355
minicom unable to use unix domain socket file as modem
Last modified: 2011-12-08 22:34:26 EST
Description of problem:
minicom allows the use of a unix socket file by specifying the serial device as "unix#<path to socket file>". This does not currently work due to the changes applied to open_term in main.c by the minicom-2.4-rh.patch. The added code to perform a ttylock on the modem file does not check for the socket prefix, the attempt to lock fails and minicom exits.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure minicom to use a unix socket as the Serial Device setting
2. Attempt to connect
Exits with status 1, prints to stderr:
"Device unix#/home/dshea/modem access failed: No such file or directory."
Connect to the socket file
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Thank you for your bug report. I have updated patch so locking is not performed on UNIX sockets now.
minicom-2.4-2.fc14 has been submitted as an update for Fedora 14.
minicom-2.4-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update minicom'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/minicom-2.4-2.fc14
minicom-2.4-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.