Bug 765659

Summary:	minicom unable to use unix domain socket file as modem
Product:	Red Hat Enterprise Linux 6	Reporter:	Gris Ge <fge>
Component:	minicom	Assignee:	Martin Sehnoutka <msehnout>
Status:	CLOSED ERRATA	QA Contact:	Branislav Náter <bnater>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2	CC:	bnater, mlichvar, thozza
Target Milestone:	rc	Keywords:	EasyFix, FastFix, Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	minicom-2.3-7.el6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	592355	Environment:
Last Closed:	2017-03-21 10:19:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	592355
Bug Blocks:	1373253

Description Gris Ge 2011-12-09 03:34:26 UTC

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.

Comment 2 Suzanne Logcher 2012-02-14 23:23:40 UTC

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.

Comment 3 Jaromír Cápík 2016-01-18 13:19:57 UTC

Needs to be backported from the fc14 rh patch.

Comment 4 Jaromír Cápík 2016-01-18 13:24:51 UTC

The following fedora git diff documents the required changes:

git diff 9ebd4bf909f4ce634ccbf2d0a927a96114fb0feb 340b6d43f6ffd1fae3cad00ba318b67436b5d0e1

Comment 14 errata-xmlrpc 2017-03-21 10:19:37 UTC

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