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 365361 - crash in Movie Player: Opening a wmv file
crash in Movie Player: Opening 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-10-26 17:39 UTC by doug
Modified: 2006-10-27 15:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description doug 2006-10-26 17:39:33 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Opening 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: 131665920 vsize: 0 resident: 131665920 share: 0 rss: 29302784 rss_rlim: 0
CPU usage: start_time: 1161884353 rtime: 0 utime: 85 stime: 0 cutime:76 cstime: 0 timeout: 9 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 -1226099024 (LWP 1602)]
[New Thread -1325487200 (LWP 1614)]
[New Thread -1309627488 (LWP 1613)]
[New Thread -1301234784 (LWP 1612)]
[New Thread -1290953824 (LWP 1611)]
[New Thread -1278461024 (LWP 1610)]
[New Thread -1269797984 (LWP 1609)]
[New Thread -1261368416 (LWP 1606)]
[New Thread -1244996704 (LWP 1604)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78497

Thread 5 (Thread -1290953824 (LWP 1611))

  • #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-10-27 15:25:27 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 ***