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 511267 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 426990
Product: totem
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-01-22 14:49 UTC by kilroydacat
Modified: 2008-01-22 16:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description kilroydacat 2008-01-22 14:49:31 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Kreski-Lines

Memory status: size: 182423552 vsize: 182423552 resident: 70631424 share: 14303232 rss: 70631424 rss_rlim: 4294967295
CPU usage: start_time: 1200994413 rtime: 11414 utime: 10994 stime: 420 cutime:1 cstime: 7 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 0xb6d676b0 (LWP 17380)]
[New Thread 0xb2dffb90 (LWP 17393)]
[New Thread 0xb35ffb90 (LWP 17392)]
[New Thread 0xb3dffb90 (LWP 17391)]
[New Thread 0xb4990b90 (LWP 17390)]
[New Thread 0xb5199b90 (LWP 17389)]
[New Thread 0xb5ebdb90 (LWP 17388)]
[New Thread 0xb6a2bb90 (LWP 17382)]
(no debugging symbols found)
0xb71f5321 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6d676b0 (LWP 17380))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_type_check_value_holds
    from /usr/lib/libgobject-2.0.so.0
  • #6 gst_value_get_fraction_denominator
    from /usr/lib/libgstreamer-0.10.so.0
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (277625 sec old) ---------------------
08-01-18 22:26:31 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:26:31 (WARNING): cannot parse Alternate-Location date: 2008-01-16T21:37Z%2C 
08-01-18 22:27:32 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:27:32 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:27:32 (WARNING): cannot parse Alternate-Location date: 2008-01-16T21:37Z%2C 
08-01-18 22:28:33 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:28:33 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:28:33 (WARNING): cannot parse Alternate-Location date: 2008-01-16T21:37Z%2C 
08-01-18 22:29:34 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:29:34 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:29:34 (WARNING): cannot parse Alternate-Location date: 2008-01-16T21:37Z%2C 
08-01-18 22:30:35 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:30:35 (WARNING): cannot parse Alternate-Location date: 2008-01-15T16:00Z%2C 
08-01-18 22:30:35 (WARNING): cannot parse Alternate-Location date: 2008-01-16T
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-22 16:45:51 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 ***