Bug 452314 – crash in Rhythmbox Music Player: Closed the app when down...

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 452314 - crash in Rhythmbox Music Player: Closed the app when down...


Summary:	crash in Rhythmbox Music Player: Closed the app when down...


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-06-29 17:09 UTC by me
Modified:	2007-06-29 23:15 UTC

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

Description me 2007-06-29 17:09:24 UTC

What were you doing when the application crashed?
Closed the app when downloading a podcast


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: 176939008 vsize: 176939008 resident: 52781056 share: 20803584 rss: 52781056 rss_rlim: 4294967295
CPU usage: start_time: 1183136594 rtime: 1269 utime: 1194 stime: 75 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 -1208890832 (LWP 3083)]
[New Thread -1339257968 (LWP 3173)]
[New Thread -1264747632 (LWP 3161)]
[New Thread -1286120560 (LWP 3135)]
[New Thread -1296610416 (LWP 3104)]
[New Thread -1230197872 (LWP 3091)]
[New Thread -1253446768 (LWP 3088)]
(no debugging symbols found)
0x00b5a402 in __kernel_vsyscall ()

+ Trace 144663

Thread 2 (Thread -1339257968 (LWP 3173))

#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 ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1408c57
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  160
  Minor opcode:  6
  Resource id:  0x1408c57
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1408c58
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  160
  Minor opcode:  6
  Resource id:  0x1408c58
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-29 23:15:23 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 ***