I have been able to recreate the problem on several ace files using package unace-nonfree, but not when using package unace. Is it possible that the bug was actually detected by using unrar-nonfree?
The good news is I managed to find the problem and have attached the patch for unace-free. ** Attachment added: "Increase buffer to cater for maximum file name length" http://launchpadlibrarian.net/35753473/acefuncs.c.patch -- *** stack smashing detected ***: /usr/bin/unace terminated https://bugs.launchpad.net/bugs/179684 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
