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 447693 - crash in Music Player: nada solo la instale y ...
crash in Music Player: nada solo la instale y ...
Status: RESOLVED DUPLICATE of bug 350304
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-14 21:43 UTC by sk8_philippe
Modified: 2007-06-15 08:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description sk8_philippe 2007-06-14 21:43:08 UTC
What were you doing when the application crashed?
nada solo la instale  y me aviso que se colgo y que instalara el bug buddy.lo cual ya hice.adios


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 82624512 vsize: 0 resident: 82624512 share: 0 rss: 15093760 rss_rlim: 0
CPU usage: start_time: 1181943387 rtime: 0 utime: 26 stime: 0 cutime:24 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208998192 (LWP 5013)]
[New Thread -1242993776 (LWP 5026)]
[New Thread -1232503920 (LWP 5025)]
[New Thread -1222014064 (LWP 5024)]
[New Thread -1211524208 (LWP 5023)]
(no debugging symbols found)
0x00815402 in __kernel_vsyscall ()

Thread 1 (Thread -1208998192 (LWP 5013))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 rhythmdb_query_deserialize
  • #10 rhythmdb_query_deserialize
  • #11 rb_playlist_source_new_from_xml
  • #12 rb_playlist_manager_load_playlists
  • #13 idle_handle_load_complete
  • #14 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
vo = (null) ao = (null)
Using match: type='signal',interface='com.gnome.mplayer'
Proxy connections and Command connected
Spawn succeeded for filename /mnt/windows/depeche mode & others/D-M/(Depeche Mode) 04-It's No Good.mp3
Spawn succeeded for filename /mnt/windows/depeche mode & others/D-M/but not nigth.mp3
Spawn succeeded for filename /mnt/windows/depeche mode & others/D-M/(Depeche Mode) 04-Halo.mp3
error getting update info:  Cannot open/read repomd.xml file for repository: livna
RhythmDB-ERROR **: file rhythmdb.c: line 1846 (rhythmdb_query_deserialize): should not be reached
aborting...
RhythmDB-ERROR **: file rhythmdb.c: line 1846 (rhythmdb_query_deserialize): should not be reached
aborting...
** (bug-buddy:5029): WARNING **: No se pudo cargar el icono para Abrir carpeta
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-15 08:48:51 UTC
This indicates you've previously used a newer version of rhythmbox, and the version you're using now doesn't support an automatic playlist query element that you were using with the newer version.  Removing ~/.gnome2/rhythmbox/playlists.xml will at least make the older version work.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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