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 311723 - crash when selecting iPod
crash when selecting iPod
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 312733 328131 329843 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-07-27 13:03 UTC by Mikel Ward
Modified: 2006-02-04 00:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mikel Ward 2005-07-27 13:03:25 UTC
Distribution: Ubuntu 5.10 (breezy)
Package: rhythmbox
Severity: Normal
Version: GNOME2.11.90 unspecified
Gnome-Distributor: Ubuntu
Synopsis: crash when selecting iPod
Bugzilla-Product: rhythmbox
Bugzilla-Component: General
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.11.1)
Description:
I tried to connect my iPod shuffle to my Ubuntu Linux system for the
first time today.  I mounted the device as a vfat partition on
/media/ipod, ensured HAL was running, then started Rhythmbox.  I clicked
on the iPod item in the library and Rhythmbox crashed.



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224533632 (LWP 5029)]
[New Thread -1234367568 (LWP 5040)]
[New Thread -1225974864 (LWP 5039)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224533632 (LWP 5029))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 g_malloc
    from /usr/lib/libglib-2.0.so.0
  • #7 rhythmdb_entry_ipod_get_type
  • #8 rhythmdb_entry_ipod_get_type
  • #9 ipod_get_next_item
  • #10 rb_ipod_source_new
  • #11 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@gnome.bugs 2005-07-27 13:03 UTC -------

Comment 1 Teppo Turtiainen 2005-08-06 08:37:07 UTC
*** Bug 312733 has been marked as a duplicate of this bug. ***
Comment 2 James "Doc" Livingston 2005-08-08 08:57:41 UTC
Can you run Rhythmbox from a terminal, and copy any messages that it prints out
before it crashes? If it doesn't print any messages, can you run "rhythmbox -d"
from a terminal and copy the last 15 or so lines from it's output
Comment 3 Mikel Ward 2005-08-08 14:52:45 UTC
After an upgrade to latest Breezy and a reboot, I can browse the contents of the
iPod playlist, but double clicking on an item in the list causes a crash.

This now looks like a different issue.

The console output is:
(rhythmbox:9658): GStreamer-CRITICAL **: gst_element_make_from_uri: assertion
`gst_uri_is_valid (uri)' failed

(rhythmbox:9658): GLib-CRITICAL **: g_error_new_literal: assertion `domain != 0'
failed
zsh: segmentation fault  rhythmbox
Comment 4 Mikel Ward 2005-08-08 14:57:42 UTC
Here's the backtrace for what it's worth.  I'll try searching for related bugs
etc tomorrow.

  • #0 rb_player_error_quark
  • #1 gst_marshal_VOID__OBJECT_BOXED_STRING
    from /usr/lib/libgstreamer-0.8.so.1
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #3 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #6 gst_element_error_full
    from /usr/lib/libgstreamer-0.8.so.1
  • #7 gst_play_base_bin_get_type
    from /usr/lib/gstreamer-0.8/libgstplaybin.so
  • #8 ??
    from /usr/lib/gstreamer-0.8/libgstplaybin.so
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgstreamer-0.8.so.1
  • #12 ??
    from /usr/lib/libgstreamer-0.8.so.1
  • #13 ??
  • #14 _gst_buffer_type
    from /usr/lib/libgstreamer-0.8.so.1
  • #15 ??
  • #16 ??
    from /usr/lib/libgstreamer-0.8.so.1
  • #17 ??
    from /usr/lib/gstreamer-0.8/libgstplaybin.so
  • #18 ??
  • #19 ??
  • #20 gst_element_set_state
    from /usr/lib/libgstreamer-0.8.so.1
  • #21 gst_element_set_state
    from /usr/lib/libgstreamer-0.8.so.1
  • #22 gst_element_set_state
    from /usr/lib/libgstreamer-0.8.so.1
  • #23 rb_player_new
  • #24 rb_player_open
  • #25 rb_shell_player_set_playing_source
  • #26 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 rb_entry_view_have_selection
  • #32 _gtk_marshal_VOID__BOXED_OBJECT
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #37 gtk_tree_view_row_activated
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #45 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 init_rb_tree_dnd_data
  • #48 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #52 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #53 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #56 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #57 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #58 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #59 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #60 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #61 main

Comment 5 James "Doc" Livingston 2005-08-08 16:16:20 UTC
I don't suppose you could run rhythmbox under gdb, using --g-fatal-warnings, and
get a backtrace of where it stops? (on the gst_element_make_from_uri error)

If you know how, going up a coupel of levels and finding out the uri that it's
dying on would be very helpful too.
Comment 6 Xavier Lacroze 2005-08-20 21:28:31 UTC
I am experiencing the same problem... i've been playing a bit the sources
(ubuntu breezy) and it seems the uri is malformed: it lacks the file:// protocol
Comment 7 James "Doc" Livingston 2005-08-21 09:37:27 UTC
Ah, if "file://" being missing is the problem, then it will probably be fixed in
the latest patch on bug 156783.
Comment 8 Luca Ognibene 2005-09-11 08:54:58 UTC
With the latest version of Rhythmbox in Ubuntu Breezy rhythmbox doesn't crash
anymore but can't play files. The error is "No URI handler implemented for
/media/ipod/...." (I can't copy&paste the error).

Btw, bug 156783 doesn't have patches...
Comment 9 James "Doc" Livingston 2005-09-11 09:15:10 UTC
Erm, that was the wrong bug number - the patches on bug 310017 should fix that
probem.
Comment 10 Luca Ognibene 2005-09-18 09:45:43 UTC
yes, it fixed it! Ubuntu packages now works fine for me! Should we close the bug?
Comment 11 James "Doc" Livingston 2006-01-22 07:52:14 UTC
*** Bug 328131 has been marked as a duplicate of this bug. ***
Comment 12 James "Doc" Livingston 2006-02-04 00:56:14 UTC
*** Bug 329843 has been marked as a duplicate of this bug. ***