GNOME Bugzilla – Bug 485911
crash in Rhythmbox Music Player: Trying to play a music C...
Last modified: 2007-10-13 07:10:24 UTC
What were you doing when the application crashed? Trying to play a music CD 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 113987584 vsize: 113987584 resident: 27828224 share: 16576512 rss: 27828224 rss_rlim: 4294967295 CPU usage: start_time: 1192071698 rtime: 832 utime: 629 stime: 203 cutime:16 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209026000 (LWP 4214)] [New Thread -1285227632 (LWP 4234)] [New Thread -1250968688 (LWP 4233)] [New Thread -1253049456 (LWP 4227)] (no debugging symbols found) 0x005f5402 in __kernel_vsyscall ()
+ Trace 169647
Thread 2 (Thread -1285227632 (LWP 4234))
----------- .xsession-errors (40 sec old) --------------------- QWidget::setMinimumSize: The smallest allowed size is (0,0) Window manager warning: Invalid WM_TRANSIENT_FOR window 0x44 specified for 0x36016ad (Error - Am). X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x360004e QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) ~ScimInputContextPlugin() ** (rhythmbox:4214): WARNING **: No property volume.disc.capacity on device with id /org/freedesktop/Hal/devices/volume_part_1_size_466905088 ICE default IO error handler doing an exit(), pid = 4167, errno = 0 *** stack smashing detected ***: rhythmbox terminated Xlib: unexpected async reply (sequence 0x3b8d)! --------------------------------------------------
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 364048 ***