Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1558532 - insert key crashes `nano --restricted`
Summary: insert key crashes `nano --restricted`
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nano
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-20 12:21 UTC by René Genz
Modified: 2018-03-30 13:12 UTC (History)
2 users (show)

Fixed In Version: nano-2.9.4-2.fc29 nano-2.9.4-2.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-30 13:12:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description René Genz 2018-03-20 12:21:40 UTC
Description of problem:
`nano --restricted` is crashing if you press the insert key on the keyboard.

Version-Release number of selected component (if applicable):
$ rpm -q nano
nano-2.9.4-1.fc28.x86_64

How reproducible:
easy, 100%

Steps to Reproduce:
1. in terminal execute:
$ nano --restricted
2. press insert key on keyboard

Actual results:
at the bottom of nano you can see
    [ This function is disabled in restricted mode ]Segmentation fault (core dumped)
(followed by the menu "^G Get Help ..." and your prompt)

Expected results:
nano should not crash

Additional info:
an unusable stack trace is: https://retrace.fedoraproject.org/faf/reports/bthash/3a8c2fdaee5138975892c9e1a4065fea1712cfb9/

With nano-2.9.4-1.fc28.x86_64 `nano` is not crashing when the insert key is pressed.

With nano-2.9.3-3.fc28.x86_64 `nano --restricted` did not crash when the insert key was pressed.

Comment 1 Kamil Dudka 2018-03-20 12:33:27 UTC
Confirmed.  I will have a look...

Comment 2 Kamil Dudka 2018-03-20 16:04:51 UTC
I have proposed a fix upstream:

http://lists.gnu.org/archive/html/nano-devel/2018-03/msg00080.html

Comment 3 René Genz 2018-03-21 07:42:09 UTC
Thank you very much :)

Comment 5 Fedora Update System 2018-03-21 12:37:11 UTC
nano-2.9.4-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d34a3f42d

Comment 6 Fedora Update System 2018-03-21 14:15:10 UTC
nano-2.9.4-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d34a3f42d

Comment 7 Fedora Update System 2018-03-30 13:12:01 UTC
nano-2.9.4-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.