After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 495949 - crash in Movie Player: ver un partido de futbol...
crash in Movie Player: ver un partido de futbol...
Status: RESOLVED DUPLICATE of bug 336370
Product: totem
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-11-11 19:13 UTC by no
Modified: 2007-11-12 07:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description no 2007-11-11 19:13:23 UTC 
Version: 2.18.3

What were you doing when the application crashed?
ver un partido de futbol con el protocolo sop


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 137277440 vsize: 137277440 resident: 43089920 share: 22818816 rss: 43089920 rss_rlim: 4294967295
CPU usage: start_time: 1194807407 rtime: 1196 utime: 1058 stime: 138 cutime:4 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209140624 (LWP 31046)]
[New Thread -1301283952 (LWP 31178)]
[New Thread -1227457648 (LWP 31175)]
[New Thread -1266345072 (LWP 31172)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 177066

Thread 2 (Thread -1301283952 (LWP 31178))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/gstreamer-0.10/libgstasf.so
  • #11 ??
    from /usr/lib/gstreamer-0.10/libgstasf.so
  • #12 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #13 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 ??
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #15 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #18 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #19 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #20 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #21 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 start_thread
    from /lib/libpthread.so.0
  • #25 clone
    from /lib/libc.so.6 


----------- .xsession-errors (7 sec old) ---------------------
** Message: Error: Resource not found.
gstgnomevfssrc.c(859): gst_gnome_vfs_src_start (): /play/source:
Could not open vfs file "http://localhost:8908/" for reading: El servicio no se encuentra disponible (38)
** Message: Error: Could not determine type of stream.
gsttypefindelement.c(491): gst_type_find_element_handle_event (): /play/decodebin14/typefind
** Message: Error: Resource not found.
gstgnomevfssrc.c(859): gst_gnome_vfs_src_start (): /play/source:
Could not open vfs file "http://localhost:8908/" for reading: El servicio no se encuentra disponible (38)
JACK tmpdir identified as [/dev/shm]
** ERROR **: file gstasfdemux.c: line 498 (gst_asf_demux_get_var_length): assertion failed: (*p_size >= 1)
aborting...
--------------------------------------------------
Comment 1 Philip Withnall 2007-11-12 07:27:49 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 336370 ***