Todisc fails with bizarre fatal error [problem spotted]

[orange_juice]

Hallo, I am using todisc to create DVDs with the videos I shoot.

However, the same command that worked a few months ago, now fails with the following error:

[Jaglover]

[nlsa8z6zoz7lyih3ap]

I also am having trouble with this, and have not found a fix.
See https://forums.gentoo.org/viewtopic-p-5961433-highlight-.html#5961433

[salahx]

You are not the only one with this error. I've got it too. I narrowed down the problem to jpeg2yuv . It segfaults, and the reset of script jumps off the end of the world.

[orange_juice]

[salahx]

Ok, after some experimentation, the problem is due to the jpeg 6.2->7.0 upgrade. When I downgraded the jpeg-6.2 and rebuilt mjpegtools against it. Now jpeg2yuv no longer crashes.

However, todisc still fails, except this time, the culprit is "transcode". It too now crashes. However the fix is the same as with mjpegtools: downgrade jpeg. Once built against 6.2, transcode no longer crashes, and "todisc" completes.

[orange_juice]

[salahx]

I do indeed run Gentoo stable. The unstable version of transcode has a different problem (--print_status no longer exists on that one, causing todisc to fail )

The problem on the Ubunutu forums is unrelated to this one, on that one, jpeg2yuv does not crash there, and creates the file successfully, but ffmpeg chokes on it (libavcodec is part of ffmpeg).

Obviously, downgrading jpeg is out of the question for most people, and I'm most certainly NOT recommending doing it, I only did it to show where the problem lies.

Here's the backtrace for transcode:

[orange_juice]

All right, I understand.

Obviously, we will have to wait for this issue to be fixed.

Thank you for the update.

Kind regards,
orange_juice

[salahx]

I patched todisc to work against the new transcode to see if the newest version of transcode still crashes. Unfortunately, it does (and in exactly the same way, too).

So, I've filed bug 294488 for the transcode issue, and bug 294492 for the issue of >=transcode-1.1.0 not working with todisc.

[nlsa8z6zoz7lyih3ap]

THanks to everyone for the above comments.

I now have todisc with menus working just fine using:
(1) mjpeg-tools-1.8.0-r2 (rather than 1.9)
(2 jpeg-6b-r8 (rather than 7)
(3) transcode-1.1.5 (which is >1.1, despite the comments above that this does not work.)
AND
(3) todisc-svn-2782 (which I obtained using the command svn checkout http://tovid.googlecode.com/svn/trunk/tovid tovid),
rather than the one in portage.

Do you think that what appears to be a bug with transcode is actually a matter of the todisc in portage not tracking the api changes in transcode >=1.1 ?
Since I run ~amd64, there have been lots of occassions in the past in which I have found that "older" todiscs don't track the api changes in transcode,
and that is why I now go to svn to get my todisc. I have never had any problems resulting from this.

Regarding the downgrades of mjpegtools and jpeg, They were completely straigthforward for me using portage-2.2_rc5, which has the feature emerge @preserved-rebuild.
I don't know whether or not the stable versions of portage have this feature. Thanks again to everyone.

[orange_juice]

Great news! A solution has been spotted.

Actually, the latest stable portage in AMD64 (portage-2.1.6.13), does not have the "@preserved-rebuild" feature.

Nevertheless, todisc is still alive.

Thank you guys, you are awesome!

Kind regards,
orange_juice

[nlsa8z6zoz7lyih3ap]

I have to confess that when I tried the downgrade of jpeg on my wife's gentoo ~amd64 (which I had thought was almost identical to my own)
I had to struggle a bit, but I did finally succeed. The problem was that after the downgrade, emerge @revdep-rebuild claimed that it had to reinstall kde-3.5's arts,
but could not do so because it was no longer in portage. I thus uninstalled everything having to do with kde-3.5 and anything depending on it, and then emerge @revdep-rebuild
worked just fine. I am uncertain as to what the corresponding steps would be with a stable portage.