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 338835 - Rhythmbox crashes when adding the result of a search in a playlist
Rhythmbox crashes when adding the result of a search in a playlist
Status: RESOLVED DUPLICATE of bug 338859
Product: rhythmbox
Classification: Other
Component: User Interface
unspecified
Other other
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-04-17 23:28 UTC by pierre.maon
Modified: 2006-04-18 06:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description pierre.maon 2006-04-17 23:28:17 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: rhythmbox
Severity: critical
Version: GNOME2.14.0 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Rhythmbox crashes when adding the result of a search in a playlist
Bugzilla-Product: rhythmbox
Bugzilla-Component: User Interface
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.0)
Description:
Description of the crash:
It is impossible to search for a song and then add it to a playlist :
rhythmbox crashes when trying to view the updated content of the
playlist.

Steps to reproduce the crash:
1. search a song in the whole library
2. drag and drop a title from the results to a playlist (in the "source"
view)
3. go to that playlist by clicking on its icon (in the "source" view)
4. rhythmbox crashes

Expected Results:
The playlist should contain the new song.

How often does this happen?
The crash seems to be systematic with the procedure described above.

Additional Information:
I use the ubuntu "dapper" package of rhythbox : 0.9.3.1-0ubuntu3


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)
[Thread debugging using libthread_db enabled]
[New Thread -1226090816 (LWP 5625)]
[New Thread -1250198608 (LWP 5628)]
[New Thread -1241805904 (LWP 5627)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67675

Thread 1 (Thread -1226090816 (LWP 5625))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 rhythmdb_query_model_remove_entry
  • #11 rhythmdb_query_model_signal_complete
  • #12 g_object_set_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #14 rb_static_playlist_source_new
  • #15 rb_static_playlist_source_new
  • #16 rb_source_search
  • #17 rb_source_header_clear_search
  • #18 g_cclosure_marshal_VOID__STRING
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 rb_search_entry_set_text
  • #24 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #29 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-04-17 23:28 -------
Comment 1 James "Doc" Livingston 2006-04-18 06:15:12 UTC 
Thanks for reporting this, it is the same issue as bug 338859, so I'm marking as a duplicate.

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