GNOME Bugzilla – Bug 493881
crash in Rhythmbox Music Player: Exiting the application ...
Last modified: 2007-11-16 13:22:14 UTC
Version: 0.11.2 What were you doing when the application crashed? Exiting the application from the notification area. It had been playing DI.fm MP3 radio stream through an HTTP web proxy but had stopped playing 30 mins ago (probably due to proxy problem). This was running on latest Solaris build (un-released). Distribution: Solaris Express Community Edition snv_76 X86 Gnome Release: 2.20.0 2007-10-08 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 162861056 vsize: 162861056 resident: 51077120 share: 786432 rss: 51077120 rss_rlim: 0 CPU usage: start_time: 0 rtime: 1404 utime: 12297901 stime: 1749944 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 175519
Thread 1 (LWP 1)
Thread 4 (Thread 488 (LWP 488)): #-1 0xfef022e7 in __pollsys () from /lib/libc.so.1 No symbol table info available. Thread 3 (LWP 488 ): #-1 0xfef022e7 in __pollsys () from /lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfef02897 in _waitid () from /lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfef02897 in _waitid () from /lib/libc.so.1 No symbol table info available. #-1 0xfef02897 in _waitid () from /lib/libc.so.1 ----------- .xsession-errors (19175 sec old) --------------------- /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance! Looks like this might be a gail problem.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 488564 ***