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 401501 - crash in Rhythmbox Music Player: nothing, i have yum runn...
crash in Rhythmbox Music Player: nothing, i have yum runn...
Status: RESOLVED DUPLICATE of bug 356485
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-27 23:08 UTC by jareduarunorudu
Modified: 2007-01-30 09:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jareduarunorudu 2007-01-27 23:08:42 UTC 
What were you doing when the application crashed?
nothing, i have yum running, firefox open, all i did was switch to music player and go to properties and clicked it. (was attempting to find out why it could not find gstreamer plugins to decode MP3 files)


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 395051008 vsize: 395051008 resident: 21118976 share: 13283328 rss: 21118976 rss_rlim: -1
CPU usage: start_time: 1169895123 rtime: 164 utime: 146 stime: 18 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496436288 (LWP 3740)]
[New Thread 1115699520 (LWP 3752)]
(no debugging symbols found)
0x00000034fe60d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 105805

Thread 1 (Thread 46912496436288 (LWP 3740))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 rb_source_set_pixbuf
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 gtk_widget_get_action
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #18 gtk_widget_activate
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 gtk_menu_shell_activate_item
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 gtk_menu_shell_append
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #26 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 gdk_add_client_message_filter
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #30 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #31 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #33 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #34 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Alex Lancaster





          2007-01-30 09:26:23 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This is most likely fixed in the 0.9.7 update now available for FC-6.

*** This bug has been marked as a duplicate of 356485 ***