** Changed in: nano (Debian)
Status: New => Fix Released
--
reproducible crash in nano on trying to save to a file different than the one
specified on the command line
https://bugs.launchpad.net/bugs/471568
You received this bug notification because you are a member of Ubuntu
Bugs, which
nano 2.2.1-1 is in Lucid and this seems to be fixed. If you need a fix in
previous releases, see
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
https://help.ubuntu.com/community/UbuntuBackports#request-new-packages
** Changed in: nano (Ubuntu)
Status: Fix Committed => Fix Release
Applied upstream in nano 2.2 -- http://savannah.gnu.org/patch/?7025
What are the chances we can fix this bug by either apply the above patch
or move to nano 2.2 before lucid?
** Changed in: nano (Ubuntu)
Status: New => Fix Committed
** Changed in: nano (Ubuntu)
Assignee: (unassigned
** Also affects: nano (Debian)
Importance: Undecided
Status: New
--
reproducible crash in nano on trying to save to a file different than the one
specified on the command line
https://bugs.launchpad.net/bugs/471568
You received this bug notification because you are a member of Ubuntu
B
The attached patch fixes the problem and should be applied upstream.
** Attachment added: "launchpad-471568.patch"
http://launchpadlibrarian.net/36758615/launchpad-471568.patch
** Description changed:
Binary package hint: nano
Steps to reproduce:
1) Put some content into a file, e.g.
Mostly a note to self: be sure to use configure --enable-nanorc when
trying to reproduce this bug from source.
--
reproducible crash in nano on trying to save to a file different than the one
specified on the command line
https://bugs.launchpad.net/bugs/471568
You received this bug notification
I'm guessing the problem is that nano is confused as to whether you have
a filename there or not.
When you launch data, the data structure containing the output filename
is not yet initialized, but after you input the filename, nano stats
file and sees that it is there (prompting you to overwrite)
Update: Upon testing on some other machines this is present on hardy and
jaunty as well as etch and lenny, and must be a very old bug, dating at
least back to etch/2.0.2. The reason other folks haven't noticed is that
it only happens when "set backup" is enabled in .nanorc AND you save the
file to
Here's an strace (attached)
** Attachment added: "nano-strace-segfault"
http://launchpadlibrarian.net/34994274/nano-strace-segfault
--
reproducible crash in nano on trying to save to a file different than the one
specified on the command line
https://bugs.launchpad.net/bugs/471568
You receiv
** Visibility changed to: Public
--
reproducible crash in nano on trying to save to a file different than the one
specified on the command line
https://bugs.launchpad.net/bugs/471568
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
10 matches
Mail list logo
