GNOME Bugzilla – Bug 680452
dragon player, and sometimes vlc crash immediately or within a few seconds of beginning to play an .avi file.
Last modified: 2012-07-31 17:57:13 UTC
I reported a bug with dragon player here: https://bugs.kde.org/show_bug.cgi?id=302026 but it was changed to a bug with gstreamer, so I thought I'd post it on the gstreamer bugzilla. For some reason all the newlines got stripped when I copied it, so I've left the full backtrace at the original bug, as reformatting it was very tedious, but I hope the important bits are here. I'd be happy to provide further information about my installation, or try removing or adding to configuration files. When VLC crashes, it's not part of KDE, so doesn't seem to bring up the backtrace. Application: dragon (2.0) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.0.0-21-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: This happens every time I open some .avi files (from dolphin, ktorrent or folder view applet) For example, it crashed with the files contained in this torrent: http://ca.isohunt.com/download/10530943/stargate.torrent But other files do it too. I don't know at this time whether it's just .avi files or all .avi files. The crash can be reproduced every time. -- Backtrace: Application: Dragon Player (dragon), signal: Segmentation fault [Current thread is 1 (Thread 0x7f0474b487a0 (LWP 8256))]
+ Trace 230558
Thread 1 (Thread 0x7f0474b487a0 (LWP 8256))
Reported using DrKonqi
Does it crash when you type this on the command line? gst-launch-0.10 playbin2 uri=file:///path/to/file.avi
I will be back at my computer tomorrow, so I will try the command then. Rob
I tried a large .avi file that causes both Dragon player and vlc to crash, but when I used the command in comment 1, it played the entire length without crashing. There was no possibility to change the volume, pause or skip (from the name of the function calls in the trace, I guess it might be volume-related), but in the absence of this functionality, it played fine. Does this help up track the cause? Rob
Hello, I just wanted to apologise - I foolishly installed some weird hacked version of phonon from a ppa perhaps more than a year ago. I didn't have any problems for quite some months after I installed it, and forgot that I wasn't using the official version. Then the problem started a few months back. When looking through my installed packages today, I discovered the version seemed odd. I've just reverted to the official ubuntu package and it now seems to have fixed the bug, making this report invalid. The lesson is not to work from bodged 3rd-party packages. I'm sorry to have taken up your time, Rob