Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Same problem in RHEL 6.2
+++ This bug was initially created as a clone of Bug #592355 +++
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):
minicom-2.4-1.fc14.i686
How reproducible:
Always
Steps to Reproduce:
1. Configure minicom to use a unix socket as the Serial Device setting
2. Attempt to connect
Actual results:
Exits with status 1, prints to stderr:
"Device unix#/home/dshea/modem access failed: No such file or directory."
Expected results:
Connect to the socket file
Additional info:
--- Additional comment from triage.org on 2010-07-30 19:37:46 CST ---
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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--- Additional comment from fedora-admin-xmlrpc on 2010-09-08 20:11:50 CST ---
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
--- Additional comment from jgorig on 2010-09-17 18:49:17 CST ---
Thank you for your bug report. I have updated patch so locking is not performed on UNIX sockets now.
--- Additional comment from updates on 2010-09-17 18:53:46 CST ---
minicom-2.4-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/minicom-2.4-2.fc14
--- Additional comment from updates on 2010-09-21 02:43:31 CST ---
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
--- Additional comment from updates on 2010-09-30 14:20:08 CST ---
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.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
The following fedora git diff documents the required changes:
git diff 9ebd4bf909f4ce634ccbf2d0a927a96114fb0feb 340b6d43f6ffd1fae3cad00ba318b67436b5d0e1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0665.html