Bug 444059 – crash in Rhythmbox Music Player: nothing

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 444059 - crash in Rhythmbox Music Player: nothing


Summary:	crash in Rhythmbox Music Player: nothing


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-04 18:48 UTC by tatarduka
Modified:	2007-06-04 19:27 UTC

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

Description tatarduka 2007-06-04 18:48:01 UTC

What were you doing when the application crashed?
nothing


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: Mist
Icon Theme: Mist

Memory status: size: 123490304 vsize: 123490304 resident: 28676096 share: 16900096 rss: 28676096 rss_rlim: 4294967295
CPU usage: start_time: 1180982732 rtime: 300 utime: 261 stime: 39 cutime:2 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 -1209103824 (LWP 3091)]
[New Thread -1272628336 (LWP 3114)]
[New Thread -1262138480 (LWP 3113)]
[New Thread -1239782512 (LWP 3111)]
[New Thread -1226761328 (LWP 3109)]
[New Thread -1251083376 (LWP 3098)]
(no debugging symbols found)
0x0071f402 in __kernel_vsyscall ()

+ Trace 138224

Thread 3 (Thread -1262138480 (LWP 3113))

#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 (8 sec old) ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x14025d6
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x14026fa
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x14026fa
--------------------------------------------------

Comment 1 Baptiste Mille-Mathias 2007-06-04 19:27:36 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 434003 ***