Bug 459043 – crash in Rhythmbox Music Player: I just clicked on the ne...

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 459043 - crash in Rhythmbox Music Player: I just clicked on the ne...


Summary:	crash in Rhythmbox Music Player: I just clicked on the ne...


Status:	RESOLVED DUPLICATE of bug 420106

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-07-21 17:53 UTC by Allan Engelhardt
Modified:	2007-07-25 14:42 UTC

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

Description Allan Engelhardt 2007-07-21 17:53:27 UTC

What were you doing when the application crashed?
I just clicked on the next track button in Music Applet and then Rhythmox crashed.


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.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 705896448 vsize: 705896448 resident: 62107648 share: 28180480 rss: 62107648 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185032005 rtime: 10886 utime: 9315 stime: 1571 cutime:5 cstime: 50 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912709363904 (LWP 3625)]
[New Thread 1115699536 (LWP 18450)]
[New Thread 1105209680 (LWP 18449)]
[New Thread 1126189392 (LWP 18447)]
[New Thread 1157658960 (LWP 18446)]
[New Thread 1136679248 (LWP 18445)]
[New Thread 1147169104 (LWP 18384)]
[New Thread 1094719824 (LWP 3631)]
0x00002aaab188b808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 149622

Thread 4 (Thread 1126189392 (LWP 18447))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#2 <signal handler called>
#3 resample_set_format
at resample.c line 289
#4 resample_set_state_from_caps
at gstaudioresample.c line 328
#5 audioresample_set_caps
at gstaudioresample.c line 430
#6 gst_base_transform_configure_caps
at gstbasetransform.c line 625
#7 gst_base_transform_setcaps
at gstbasetransform.c line 803
#8 gst_pad_set_caps
at gstpad.c line 2362
#9 gst_pad_chain_unchecked
at gstpad.c line 2421
#10 gst_pad_push
at gstpad.c line 3625
#11 gst_base_transform_chain
at gstbasetransform.c line 1571
#12 gst_pad_chain_unchecked
at gstpad.c line 3459
#13 gst_pad_push
at gstpad.c line 3625
#14 gst_queue_loop
at gstqueue.c line 810
#15 gst_task_func
at gsttask.c line 192
#16 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#17 g_thread_create_proxy
at gthread.c line 591
#18 start_thread
at pthread_create.c line 296
#19 clone
from /lib64/libc.so.6



----------- .xsession-errors (5610 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5200003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
error : xmlEncodeEntitiesReentrant : input not UTF-8
encoding error : output conversion failed due to conv error, bytes 0x84 0x22 0x20 0x6C
I/O error : encoder error
Initializing nautilus-search-tool extension
Initializing nautilus-flac-converter extension
Initializing nautilus-image-converter extension
Initializing nautilus-open-terminal extension
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-25 14:42:04 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 420106 ***