Description of problem: 1. edit a file with nano (with "set locking" in .nanorc) 2. start another nano session on the same file. 3. at the locking conflict prompt enter N Version-Release number of selected component: nano-2.4.2-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: nano temp.txt crash_function: main executable: /usr/bin/nano global_pid: 3499 kernel: 4.3.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (0 frames)
Created attachment 1122875 [details] File: backtrace
Created attachment 1122876 [details] File: cgroup
Created attachment 1122877 [details] File: core_backtrace
Created attachment 1122878 [details] File: dso_list
Created attachment 1122879 [details] File: environ
Created attachment 1122880 [details] File: exploitable
Created attachment 1122881 [details] File: limits
Created attachment 1122882 [details] File: maps
Created attachment 1122883 [details] File: mountinfo
Created attachment 1122884 [details] File: open_fds
Created attachment 1122885 [details] File: proc_pid_status
Created attachment 1122886 [details] File: var_log_messages
*** Bug 1306272 has been marked as a duplicate of this bug. ***
The backtrace does not make any sense to me. Are you sure you have up2date debuginfo packages installed?
5 or 8 new packages were automatically installed today during the reporting of this bug (1306413), so I assume the debuginfo is current. If there is some additional check I need to do to insure it is current, I don't know how to do that.
The backtrace is actually correct although it contains only the main() frame. Sorry for not recognizing it previously! The following patch will fix it: --- a/src/nano.c +++ b/src/nano.c @@ -520,15 +520,12 @@ openfilestruct *make_new_opennode(void) openfilestruct *newnode = (openfilestruct *)nmalloc(sizeof(openfilestruct)); - newnode->filename = NULL; - newnode->fileage = NULL; - newnode->filebot = NULL; - newnode->edittop = NULL; - newnode->current = NULL; + /* make sure that everything is initialized instead of open-coding + * NULL assignments that compilers do not check for completeness */ + memset(newnode, 0, sizeof *newnode); + #ifndef NANO_TINY - newnode->current_stat = NULL; newnode->last_action = OTHER; - newnode->lock_filename = NULL; #endif return newnode;
pushed to the f23 branch dist-git: http://pkgs.fedoraproject.org/cgit/rpms/nano.git/commit/?id=798e2b0d
nano-2.4.2-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7cad63cca8
The bug occurred when nano was executed in a MATE terminal with monospace 12 font size. If I "zoom out" so that the font size is smaller, then the bug does not occur.
Could you please re-test it with nano-2.4.2-3.fc23? http://koji.fedoraproject.org/koji/buildinfo?buildID=734964
nano-2.4.2-3.fc23 has been pushed to the Fedora 23 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-2016-7cad63cca8
nano-2.4.2-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.