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 597469 - crash in Movie Player: playing dvd
crash in Movie Player: playing dvd
Status: RESOLVED DUPLICATE of bug 426990
Product: totem
Classification: Core
Component: general
2.26.x
Other All
: Normal critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-10-05 20:09 UTC by djpencho
Modified: 2009-10-05 22:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description djpencho 2009-10-05 20:09:34 UTC
Version: 2.26.2

What were you doing when the application crashed?
playing dvd


Distribution: Debian lenny/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-1-686 #1 SMP Mon Aug 3 16:18:30 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAquaIsh
Icon Theme: yasis
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 251183104 vsize: 251183104 resident: 66187264 share: 18767872 rss: 66187264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254773264 rtime: 1156 utime: 1064 stime: 92 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb695a720 (LWP 25310)]
[New Thread 0xaac02b90 (LWP 25330)]
[New Thread 0xac017b90 (LWP 25329)]
[New Thread 0xb0c41b90 (LWP 25328)]
[New Thread 0xb1996b90 (LWP 25322)]
[New Thread 0xb2dbab90 (LWP 25321)]
[New Thread 0xb3a6cb90 (LWP 25320)]
[New Thread 0xb44e1b90 (LWP 25316)]
0xb7ff5424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb695a720 (LWP 25310))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__g_type_check_value_holds
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/gobject/gtype.c line 3827
  • #7 gst_value_get_fraction_numerator
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 ??
  • #0 __kernel_vsyscall


---- Critical and fatal warnings logged during execution ----

** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 
Output of custom script "/usr/lib/totem/gstreamer/totem/totem-bugreport.py":
gst-typefind-0.10 version 0.10.24
GStreamer 0.10.24
http://packages.qa.debian.org/gstreamer0.10
Listened to a "mpegversion=(int)2" file on 2009-10-05T22:06:27




----------- .xsession-errors (25051 sec old) ---------------------
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:5006): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-10-05 22:51:36 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 bug 426990 ***