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 410338 - rhythmbox crashed when trying to rename ipod-name
rhythmbox crashed when trying to rename ipod-name
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: Plugins (other)
0.9.7
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-21 10:54 UTC by Sebastien Bacher
Modified: 2007-02-21 11:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2007-02-21 10:54:12 UTC
That bug has been opened on https://launchpad.net/bugs/86605

"Binary package hint: rhythmbox

In 'Source' dialog, right click on ipod, select 'Rename'. After that rhytmbox crashes.
...
Package: rhythmbox 0.9.7.90-0ubuntu1
...
"

Debug backtrace for the crash:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `rhythmbox'.
Program terminated with signal 11, Segmentation fault.
  • #0 rb_tray_icon_drop_cb
    at rb-tray-icon.c line 514
  • #0 rb_tray_icon_drop_cb
    at rb-tray-icon.c line 514
  • #1 rb_tray_icon_notify
    at rb-tray-icon.c line 679
  • #2 ??
  • #3 ??

Comment 1 Sebastien Bacher 2007-02-21 10:57:54 UTC
Doing those actions rhythmbox crashes on my feisty desktop, the backtrace is different though, do you want an another bug about that?

Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 16993)

  • #0 rb_sourcelist_visible_source_to_iter
    at rb-sourcelist.c line 543
  • #1 rb_sourcelist_edit_source_name
    at rb-sourcelist.c line 563
  • #2 rb_ipod_plugin_cmd_rename
    at rb-ipod-plugin.c line 244
  • #3 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #4 IA__g_closure_invoke
    at gclosure.c line 490
  • #5 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #6 IA__g_signal_emit_valist
  • #7 IA__g_signal_emit
    at gsignal.c line 2243
  • #8 _gtk_action_emit_activate
    at gtkaction.c line 835

Comment 2 James "Doc" Livingston 2007-02-21 11:18:52 UTC
The first stack trace appears badly damaged. I've just fixed the cause of the second trace in SVN (just got in for 0.9.8).

I could easily reproduce the second trace, and the first one is probably the same crasher. Marking FIXED unless someone can cause it to crash with an undamaged stack trace different from the second.