Bug 1306272 - nano seg-faults when NO replied to file lock conflict
Summary: nano seg-faults when NO replied to file lock conflict
Keywords:
Status: CLOSED DUPLICATE of bug 1306413
Alias: None
Product: Fedora
Classification: Fedora
Component: nano
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-10 13:05 UTC by Don Swaner
Modified: 2016-02-10 19:21 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-10 19:21:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.