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 454524 - crash in Rhythmbox Music Player: unselected the Magnatune...
crash in Rhythmbox Music Player: unselected the Magnatune...
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-07-07 10:00 UTC by demancey
Modified: 2007-07-07 23:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description demancey 2007-07-07 10:00:58 UTC
What were you doing when the application crashed?
unselected the Magnatune Plugin


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 241397760 vsize: 241397760 resident: 55074816 share: 38989824 rss: 55074816 rss_rlim: 4294967295
CPU usage: start_time: 1183796881 rtime: 22025 utime: 21017 stime: 1008 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 -1208268240 (LWP 8897)]
[New Thread -1422578800 (LWP 10121)]
[New Thread -1401599088 (LWP 10119)]
[New Thread -1380619376 (LWP 10113)]
[New Thread -1370129520 (LWP 10111)]
[New Thread -1349149808 (LWP 10110)]
[New Thread -1328170096 (LWP 8945)]
[New Thread -1317680240 (LWP 8944)]
[New Thread -1307190384 (LWP 8943)]
[New Thread -1338659952 (LWP 8942)]
[New Thread -1282864240 (LWP 8904)]
(no debugging symbols found)
0x00313402 in __kernel_vsyscall ()

Thread 2 (Thread -1422578800 (LWP 10121))

  • #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 (12 sec old) ---------------------
** Message: another gnome-keyring-daemon is running
(gnome-help:9888): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed
(evolution:9536): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:9536): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa3a4020'
(evolution:9536): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa3a4140'
(rhythmbox:8897): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-07 23:20:36 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 ***