Bug 457602 – crash in Rhythmbox Music Player: I was closing Rhythmbox ...

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 457602 - crash in Rhythmbox Music Player: I was closing Rhythmbox ...


Summary:	crash in Rhythmbox Music Player: I was closing Rhythmbox ...


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-07-17 07:48 UTC by webmaster
Modified:	2007-07-18 09:45 UTC

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

Description webmaster 2007-07-17 07:48:15 UTC

What were you doing when the application crashed?
I was closing Rhythmbox by clicking the ¨x¨ button in the top right corner


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 108449792 vsize: 108449792 resident: 28250112 share: 16781312 rss: 28250112 rss_rlim: 4294967295
CPU usage: start_time: 1184658379 rtime: 276 utime: 247 stime: 29 cutime:19 cstime: 6 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 -1208227280 (LWP 3664)]
[New Thread -1254888560 (LWP 3690)]
[New Thread -1224750192 (LWP 3685)]
[New Thread -1265378416 (LWP 3684)]
(no debugging symbols found)
0x00a30402 in __kernel_vsyscall ()

+ Trace 148547

Thread 2 (Thread -1254888560 (LWP 3690))

#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 free
from /lib/libc.so.6



----------- .xsession-errors ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x18015e9
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x5d
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x180185e
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x5d
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-18 09:45:18 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 ***