Bug 474636 – 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 474636 - 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-09-07 18:49 UTC by xneox
Modified:	2007-09-09 05:02 UTC

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

Description xneox 2007-09-07 18:49:13 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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000001
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 109600768 vsize: 109600768 resident: 30146560 share: 18210816 rss: 30146560 rss_rlim: 4294967295
CPU usage: start_time: 1189190881 rtime: 385 utime: 332 stime: 53 cutime:2 cstime: 0 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 -1209009616 (LWP 3583)]
[New Thread -1269118064 (LWP 3597)]
[New Thread -1258292336 (LWP 3591)]
[New Thread -1246758000 (LWP 3587)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 161172

Thread 2 (Thread -1269118064 (LWP 3597))

#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 ---------------------
(gnome_segv:3598): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(gnome_segv:3598): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
(bug-buddy:3599): Gdk-WARNING **: Mask is 0 in visual. Server bug ?
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-09-09 05:02:28 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 434003 ***