GNOME Bugzilla – Bug 573676
crash in Movie Player: Changing volume while li...
Last modified: 2009-03-01 21:50:44 UTC
Version: 2.22.2 What were you doing when the application crashed? Changing volume while listening to music Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 494370816 vsize: 494370816 resident: 39104512 share: 17051648 rss: 39104512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1235940167 rtime: 225 utime: 210 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0x7f8bb3c3c700 (LWP 4658)] [New Thread 0x44d01950 (LWP 4666)] [New Thread 0x44500950 (LWP 4665)] [New Thread 0x43cff950 (LWP 4664)] [New Thread 0x434fe950 (LWP 4663)] [New Thread 0x42cfd950 (LWP 4661)] [New Thread 0x424fc950 (LWP 4660)] 0x00007f8bad0f6b66 in poll () from /lib/libc.so.6
+ Trace 213034
Thread 5 (Thread 0x434fe950 (LWP 4663))
----------- .xsession-errors (416 sec old) --------------------- Reparsing saved files... Starting batch parsing Parsing stage done (523 total parsed files, 11966 tokens in 0 minute(s), 0.1 seconds). Updating class browser... Class browser updated. Reparsing saved files... Starting batch parsing Parsing stage done (523 total parsed files, 11990 tokens in 0 minute(s), 0.14 seconds). Updating class browser... Class browser updated. Reparsing saved files... Starting batch parsing Parsing stage done (523 total parsed files, 11965 tokens in 0 minute(s), 0.1 seconds). Updating class browser... Class browser updated. Reparsing saved --------------------------------------------------
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 ***