As the patch for bug #1641592 has been released to Xenial, it means that
this bug has been fixed too.
** Changed in: nano (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
(Oh! For some reason I am not getting all of the bug mail from
Launchpad. At least: I missed notifications about this bug.)
Hm... It seems that free() on Ubuntu checks that nothing was written
outside of the allocated space? Does malloc() put a "canary" at the
tail?
Anyway, I am pretty sure t
** Changed in: nano (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572807
Title:
/bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR
**
It's possible the stacktrace in the Error Tracker contains sensitive
information, that's why access to it is restricted and it's not
automatically added to the bug report here.
Here's the Stacktrace though:
#0 0x7f38ce77e428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/rais
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nano (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572807
Title:
/bin/
I am logged in on Launchpad, why must I log in again (on Ubuntu One) to
access the above information? I do not want to log in again, nor create
another account. Just give me the info about the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
