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 509706 - crash in Movie Player: just i was about to watc...
crash in Movie Player: just i was about to watc...
Status: RESOLVED DUPLICATE of bug 368224
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-15 17:34 UTC by basheer_n90
Modified: 2008-01-15 19:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description basheer_n90 2008-01-15 17:34:08 UTC
Version: 2.18.3

What were you doing when the application crashed?
just i was about to watch movie.................



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

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

Memory status: size: 498020352 vsize: 498020352 resident: 30932992 share: 13840384 rss: 30932992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200375022 rtime: 51 utime: 40 stime: 11 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496360160 (LWP 3610)]
[New Thread 1157658960 (LWP 3622)]
[New Thread 1147169104 (LWP 3617)]
[New Thread 1136679248 (LWP 3616)]
[New Thread 1126189392 (LWP 3615)]
[New Thread 1115699536 (LWP 3614)]
[New Thread 1105209680 (LWP 3613)]
[New Thread 1094719824 (LWP 3612)]
[New Thread 1084229968 (LWP 3611)]
(no debugging symbols found)
0x0000003f8c8c7956 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1157658960 (LWP 3622))

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


----------- .xsession-errors (93 sec old) ---------------------
localuser:basheer being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3256
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x36001ef (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-15 19:56:44 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://www.gnome.org/projects/totem/#bugs for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Philip Withnall 2008-01-15 19:58:03 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 368224 ***