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 336199 - Rhythmbox crashed when accessing newly created playlist
Rhythmbox crashed when accessing newly created playlist
Status: RESOLVED DUPLICATE of bug 338859
Product: rhythmbox
Classification: Other
Component: general
0.9.3
Other other
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-27 14:36 UTC by Francis Provencher
Modified: 2006-04-18 09:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Francis Provencher 2006-03-27 14:36:08 UTC
Distribution: Ubuntu 6.04 (dapper)
Package: rhythmbox
Severity: critical
Version: GNOME2.14.0 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Rhythmbox crashed when accessing newly created playlist
Bugzilla-Product: rhythmbox
Bugzilla-Component: General
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.0)
Description:
Description of the crash:

I created a new playlist called Stellvia. I did a search in the library
and added some files, including one file with UTF-8 in the name (namely
Japanese). When I tried to access that playlist, the file with the
Japanese in the filename didn't show up in the list and Rhythmbox
crashed. 

On my previous attempt, Rhythmbox crashed when I added the files to the
playlist. Upon restart, the new playlist had lost his name.

Steps to reproduce the crash:
1. Create a playlist
2. Do a search in the library and add a file with Japanese in it.
3. Access the playlist

Expected Results:
Rhythmbox crash.

How often does this happen?
It happened to me twice in a row, maybe every time, maybe not.

Additional Information:



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 -1225947456 (LWP 12176)]
[New Thread -1243182160 (LWP 12179)]
[New Thread -1234789456 (LWP 12178)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225947456 (LWP 12176))

  • #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-03-27 14:36 -------

Comment 1 Christian Kirbach 2006-03-27 14:47:07 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

can you please attach an empty file with a name causing this if you can pinpoint it to one=?
Comment 2 Francis Provencher 2006-03-27 14:56:28 UTC
I tried to recreate this bug to see when it was happening: 

Actually, it has nothing to do with Japanese or with adding a file. 

All I have to do is enter a search pattern, then select a playlist and then
Rhythmbox is crashing.

It happened everytime I tried.

I just received your comment, I will try to get one with Debugging symbols.
Comment 3 Alex Lancaster 2006-03-28 07:53:59 UTC
I can't duplicate this with CVS HEAD.  Can you retest against CVS and see if you can reproduce the bug?
Comment 4 James "Doc" Livingston 2006-04-18 09:08:05 UTC

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