Bug 492110 – 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 492110 - crash in Rhythmbox Music Player: Nothing


Summary:	crash in Rhythmbox Music Player: Nothing


Status:	RESOLVED DUPLICATE of bug 434996

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-31 14:39 UTC by gfeiden
Modified:	2007-10-31 22:44 UTC

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

Description gfeiden 2007-10-31 14:39:45 UTC

Version: 0.10.1

What were you doing when the application crashed?
Nothing



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Oxygen-Refit

Memory status: size: 685465600 vsize: 685465600 resident: 70225920 share: 25382912 rss: 70225920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193841219 rtime: 2136 utime: 1850 stime: 286 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496392112 (LWP 11802)]
[New Thread 1105209680 (LWP 11829)]
[New Thread 1084229968 (LWP 11828)]
[New Thread 1094719824 (LWP 11807)]
(no debugging symbols found)
0x00000038d70c82e6 in poll () from /lib64/libc.so.6

+ Trace 174183

Thread 3 (Thread 1084229968 (LWP 11828))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 g_object_set_valist
from /lib64/libgobject-2.0.so.0
#5 g_object_set
from /lib64/libgobject-2.0.so.0
#6 ??
from /usr/lib64/gstreamer-0.10/libgstplaybin.so
#7 ??
from /usr/lib64/gstreamer-0.10/libgstplaybin.so
#8 ??
from /usr/lib64/gstreamer-0.10/libgstplaybin.so
#9 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#10 ??
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /lib64/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 ??
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/gstreamer-0.10/libgstqtdemux.so
#18 ??
from /usr/lib64/gstreamer-0.10/libgstqtdemux.so
#19 ??
from /usr/lib64/libgstreamer-0.10.so.0
#20 ??
from /lib64/libglib-2.0.so.0
#21 ??
from /lib64/libglib-2.0.so.0
#22 start_thread
from /lib64/libpthread.so.0
#23 clone
from /lib64/libc.so.6



----------- .xsession-errors (40437 sec old) ---------------------
** (avant-window-navigator:3386): CRITICAL **: awn_task_win_enter_out: assertion `AWN_IS_TASK(task)' failed
** (avant-window-navigator:3386): CRITICAL **: awn_task_win_enter_out: assertion `AWN_IS_TASK(task)' failed
Launched application : 7663
** (avant-window-navigator:3386): CRITICAL **: awn_task_win_enter_out: assertion `AWN_IS_TASK(task)' failed
(evolution:5919): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:5919): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:5919): evolution-mail-WARNING **: Failed to refresh folders: No such folder mail
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-10-31 22:44: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 bug has been marked as a duplicate of 434996 ***