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 384764 - crash in Movie Player:
crash in Movie Player:
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-12-11 17:30 UTC by felipe.lloyd
Modified: 2006-12-11 18:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description felipe.lloyd 2006-12-11 17:30:40 UTC 
Version: 2.16.2

What were you doing when the application crashed?



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

Memory status: size: 165343232 vsize: 0 resident: 165343232 share: 0 rss: 45133824 rss_rlim: 0
CPU usage: start_time: 1165857209 rtime: 0 utime: 16886 stime: 0 cutime:16594 cstime: 0 timeout: 292 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 -1225775440 (LWP 18419)]
[New Thread -1360004192 (LWP 18850)]
[New Thread -1329415264 (LWP 18434)]
[New Thread -1321022560 (LWP 18432)]
[New Thread -1310741600 (LWP 18431)]
[New Thread -1298248800 (LWP 18430)]
[New Thread -1289585760 (LWP 18429)]
[New Thread -1281156192 (LWP 18426)]
[New Thread -1264776288 (LWP 18425)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93323

Thread 5 (Thread -1310741600 (LWP 18431))

  • #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


palfrey





          2006-12-11 18:34:26 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://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 364037 ***