GNOME Bugzilla – Bug 695453
v 2.1.7 crashes when browsing my folder
Last modified: 2014-01-24 14:18:48 UTC
the program stops and crashes when browsing (searching) for files. it seems to happen only with folder containing m4a or mp4 files... thx for support
Ubuntu 12.04 uptodate
Here is an extract of ls -l of the folder that makes problem. I (me user) own the files. -rw-rw-r-- 1 .mp3 -rw-r--r-- 1 .mp4 -rw-rw-r-- 1 .m4a -rw-rw-r-- 1 .jpeg -rw-rw-r-- 1 .m4a -rw-rw-r-- 1 .mp4 -rw-rw-r-- 1 .m4a -rw-r--r-- 1 .mp4 -rw-rw-r-- 1 .mp4 -rw-rw-r-- 1 .m4a -rw-rw-r-- 1 .mp3 -rw-rw-r-- 1 .jpeg -rw-rw-r-- 1 .m4a -rw-r--r-- 1 .mp4 -rw-rw-r-- 1 .m4a -rw-rw-r-- 1 .mp3 -rw-r--r-- 1 .mp4
okay, i removed the mp4 (video) files from the folder and now its fine. so one or several .mp4 files are making the problem...
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 240206 [details] GDB Log w/backtrace
I am experiencing the same behavior on Parabola GNU/Linux. I have attached a GDB backgtrace.
Comment on attachment 240206 [details] GDB Log w/backtrace Thanks for the trace. Could you install the debug symbols for EasyTAG and TagLib and get another back trace? Finally, could you paste the stack trace into the comment field rather than attaching it to the bug. This way, the stack trace plugin can process the trace.
Sorry about that David. I'm new to Parabola. Hopefully this will be enough for you.
+ Trace 231705
(In reply to comment #8) > Sorry about that David. I'm new to Parabola. Hopefully this will be enough > for you. Thanks Nathan, with that trace I was able to fix the bug. I pushed a patch to fix to the MP4 error handling and crash to master as commit f4c3b3fbacdaf6a4c32b2c39efa88c6fea6926b1.
*** Bug 702915 has been marked as a duplicate of this bug. ***
*** Bug 707664 has been marked as a duplicate of this bug. ***
*** Bug 722915 has been marked as a duplicate of this bug. ***