GNOME Bugzilla – Bug 535329
crash in Movie Player: não sei, nem estou aqui!...
Last modified: 2008-05-29 09:41:38 UTC
Version: 2.20.3 What were you doing when the application crashed? não sei, nem estou aqui!! Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 156831744 vsize: 156831744 resident: 70307840 share: 43814912 rss: 70307840 rss_rlim: 4294967295 CPU usage: start_time: 1211990658 rtime: 535 utime: 497 stime: 38 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6c78940 (LWP 20386)] [New Thread 0xb2647b90 (LWP 20394)] [New Thread 0xb2e65b90 (LWP 20393)] [New Thread 0xb3681b90 (LWP 20392)] [New Thread 0xb3efeb90 (LWP 20391)] [New Thread 0xb46ffb90 (LWP 20390)] [New Thread 0xb5485b90 (LWP 20389)] [New Thread 0xb6660b90 (LWP 20388)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 198894
Thread 4 (Thread 0xb3681b90 (LWP 20392))
----------- .xsession-errors (4851 sec old) --------------------- Artwork: Alexis Younes Amaury Amblard-Ladurantie Soundtrack: Matthias Le Bidan Design & Programming: Guillaume Cottenceau Level Editor: Kim and David Joham Originally sponsored by Mandriva <http://www.mandriva.com/> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2, as published by the Free Software Foundation. [SDL Init] [Graphics............] [Sound Init] [Levels] Ready. Addicted for 1h 6s, 1214 bubbles were launched. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 527572 ***