Your message dated Fri, 10 May 2019 17:19:29 +0200
with message-id <[email protected]>
and subject line Re: segmentation fault when editing two files in two terminals
has caused the Debian Bug report #787890,
regarding segmentation fault when editing two files in two terminals
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
787890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787890
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nano
Version: 2.4.1-1
Severity: normal
Dear Maintainer,
2 open terminal windows.
"nano foo" in terminal A, leave nano open.
Then do "nano bar foo" in terminal B.
It will ask "File foo is being edited (by $USERNAME with nano 2.4.1, PID
14361); continue?"
Press N.
You are editing bar.
Type something.
Do ^X
>> Press N and get a segmentation fault.
>> Press Y and bar will be saved but you still get a segmentation fault.
I was able to reproduce this on multiple Debian unstable systems.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages nano depends on:
ii libc6 2.19-18
ii libncursesw5 5.9+20150516-2
ii libtinfo5 5.9+20150516-2
ii zlib1g 1:1.2.8.dfsg-2+b1
nano recommends no packages.
Versions of packages nano suggests:
pn spell <none>
-- no debconf information
--
https://justaguy.pw
PGP fingerprint: 3270 891F 27E5 2638 4EF6 706D 609E 2842 CB06 CC23
The Net treats censorship as a defect and routes around it. ~John
Gilmore, 1993
--- End Message ---
--- Begin Message ---
Version: 2.4.3-1
Reproduction recipe for 2.4.1:
Run in one terminal: nano --ignore --locking second
Run in another terminal: nano --ignore --locking first second
In the latter terminal, answer N to the question
"File second is being edited (...); continue?"
Then (in the file 'first') type: xxx ^X N
Result: Segmentation fault
Fixed since nano-2.4.3.
Benno
--- End Message ---
