Bug 390546 – crash in Rhythmbox Music Player: Nothing

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 390546 - crash in Rhythmbox Music Player: Nothing


Summary:	crash in Rhythmbox Music Player: Nothing


Status:	RESOLVED DUPLICATE of bug 350304

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-29 03:09 UTC by Felipe Contreras (banned)
Modified:	2006-12-29 04:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Felipe Contreras (banned) 2006-12-29 03:09:18 UTC

What were you doing when the application crashed?
Nothing


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors ---------------------
Auto resize true
Auto resize true
Auto resize true
Auto resize true
Auto resize true
Auto resize true
Auto resize true
Tracker: no "peers" field
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1006036 (Billboard ); these messages lack timestamps and therefore suck.
RhythmDB-ERROR **: file rhythmdb-tree.c: line 248 (rhythmdb_tree_parser_start_element): should not be reached
aborting...
Xlib: unexpected async reply (sequence 0x2400)!
** (bug-buddy:15752): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 61308928 vsize: 0 resident: 61308928 share: 0 rss: 23060480 rss_rlim: 0
CPU usage: start_time: 1167361693 rtime: 0 utime: 149 stime: 0 cutime:91 cstime: 0 timeout: 58 it_real_value: 0 frequency: 4

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 -1208240416 (LWP 15746)]
[New Thread -1220375664 (LWP 15750)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 97692

Thread 2 (Thread -1220375664 (LWP 15750))

#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 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 Felipe Contreras (banned) 2006-12-29 03:45:11 UTC

I don't know if this is really a bug, but it seems since I installed the latest rhythmbox (0.9.7) from source I can't use the old one (0.9.5), GConf schemas?

Anyway, it would be great if there was a way to have the new schemas installed somewhere so if I don't like 0.9.7 I could go back to 0.9.5, the one on my distro.

Comment 2 Alex Lancaster 2006-12-29 04:21:31 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 bug has been marked as a duplicate of 350304 ***