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 369130 - crash in Movie Player: opened a .wmv file
crash in Movie Player: opened a .wmv file
Status: RESOLVED DUPLICATE of bug 364037
Product: totem
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-11-01 23:16 UTC by Paul Benkovitz
Modified: 2006-11-02 14:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Paul Benkovitz 2006-11-01 23:16:11 UTC
Version: 2.16.2

What were you doing when the application crashed?
opened a .wmv file


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 131833856 vsize: 0 resident: 131833856 share: 0 rss: 29949952 rss_rlim: 0
CPU usage: start_time: 1162422844 rtime: 0 utime: 134 stime: 0 cutime:118 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225476432 (LWP 5021)]
[New Thread -1326347360 (LWP 5031)]
[New Thread -1310692448 (LWP 5030)]
[New Thread -1302299744 (LWP 5029)]
[New Thread -1292018784 (LWP 5028)]
[New Thread -1279525984 (LWP 5027)]
[New Thread -1270862944 (LWP 5026)]
[New Thread -1262470240 (LWP 5025)]
[New Thread -1246032992 (LWP 5024)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 5 (Thread -1292018784 (LWP 5028))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??

Comment 1 Fabio Bonelli 2006-11-02 14:19:28 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 364037 ***