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 384253 - crash in Rhythmbox Music Player: i had been listening to ...
crash in Rhythmbox Music Player: i had been listening to ...
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-10 03:38 UTC by Richard Edmands
Modified: 2006-12-10 04:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Richard Edmands 2006-12-10 03:38:12 UTC
What were you doing when the application crashed?
i had been listening to music, turning the visualizations on and off every once and awhile. removed a bunchload of songs from the filesystem. the crash happened when i went to check the properties of a file (one that was not removed during the deletion, tho, those songs seemed to have been removed from the list automatically anyways).

this is cvs rhythmbox as of changelog revision 1.2434 + latest visualization patch.


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

Memory status: size: 218849280 vsize: 0 resident: 218849280 share: 0 rss: 56741888 rss_rlim: 0
CPU usage: start_time: 1165714098 rtime: 0 utime: 84600 stime: 0 cutime:81566 cstime: 0 timeout: 3034 it_real_value: 0 frequency: 145

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228966224 (LWP 6235)]
[New Thread -1334432864 (LWP 10478)]
[New Thread -1326040160 (LWP 10476)]
[New Thread -1390421088 (LWP 10475)]
[New Thread -1436292192 (LWP 10209)]
[New Thread -1410360416 (LWP 10208)]
[New Thread -1360004192 (LWP 10207)]
[New Thread -1343218784 (LWP 10206)]
[New Thread -1317647456 (LWP 6249)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1228966224 (LWP 6235))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 rb_source_song_properties
    at rb-source.c line 925
  • #5 rb_shell_clipboard_cmd_song_info
    at rb-shell-clipboard.c line 818
  • #6 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #7 IA__g_closure_invoke
    at gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
  • #10 IA__g_signal_emit
    at gsignal.c line 2243
  • #11 _gtk_action_emit_activate
    at gtkaction.c line 835
  • #12 IA__gtk_action_activate
    at gtkaction.c line 862
  • #13 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #14 IA__g_closure_invoke
    at gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #16 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #17 IA__g_signal_emit
    at gsignal.c line 2243
  • #18 IA__gtk_widget_activate
    at gtkwidget.c line 3942
  • #19 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1024
  • #20 gtk_menu_shell_button_release
    at gtkmenushell.c line 630
  • #21 gtk_menu_button_release
    at gtkmenu.c line 2619
  • #22 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #23 g_type_class_meta_marshal
    at gclosure.c line 567
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #27 IA__g_signal_emit
    at gsignal.c line 2243
  • #28 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #29 IA__gtk_propagate_event
    at gtkmain.c line 2211
  • #30 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #31 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #32 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #33 g_main_context_iterate
    at gmain.c line 2677
  • #34 IA__g_main_loop_run
    at gmain.c line 2881
  • #35 IA__gtk_main
    at gtkmain.c line 1024
  • #36 main
    at main.c line 382
  • #0 __kernel_vsyscall

Comment 1 James "Doc" Livingston 2006-12-10 04:14:30 UTC
It looks like the RBShellClipboard thinks the current source is NULL, causing the above. I'm fairly certain that rb_shell_clipboard_set_source should never be passed NULL.
Comment 2 Jonathan Matthew 2006-12-10 04:36:36 UTC
Fixed in the latest visualisation patch.