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 531234 - crash in Movie Player: Playing DVD and then pre...
crash in Movie Player: Playing DVD and then pre...
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-05-03 15:40 UTC by hockchui.goh
Modified: 2008-05-03 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description hockchui.goh 2008-05-03 15:40:44 UTC 
Version: 2.22.1

What were you doing when the application crashed?
Playing DVD and then press 'F' key


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

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 188329984 vsize: 188329984 resident: 96010240 share: 16867328 rss: 96010240 rss_rlim: 4294967295
CPU usage: start_time: 1209828961 rtime: 17931 utime: 17307 stime: 624 cutime:1 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 0xb68b8740 (LWP 7879)]
[New Thread 0xb1e28b90 (LWP 7969)]
[New Thread 0xb45d8b90 (LWP 7968)]
[New Thread 0xb571fb90 (LWP 7967)]
[New Thread 0xb04ffb90 (LWP 7966)]
[New Thread 0xb264eb90 (LWP 7965)]
[New Thread 0xb2ea2b90 (LWP 7964)]
[New Thread 0xb3d67b90 (LWP 7963)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 196777

Thread 1 (Thread 0xb68b8740 (LWP 7879))

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




----------- .xsession-errors (4424 sec old) ---------------------
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
** (gnome-cups-icon:3767): WARNING **: IPP request failed with status 1280
** (gnome-cups-icon:3767): WARNING **: IPP request failed with status 1280
Initializing gnome-mount extension
seahorse nautilus module initialized
** (gnome-cups-icon:3767): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted.
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (3075761200) is greater than comparison timestamp (2939522521).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x3200003 (Software U) appears to be one of the offending windows with a timestamp of 3075761200.  Working around...
current dist not found in meta-release file
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-03 15:49:25 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 ***