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 528331 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 523936
Product: totem
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-04-16 00:33 UTC by leogex
Modified: 2008-04-16 05:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description leogex 2008-04-16 00:33:38 UTC 
Version: 2.22.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-chris2 #1 SMP Sun Jan 27 15:29:46 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 76701696 vsize: 76701696 resident: 26214400 share: 14757888 rss: 26214400 rss_rlim: 4294967295
CPU usage: start_time: 1208306007 rtime: 124 utime: 104 stime: 20 cutime:2 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb687f740 (LWP 11951)]
[New Thread 0xb4322b90 (LWP 11956)]
[New Thread 0xb4be7b90 (LWP 11955)]
[New Thread 0xb57a9b90 (LWP 11954)]
[New Thread 0xb6144b90 (LWP 11953)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195333

Thread 3 (Thread 0xb4be7b90 (LWP 11955))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
    from /usr/lib/gstreamer-0.10/libgstreal.so
  • #8 ??
    from /usr/lib/gstreamer-0.10/libgstreal.so
  • #9 ??
    from /usr/lib/gstreamer-0.10/libgstreal.so
  • #10 ??
  • #11 pthread_getspecific
    from /lib/i686/cmov/libpthread.so.0
  • #12 gst_pad_set_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #13 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 ??
  • #15 ??
  • #16 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #17 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #18 ??
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #19 ??
  • #20 ??
  • #21 ?? 




----------- .xsession-errors (80 sec old) ---------------------
[00000289] main input error: no suitable access module for `'
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e000e1 (VLC media )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
[20:28:47.552 flock:peopleSidebar:error] Exception in call to localizeElement
[20:28:47.555 flock:peopleSidebar:error] Exception in call to localizeElement
[20:28:47.556 flock:peopleSidebar:error] Exception in call to localizeElement
[20:28:47.557 flock:peopleSidebar:error] Exception in call to localizeElement
(totem:11901): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed
(totem:11901): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed
(totem:11901): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed
(totem:11901): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed
--------------------------------------------------
Comment 1 Philip Withnall 2008-04-16 05:48:53 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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