After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 450620 - crash in Rhythmbox Music Player: Trying to play a music s...
crash in Rhythmbox Music Player: Trying to play a music s...
Status: RESOLVED DUPLICATE of bug 420106
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-24 14:27 UTC by ed.whitcomb
Modified: 2007-06-24 22:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ed.whitcomb 2007-06-24 14:27:06 UTC
What were you doing when the application crashed?
Trying to play a music station.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 223805440 vsize: 223805440 resident: 40845312 share: 25751552 rss: 40845312 rss_rlim: 4294967295
CPU usage: start_time: 1182694494 rtime: 8035 utime: 7368 stime: 667 cutime:14 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209083344 (LWP 2902)]
[New Thread -1388356720 (LWP 2983)]
[New Thread -1367377008 (LWP 2982)]
[New Thread -1250661488 (LWP 2981)]
[New Thread -1271641200 (LWP 2980)]
[New Thread -1377866864 (LWP 2976)]
[New Thread -1261151344 (LWP 2975)]
[New Thread -1325417584 (LWP 2974)]
[New Thread -1356887152 (LWP 2966)]
[New Thread -1335907440 (LWP 2965)]
[New Thread -1304437872 (LWP 2963)]
[New Thread -1293948016 (LWP 2950)]
[New Thread -1283458160 (LWP 2946)]
[New Thread -1314927728 (LWP 2940)]
[New Thread -1250395248 (LWP 2911)]
[New Thread -1238430832 (LWP 2908)]
(no debugging symbols found)
0x00d6a402 in __kernel_vsyscall ()

Thread 3 (Thread -1367377008 (LWP 2982))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/gstreamer-0.10/libgstaudioresample.so
  • #5 ??
    from /usr/lib/gstreamer-0.10/libgstaudioresample.so
  • #6 ??
    from /usr/lib/gstreamer-0.10/libgstaudioresample.so
  • #7 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #8 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #9 gst_pad_set_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #10 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #12 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #13 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 ??
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #16 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 start_thread
    from /lib/libpthread.so.0
  • #20 clone
    from /lib/libc.so.6


----------- .xsession-errors (806 sec old) ---------------------
localuser:edrw being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2580
Loading "installonlyn" plugin
kbuildsycoca running...
Reusing existing ksycoca
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0x3400042 (No Encoder).
Launched ok, pid = 2865
ICE default IO error handler doing an exit(), pid = 2862, errno = 0
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-24 22:46:01 UTC
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 420106 ***