Bug 783367
Summary: | [abrt] mediatomb-0.12.1-14.fc16: Process /usr/bin/mediatomb was killed by signal 11 (SIGSEGV) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | brothermand38 | ||||||||||||
Component: | mediatomb | Assignee: | Gwyn Ciesla <gwync> | ||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 16 | CC: | jk, mathieu-acct, richmattes, seanlkml | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | abrt_hash:86465dd6930a0efa60c53b884b497d59b71c03f9 | ||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-01-25 21:26:29 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
brothermand38
2012-01-20 06:38:17 UTC
Created attachment 556451 [details]
File: dso_list
Created attachment 556452 [details]
File: maps
Created attachment 556453 [details]
File: backtrace
Is there any way you can provide steps to reproduce this issue? I.e. what type of file you were using, what format you were transcoding to, what device were you streaming to, what if any config.xml changes you were using? It will be much easier for me if I can reproduce your issue. Thanks! Created attachment 557592 [details]
My Mediatomb file config.xml and transcode script file ffmpegvideo
These are the files my mediatomb is using for configuration, and mpeg transcoding.
I'm transcoding avi video to mpeg video file mediatomb-0.12.1-14.fc16.x86_64 would crash, mediatomb-0.12.1-12.fc16.x86_64.rpm works. I'm streaming to Directv H24, and HR24 boxes. Created attachment 570840 [details]
Mediatomb config file
I have a similar problem with 0.12.1-14 i368. It appears to segv on any attempted transcode. 0.12.1-12 works.
I've attached my config.xml. The transcode profile is audio2mp3 which calls a script to use ffmpeg. However in practice the script doesn't appear to get executed, and the segv happens with other attempted profiles.
Roger
Definitely a bug. Wanted to debug it but there doesn't appear to be a debuginfo package available. Ugh. What's the latest on this bug? transcoding solved! I managed to get mediatomb behave with the following patch: diff -urN src/tools.cc.old src/tools.cc --- src/tools.cc.old 2012-12-30 16:38:43.693986158 +0100 +++ src/tools.cc 2012-12-30 16:50:26.747679986 +0100 @@ -1223,7 +1223,8 @@ String param = params->get(i); String newParam = param.replace(_("%in"), in); newParam = newParam.replace(_("%out"), out); - newParam = newParam.replace(_("%range"), range); + if ( range != nil) + newParam = newParam.replace(_("%range"), range); if (param != newParam) params->set(newParam, i); } I did not debug further (I know nothing about c++), but a correct patch would address the replace method which is returning null when its second argument is null. Can we get this fix added to the next update? I'll get this out ASAP. mediatomb-0.12.1-22.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-22.fc17 mediatomb-0.12.1-15.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-15.fc16 mediatomb-0.12.1-22.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-22.fc18 Package mediatomb-0.12.1-15.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mediatomb-0.12.1-15.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0842/mediatomb-0.12.1-15.fc16 then log in and leave karma (feedback). This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Tested with Fedora 17 64 bit, fix worked correctly for fedora 17 64 bit. I did not see the issue. works for me: f17 i686 Thanks! mediatomb-0.12.1-22.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. mediatomb-0.12.1-22.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. mediatomb-0.12.1-15.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |