Bug 438136 – crash in Rhythmbox Music Player: My first attempt to play...

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 438136 - crash in Rhythmbox Music Player: My first attempt to play...


Summary:	crash in Rhythmbox Music Player: My first attempt to play...


Status:	RESOLVED DUPLICATE of bug 436456

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-05-13 16:13 UTC by bshotts
Modified:	2007-05-20 10:23 UTC

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

Description bshotts 2007-05-13 16:13:07 UTC

What were you doing when the application crashed?
My first attempt to play a song on Magnature (Cargo Cult - track 13 from Alchemy).


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

System: Linux 2.6.21-1.3142.fc7 #1 SMP Mon May 7 21:14:09 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 267632640 vsize: 267632640 resident: 152662016 share: 13484032 rss: 152662016 rss_rlim: 4294967295
CPU usage: start_time: 1179071592 rtime: 29493 utime: 27448 stime: 2045 cutime:15 cstime: 14 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 -1208694528 (LWP 2834)]
[New Thread -1279267952 (LWP 3022)]
[New Thread -1225725040 (LWP 2851)]
(no debugging symbols found)
0x00818402 in __kernel_vsyscall ()

+ Trace 133957

Thread 1 (Thread -1208694528 (LWP 2834))

#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 __assert_fail
from /lib/libc.so.6
#8 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#9 ??
from /usr/lib/libpython2.5.so.1.0
#10 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#11 ??
from /usr/lib/libpython2.5.so.1.0
#12 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#13 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#14 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#15 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#0 __kernel_vsyscall



----------- .xsession-errors (32 sec old) ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x14015ff
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x14015ff
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1401600
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x1401600
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-05-20 10:23:40 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 436456 ***