[Bug 514739] Re: [SRU] ripperX assert failure: *** buffer overflow detected ***: ripperx terminated

I've ripped several disks with the lucid-proposed package, and no problems occur with > 9 tracks. However, it would be really nice if the package also contained the fix here: https://bugs.launchpad.net/ubuntu/+source/ripperx/+bug/671852. Thanks to everyone for their work on this project. -- You

[Bug 514739] Re: ripperX assert failure: *** buffer overflow detected ***: ripperx terminated

Here's another buffer overflow bug fix. To see this problem, you have to encode many tracks without restarting ripperX. The path environment variable outgrows the buffer size in this function. ** Patch added: "fix_path_buffer_overflow.diff" https://bugs.launchpad.net/ubuntu/+source/ripperx

[Bug 671852] Re: "Convert spaces to underscores" modifies the track data, not just the filename.

** Patch added: "fix_underscore_in_id3_data.diff" https://bugs.launchpad.net/bugs/671852/+attachment/1724902/+files/fix_underscore_in_id3_data.diff -- "Convert spaces to underscores" modifies the track data, not just the filename. https://bugs.launchpad.net/bugs/671852 You received this bug

[Bug 671852] [NEW] "Convert spaces to underscores" modifies the track data, not just the filename.

Public bug reported: Binary package hint: ripperx When I ask ripperX to "Convert spaces to underscores" in the "Files" configuration panel, I only expect that to apply to the directories and files that are created by ripperX. However, it also modifies the Artist and Album data files, so that ID3

[Bug 514739] Re: ripperX assert failure: *** buffer overflow detected ***: ripperx terminated

I rebuilt ripperX from the source packages and the error returned on my system. This would seem to be good evidence that the patch is useful. I also have used ripperX for many years. That's why I was motivated to find a solution to the problem when I moved to lucid. However, just because the co

[Bug 514739] Re: ripperX assert failure: *** buffer overflow detected ***: ripperx terminated

This problem is not caused by libid3tag. RipperX has an array of size 2 to store the track number string into. So, higher than 1 digits, plus the null character cause the buffer to overflow. I imagine other builds do not have problems because they are lucky with stack frame construction. Attach

[Bug 87787] Re: [apport] emacs21-x crashed with SIGSEGV

I had 3 or 4 emacs frames open. I opened another frame, and used the font menu to change the new frame's font. After about 30 seconds, emacs crashed while I was working in a different application. The traces look like it may be related to this thread. I hope there is useful information here. T