GNOME Bugzilla – Bug 536333
crash in Rhythmbox Music Player: Rien. L'appli crash au d...
Last modified: 2008-06-07 12:14:31 UTC
Version: 0.11.5 What were you doing when the application crashed? Rien. L'appli crash au démarrage. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.4 #1 SMP PREEMPT Sun Jun 1 11:24:27 CEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 500547584 vsize: 500547584 resident: 42835968 share: 20058112 rss: 42835968 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212442620 rtime: 60 utime: 54 stime: 6 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f38710c67a0 (LWP 17219)] [New Thread 0x40b14950 (LWP 17222)] (no debugging symbols found) 0x00007f387034fedf in waitpid () from /lib/libpthread.so.0
+ Trace 199440
Thread 1 (Thread 0x7f38710c67a0 (LWP 17219))
----------- .xsession-errors (483 sec old) --------------------- GetBoundingMetrics (char *) GetBoundingMetrics (char *) GetBoundingMetrics (char *) xEmbed supported in this browser GTK2 supported in this browser GetBoundingMetrics (char *) GetBoundingMetrics (char *) NewStream: The full URL is http://c.liberation.fr/_files/file_315215_134058.swf Forked successfully, child process PID is 16790 Closed 68 files. Starting process: /usr/bin/gtk-gnash -x 41952860 -j 300 -k 250 -u http://c.liberation.fr/_files/file_315215_134058.swf -F 70 -U http://www.liberation.fr/ -P height=250 -P pluginspage=http://www.macrom Shutting down Child process exited with status 15 plugin instance destruction shutting down input chan 0x33743a0 --------------------------------------------------
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 524985 ***