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 436973 - crash in Rhythmbox Music Player: I just started it.
crash in Rhythmbox Music Player: I just started it.
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-05-08 18:42 UTC by m.matze
Modified: 2007-05-08 21:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description m.matze 2007-05-08 18:42:58 UTC 
What were you doing when the application crashed?
I just started it.


Distribution: CentOS release 5 (Final)
Gnome Release: 2.16.0 2007-02-18 (CentOS)
BugBuddy Version: 2.16.0

Memory status: size: 96407552 vsize: 0 resident: 96407552 share: 0 rss: 23695360 rss_rlim: 0
CPU usage: start_time: 1178649719 rtime: 0 utime: 202 stime: 0 cutime:174 cstime: 0 timeout: 28 it_real_value: 0 frequency: 6

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 -1208539424 (LWP 3680)]
[New Thread -1256785008 (LWP 3686)]
(no debugging symbols found)
0x00f18402 in __kernel_vsyscall ()

+ Trace 133128

Thread 2 (Thread -1256785008 (LWP 3686))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 rhythmdb_tree_new
  • #11 xmlParseStartTag
    from /usr/lib/libxml2.so.2
  • #12 xmlParseElement
    from /usr/lib/libxml2.so.2
  • #13 xmlParseDocument
    from /usr/lib/libxml2.so.2
  • #14 rhythmdb_tree_new
  • #15 rhythmdb_load
  • #16 g_thread_create_full
    from /lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6 






Comment 1


Jonathan Matthew





          2007-05-08 21:54:51 UTC
        



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 indicates that you've previously run a more recent version of rhythmbox, and the older version you ran this time did not know how to read the database file written by the newer version.


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