| Summary: | Audio Spectrum Widget causes Segmentation Fault | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Jacob Kauffmann <jacob> |
| Component: | User Interface & Miscellaneous | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jacob Kauffmann
2016-05-12 23:37:23 UTC
Alright, I haven't gotten any feedback yet, but just in case anyone else is having this problem, I thought I'd share my progress. I took a look at the backtrace and figured that the problem must have to do with the "AudioGraphWidget." I took the liberty of removing every trace of the "audio graph spectrum" widget from the source code (which was basically attempting to compile over and over again and removing references from whichever files the compiling error included, since I don't know what I'm doing.) And after doing so, Kdenlive runs! The only problem is that now, I don't have the audio spectrum widget, which I actually happen to use. (I find it a great visual way to tell when I can make a cut without voices sounding cut off.) I know the widget was working fine early last week, so either something about the widget changed, or something about my system (possibly that "atomic" C++ handler) changed. Now that I've got Kdenlive working, this is much less critical for me, but I'd still like to have that widget, and I'd also like to be able to update without stripping out the audio spectrum widget and manually compiling every time. Like I said, not really a coder here, but if I can be of any assistance debugging this, please let me know. Today when I sat down to use my computer, the regular Kdenlive opened up normally again, and I can once again use the Audio Spectrum widget. I did NOT update before it started working again, although I have updated since and it is still working. Hopefully the backtrace proves that I'm not crazy, but it seems that this issue has magically resolved itself. I would still be happy to help in any way I can if more info on this issue is ever needed. |