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 511442 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 367826
Product: totem
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-01-23 04:12 UTC by wangjuefu
Modified: 2008-01-23 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description wangjuefu 2008-01-23 04:12:54 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 161153024 vsize: 161153024 resident: 41213952 share: 22224896 rss: 41213952 rss_rlim: 4294967295
CPU usage: start_time: 1201057848 rtime: 112 utime: 92 stime: 20 cutime:0 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208650016 (LWP 3905)]
[New Thread -1324786800 (LWP 3913)]
[New Thread -1306174576 (LWP 3912)]
[New Thread -1295684720 (LWP 3911)]
[New Thread -1283306608 (LWP 3910)]
[New Thread -1268716656 (LWP 3909)]
[New Thread -1258226800 (LWP 3908)]
[New Thread -1247736944 (LWP 3907)]
[New Thread -1233007728 (LWP 3906)]
(no debugging symbols found)
0x009a6402 in __kernel_vsyscall ()

Thread 2 (Thread -1324786800 (LWP 3913))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 vcdinfo_get_area_selection
    from /usr/lib/libvcdinfo.so.0
  • #5 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_inp_vcd.so
  • #6 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_inp_vcd.so
  • #7 ??
    from /usr/lib/libxine.so.1
  • #8 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_dmx_mpeg_block.so
  • #9 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_dmx_mpeg_block.so
  • #10 ??
    from /usr/lib/libxine.so.1
  • #11 start_thread
    from /lib/libpthread.so.0
  • #12 clone
    from /lib/libc.so.6


----------- .xsession-errors ---------------------
(totem:3682): Gtk-WARNING **: Attempting to add `vcd:///dev/sr0@P1' to the list of recently used resources, but not MIME type was defined
AFD changed from -2 to -1
(totem:3716): Gtk-WARNING **: Attempting to add `vcd:///dev/sr0@P1' to the list of recently used resources, but not MIME type was defined
AFD changed from -2 to -1
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200001 (tvtime)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
/usr/sbin/pirut:53: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid inside an entity name
  gtk.main_iteration()
/usr/sbin/pirut:417: GtkWarning: Failed to set text from markup due to error parsing markup: Error on line 1: Character ' ' is not valid inside an entity name
  gtk.main()
(totem:3905): Gtk-WARNING **: Attempting to add `vcd:///dev/sr0@P1' to the list of recently used resources, but not MIME type was defined
AFD changed from -2 to -1
--------------------------------------------------
Comment 1 Baptiste Mille-Mathias 2008-01-23 16:41:10 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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