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 539413 - crash in Rhythmbox Music Player: just listening
crash in Rhythmbox Music Player: just listening
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 543950 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-06-21 06:30 UTC by raynus.blueray
Modified: 2010-12-11 12:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description raynus.blueray 2008-06-21 06:30:31 UTC 
Version: 0.11.5

What were you doing when the application crashed?
just listening 


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.7 #1 SMP Mon Jun 16 20:12:25 ICT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Xfce-dusk
Icon Theme: OSX

Memory status: size: 134803456 vsize: 134803456 resident: 37715968 share: 21073920 rss: 37715968 rss_rlim: 4294967295
CPU usage: start_time: 1214025805 rtime: 17476 utime: 17257 stime: 219 cutime:2 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6561960 (LWP 12553)]
[New Thread 0xb11a5b90 (LWP 13489)]
[New Thread 0xb19a6b90 (LWP 13488)]
[New Thread 0xb21a7b90 (LWP 13464)]
[New Thread 0xb31a9b90 (LWP 13463)]
[New Thread 0xb29a8b90 (LWP 13462)]
[New Thread 0xb52cfb90 (LWP 12558)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 200992

Thread 3 (Thread 0xb19a6b90 (LWP 13488))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 stream_src_event_cb
    at rb-player-gst-xfade.c line 1855
  • #7 gst_marshal_BOOLEAN__POINTER
    at gstmarshal.c line 584
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /usr/lib/libglib-2.0.so.0
  • #16 ?? 


----------- .xsession-errors (94519 sec old) ---------------------
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
(geany:3993): Vte-WARNING **: Error reading from child: Bad file descriptor.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2008-07-21 22:04:20 UTC 
*** Bug 543950 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2010-12-11 12:22:31 UTC 
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!