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 517970 - crash in Movie Player: trying to open a .wmv mo...
crash in Movie Player: trying to open a .wmv mo...
Status: RESOLVED DUPLICATE of bug 509753
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-02-21 23:20 UTC by Mauricio Vieira
Modified: 2008-02-21 23:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Mauricio Vieira 2008-02-21 23:20:07 UTC 
Version: 2.20.3

What were you doing when the application crashed?
trying to open a .wmv movie attached in a email readed by thunderbird


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 40882176 vsize: 40882176 resident: 19664896 share: 13148160 rss: 19664896 rss_rlim: 4294967295
CPU usage: start_time: 1203635821 rtime: 54 utime: 47 stime: 7 cutime:2 cstime: 2 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 0xb6cd96b0 (LWP 30483)]
[New Thread 0xb6691b90 (LWP 30485)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 190031

Thread 1 (Thread 0xb6cd96b0 (LWP 30483))

  • #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 strncpy
    from /lib/i686/cmov/libc.so.6
  • #7 ??
    from /usr/lib/gstreamer-0.10/libgstbluetooth.so
  • #8 ??
  • #9 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (3322 sec old) ---------------------
EXEC: seahorse-tool --encrypt 'file:///home/vieira/dinheiro/pagamentos%20notebook/pagamentoNotebook.ods'
** (process:19022): WARNING **: can't lock memory: Cannot allocate memory
WARNING: not using secure memory for passwords
** (seahorse-tool:19022): WARNING **: couldn't load all the keys (1/2) from GPGME
** (process:19039): WARNING **: can't lock memory: Cannot allocate memory
WARNING: not using secure memory for passwords
(gnome-terminal:20712): Vte-WARNING **: Nenhum manipulador foi definido para a seqüência de controle "device-control-string".
(gnome-terminal:20712): Vte-WARNING **: Nenhum manipulador foi definido para a seqüência de controle "device-control-string".
(gnome-terminal:20712): Vte-WARNING **: Nenhum manipulador foi definido para a seqüência de controle "device-control-string".
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-21 23:33:23 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 509753 ***