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 474960 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-08 20:34 UTC by pldnnlly
Modified: 2007-09-09 05:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description pldnnlly 2007-09-08 20:34:26 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 103137280 vsize: 103137280 resident: 36417536 share: 24535040 rss: 36417536 rss_rlim: 4294967295
CPU usage: start_time: 1189283384 rtime: 741 utime: 625 stime: 116 cutime:7 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 -1208239568 (LWP 3512)]
[New Thread -1249059952 (LWP 3526)]
[New Thread -1225540720 (LWP 3524)]
[New Thread -1237759088 (LWP 3519)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 161409

Thread 2 (Thread -1249059952 (LWP 3526))

  • #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 (34 sec old) ---------------------
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
Bonobo accessibility support initialized
GTK Accessibility Module initialized
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1404fca
Bonobo accessibility support initialized
GTK Accessibility Module initialized
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x45
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-09-09 05:13:46 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 ***