GNOME Bugzilla – Bug 353301
aborts in _get_element_by_uri(), probably due to buggy element
Last modified: 2007-06-18 02:35:47 UTC
Version: 1.5.92 What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.91 2006-08-08 (Ubuntu) BugBuddy Version: 2.15.90 Memory status: size: 87605248 vsize: 0 resident: 87605248 share: 0 rss: 25079808 rss_rlim: 0 CPU usage: start_time: 1156800177 rtime: 0 utime: 134 stime: 0 cutime:128 cstime: 0 timeout: 6 it_real_value: 0 frequency: 8 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226185040 (LWP 17037)] [New Thread -1276191840 (LWP 17042)] [New Thread -1267799136 (LWP 17041)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71141
Thread 1 (Thread -1226185040 (LWP 17037))
Can you reproduce this? If yes, could you run totem (or 'gst-launch-0.10 playbin uri=sftp://foo@bar') in gdb with G_DEBUG=fatal_warnings, wait until it aborts and then do (gdb) frame #10 (or whatever frame search_by_entry() is at according to 'bt') (gdb) print *feature (gdb) print *factory and paste all the output you get from that?
Thanks for your feedback! After installing the gstreamer debugging packages, I suddently got another bt:
+ Trace 71200
After recompiling gnome-keyring myself (because there is no libgnome-keyring-dbg avail. for Ubuntu), the issue is gone. Changing status to NEEDINFO, maybe we'll get a dup some day.
Surely this is a bug in gnomevfs in the end? Still, it shouldn't crash/abort like this. Fixed in GStreamer core CVS HEAD: 2006-09-25 Tim-Philipp Müller <tim at centricular dot net> * gst/gsturi.c: (search_by_entry): Don't assert/crash here if a uri handler doesn't return any supported protocols. The list of protocols could be generated dynamically at runtime or at plugin registration, and an error in the underlying library shouldn't be fatal (#353301).
*** Bug 381454 has been marked as a duplicate of this bug. ***
*** Bug 415144 has been marked as a duplicate of this bug. ***
*** Bug 421657 has been marked as a duplicate of this bug. ***
*** Bug 448647 has been marked as a duplicate of this bug. ***