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 Thu, 15 Dec 2016 15:30:45 -0800
** Changed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
https://bugs.launchpad.net/bugs/1595607
Title:
/bin/nano:*** Error in `nano': free():
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=nano=month=2.5.3-2ubuntu1
Looking at some of the individual buckets we can see quite a few people
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
** Description changed:
+ [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
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
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
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nano in Ubuntu.
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.
** Also affects: nano (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: nano (Ubuntu Xenial)
Status: New => In Progress
**
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
9 matches
Mail list logo