Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 578894 - app-cdr/k3b-2.0.3-r2 fails when ripping video dvd
Summary: app-cdr/k3b-2.0.3-r2 fails when ripping video dvd
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2016-04-03 07:07 UTC by Paul Jewell
Modified: 2017-02-26 03:16 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Patch to fix problem (k3b-2.0.3-r2.patch,574 bytes, patch)
2016-04-03 07:07 UTC, Paul Jewell
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Jewell 2016-04-03 07:07:11 UTC
Created attachment 429536 [details, diff]
Patch to fix problem

When ripping video dvd, two issues were uncovered. One was due to transcode seg faulting (separate bug submitted with patch), and then when that was resolved, k3b would fail with "Error opening AVI file". 
This is a known issue: https://bugs.kde.org/show_bug.cgi?id=350403
Patch to gentoo ebuild attached.
Comment 1 Markus Wernig 2016-10-13 13:33:47 UTC
This issue still exists in app-cdr/k3b-2.0.3-r3.

Manually running the transcode command at the end of the "debugging output" window succeeds after removing the quotes around the output file name (-o) and removing all blanks and shell metacharacters from the file name (if using xvid as video codec - mpeg4 does not work because transcode does not support the "new" avcodec_encode_video2 API in libavcodec, see also https://bugs.launchpad.net/ubuntu/+source/transcode/+bug/1477272)

The patch reproduced in attachment #429536 [details, diff] from the kde bugtracker is from 2015-10-26, almost a year ...
Comment 2 Andreas Sturmlechner gentoo-dev 2017-02-12 21:27:16 UTC
Please try out 2.0.3-r4 which contains the fix.
Comment 3 Markus Wernig 2017-02-26 03:16:06 UTC
Tested with 2.0.3-r5, and the problem does not occur anymore.

Good work, thanks for the fix!

Considering that we have been waiting for this for 1.5 years, providing patch, links and everything (well, not me), you might as well have waited for our feedback before closing the issue. We do exist, you know.