Bug 1306272

Summary:	nano seg-faults when NO replied to file lock conflict
Product:	[Fedora] Fedora	Reporter:	Don Swaner <greatauk37>
Component:	nano	Assignee:	Kamil Dudka <kdudka>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	dwmw2, greatauk37, jaswinder, kdudka
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-10 19:21:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Don Swaner 2016-02-10 13:05:02 UTC

Description of problem:
When 2 nano sessions attempt to edit the same file, and the file locking prompt is displayed, when "NO" is entered, nano seg-faults

Version-Release number of selected component (if applicable):
nano-2.4.2-2.fc23.x86_64

How reproducible:
always

Steps to Reproduce:
1. edit an existing file with nano (with "set locking" in .nanorc)
2. in a second nano session, attempt to edit the same file
3. reply 'N' to the file locking prompt

Actual results:
nano seg-faults

Expected results:
nano gracefully terminates the second attempted edit of the file.

Additional info:

Comment 1 Kamil Dudka 2016-02-10 17:18:39 UTC

I am not able to reproduce the crash locally.  Could you please attach a backtrace or coredump from the crash?

Comment 2 Don Swaner 2016-02-10 19:13:06 UTC

See BUG 1306413 for the backtrace.  Sorry for the inconvenience of the duplicate BUG report, but a SELINUX issue is complicating matters at this end, and my MATE automatic bug reporting tool didn't find BUG 1306272 for some reason.

Comment 3 Kamil Dudka 2016-02-10 19:21:43 UTC


*** This bug has been marked as a duplicate of bug 1306413 ***