Bug 469906 – crash in Rhythmbox Music Player: 添加歌曲，不见歌曲显示就崩溃了

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 469906 - crash in Rhythmbox Music Player: 添加歌曲，不见歌曲显示就崩溃了


Summary:	crash in Rhythmbox Music Player: 添加歌曲，不见歌曲显示就崩溃了


Status:	RESOLVED DUPLICATE of bug 434003

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-24 14:11 UTC by camwind
Modified:	2007-08-27 12:29 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description camwind 2007-08-24 14:11:20 UTC

What were you doing when the application crashed?
添加歌曲，不见歌曲显示就崩溃了


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 189562880 vsize: 189562880 resident: 32432128 share: 19308544 rss: 32432128 rss_rlim: 4294967295
CPU usage: start_time: 1187993044 rtime: 2234 utime: 2009 stime: 225 cutime:16 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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 -1208948176 (LWP 2802)]
[New Thread -1410364528 (LWP 2878)]
[New Thread -1314129008 (LWP 2860)]
[New Thread -1357915248 (LWP 2857)]
[New Thread -1303245936 (LWP 2808)]
(no debugging symbols found)
0x00dd6402 in __kernel_vsyscall ()

+ Trace 157597

Thread 2 (Thread -1410364528 (LWP 2878))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
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 ??
from /lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
from /usr/lib/libgnomevfs-2.so.0
#13 ??
#14 ??
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 ??
#22 ??
from /lib/libglib-2.0.so.0



----------- .xsession-errors (1797 sec old) ---------------------
EvaAgentUploader::slotWriteReady
received new message
IM: seq: 899468 ----- msg seq: 880
Unknow IM Type: 0x1e
sender: 10000, receiver: 85005776, sender IP: 219.133.49.181, sender port: 8000
version:0x 100, command: 0x  17, sequence: 0x 370
after InPacket headr(7(UDP) or 9(TCP) bytes) plus ReceiveIMPacket header(20 bytes):
0:  0  0 27 10  5 11 15 d0 
8:  0  d b9 8c db 85 31 b5 
16: 1f 40  0 1e  7 2f 6f 34 
24: 51 c4  5  1 10  c  0  0 
32:  0  0  0  0  0  0  0  0 
40:
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-08-27 12:29:51 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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