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 541287 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 426990
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-07-02 17:56 UTC by koji.nakamura
Modified: 2008-07-02 19:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description koji.nakamura 2008-07-02 17:56:10 UTC 
Version: 2.22.2

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 171986944 vsize: 171986944 resident: 66244608 share: 16093184 rss: 66244608 rss_rlim: 4294967295
CPU usage: start_time: 1215021328 rtime: 236 utime: 214 stime: 22 cutime:2 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68c3740 (LWP 20691)]
[New Thread 0xb139fb90 (LWP 20704)]
[New Thread 0xb1c9eb90 (LWP 20703)]
[New Thread 0xb24c4b90 (LWP 20702)]
[New Thread 0xb2d12b90 (LWP 20701)]
[New Thread 0xb3513b90 (LWP 20700)]
[New Thread 0xb434db90 (LWP 20696)]
[New Thread 0xb4fbab90 (LWP 20695)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 201924

Thread 1 (Thread 0xb68c3740 (LWP 20691))

  • #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 g_type_check_value_holds
    from /usr/lib/libgobject-2.0.so.0
  • #7 gst_value_get_fraction_numerator
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall 




----------- .xsession-errors (2219 sec old) ---------------------
(gnome-www-browser:18487): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gnome-www-browser:18487): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(gnome-www-browser:18487): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: evolution_new_mail_callback() takes at most 2 arguments (3 given)
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in maybe_handle_message
    self._handler(*args, **kwargs)
TypeError: evolution_new_mail_callback() takes at most 2 arguments (3 given)
--------------------------------------------------
Comment 1 Philip Withnall 2008-07-02 19:18:22 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 426990 ***