/bin/nano:*** Error in `nano': free(): invalid next size (normal): ADDR ***

[errors.ubuntu.com bug bridge]

[Test Case]
Using the provided Error Tracker bucket confirm that there are no instances of the crash with the version of the package from -proposed. Given that we don't have a reproducer we should let the package age for longer than 7 days to ensure many users are testing it.

The Ubuntu Error Tracker has been receiving reports about a problem regarding nano. This problem was most recently seen with version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9 contains more details.

[Benno Schulenberg (bennoschulenberg)]

I am quite willing to work on this issue, but... don't make me jump through hoops just to see the crash report. (Take an example from Fedora, where such reports are freely accessible (for example, https://retrace.fedoraproject.org/faf/reports/1181921/). I don't need heaps of information -- a backtrace is normally enough.)

Anyway, I'm guessing your users are hitting a bug that is fixed by the first patch attached to this message: https://lists.gnu.org/archive/html/nano-devel/2016-04/msg00075.html. That patch (and the other three) were already applied to nano in Debian.

[Brian Murray (brian-murray)]

This fix made it into Yakkety and Zesty, but not Xenial. I've uploaded a fix to the Xenial SRU queue for review by the Ubuntu SRU team.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted nano into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nano/2.5.3-2ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Timo Aaltonen (tjaalton)]

bug description probably could be more like the SRU guidelines ask, but looks like there is no clear test case, so I've acked the upload

[Sebastien Bacher (seb128)]

there are no e.u.c reports from the new version (though the numbers were not that high with the current one so it means not many users are hitting the issue and that it could be that none of the proposed testers hit it yet) nor regressions/new bugs reported and nano seems to work fine, probably good to set as verification-done?

[Brian Murray (brian-murray)]

To get an idea of the number of users of the proposed package I filtered for crashes from Ubuntu 16.04 and with the proposed version of the package:

https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=nano&period=month&version=2.5.3-2ubuntu1

Looking at some of the individual buckets we can see quite a few people using 2.5.3-2ubuntu1 and that version doesn't appear in the bucket for the crash we are trying to fix, so I'll set it as v-done.

[Launchpad Janitor (janitor)]

This bug was fixed in the package nano - 2.5.3-2ubuntu1

---------------
nano (2.5.3-2ubuntu1) xenial-proposed; urgency=medium

  * Apply upstream patch to not call free on the result of a dirname.
    (LP: #1595607)

 -- Brian Murray <email address hidden> Thu, 15 Dec 2016 15:30:45 -0800

[Steve Langasek (vorlon)]

The verification of the Stable Release Update for nano has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.