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 378223 - crash in Rhythmbox Music Player: Browsing the internet wi...
crash in Rhythmbox Music Player: Browsing the internet wi...
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-22 19:51 UTC by mark_harvey_121
Modified: 2007-10-30 01:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description mark_harvey_121 2006-11-22 19:51:52 UTC
What were you doing when the application crashed?
Browsing the internet with Firefox 2.0. The playlist had run to the end, but had been set on repeat. The crash happened after the playlist had finished the last track. Rhythmbox was minimized in the background


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 256135168 vsize: 256135168 resident: 38424576 share: 17252352 rss: 38424576 rss_rlim: -1
CPU usage: start_time: 1164218366 rtime: 19899 utime: 18802 stime: 1097 cutime:8 cstime: 7 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 47780528243680 (LWP 17580)]
[New Thread 1107310928 (LWP 20765)]
[New Thread 1132489040 (LWP 20761)]
[New Thread 1082132816 (LWP 18943)]
[New Thread 1090525520 (LWP 18942)]
[New Thread 1098918224 (LWP 17593)]
(no debugging symbols found)
0x00002b74c08cbeef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47780528243680 (LWP 17580))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 rb_sourcelist_select
  • #9 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #13 rb_shell_player_set_playing_source
  • #14 rb_shell_player_do_next
  • #15 rb_shell_player_do_next
  • #16 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #20 rb_player_gst_new
  • #21 gst_bus_pop
    from /usr/lib64/libgstreamer-0.10.so.0
  • #22 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #23 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Alex Lancaster 2006-11-23 00:26:30 UTC
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 346800 ***
Comment 2 Jonathan Matthew 2006-11-23 02:06:53 UTC
This doesn't look anything like bug 346800, and the reporter almost certainly has a version of gtk including the temporary fix for that bug.
Comment 3 James "Doc" Livingston 2007-02-06 11:08:36 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. Thanks in advance!
Comment 4 André Klapper 2007-10-30 01:42:01 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!