GNOME Bugzilla – Bug 362836
crash in Movie Player: tentando ver um vídeo em...
Last modified: 2006-10-27 15:26:57 UTC
Version: 2.16.2 What were you doing when the application crashed? tentando ver um vídeo em www.break.com Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 139345920 vsize: 0 resident: 139345920 share: 0 rss: 30298112 rss_rlim: 0 CPU usage: start_time: 1161087138 rtime: 0 utime: 136 stime: 0 cutime:128 cstime: 0 timeout: 8 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 -1225328976 (LWP 10366)] [New Thread -1330144352 (LWP 10385)] [New Thread -1314468960 (LWP 10384)] [New Thread -1306076256 (LWP 10383)] [New Thread -1295795296 (LWP 10382)] [New Thread -1283302496 (LWP 10381)] [New Thread -1274639456 (LWP 10380)] [New Thread -1266246752 (LWP 10377)] [New Thread -1249723488 (LWP 10376)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 76774
Thread 5 (Thread -1295795296 (LWP 10382))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
ebby, NEEDINFO as per last comment.
i didn't get it
ebby, if you ask for more information, then please also set the status of the bug report to NEEDINFO. :-) please also take a look at the triage guide at http://live.gnome.org/Bugsquad/TriageGuide/ . thanks in advance, any new bug triagers are welcome. :-)
thanks for correcting .
can u pls guide on how to change the status of the bug report . ( i thot i didn't hav permissions .)
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 ***