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 444585 - crash in Rhythmbox Music Player: disabling a plugin
crash in Rhythmbox Music Player: disabling a plugin
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-06-06 04:44 UTC by romero2k
Modified: 2007-06-06 10:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description romero2k 2007-06-06 04:44:23 UTC 
What were you doing when the application crashed?
disabling a plugin


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: 213577728 vsize: 213577728 resident: 53997568 share: 19128320 rss: 53997568 rss_rlim: 4294967295
CPU usage: start_time: 1181104587 rtime: 2883 utime: 2731 stime: 152 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 -1208817104 (LWP 4161)]
[New Thread -1364206704 (LWP 4286)]
[New Thread -1353716848 (LWP 4280)]
[New Thread -1265636464 (LWP 4277)]
[New Thread -1309684848 (LWP 4276)]
[New Thread -1320174704 (LWP 4274)]
[New Thread -1299194992 (LWP 4205)]
[New Thread -1288705136 (LWP 4204)]
[New Thread -1278215280 (LWP 4203)]
[New Thread -1238787184 (LWP 4202)]
[New Thread -1255146608 (LWP 4169)]
(no debugging symbols found)
0x00fad402 in __kernel_vsyscall ()

+ Trace 138649

Thread 2 (Thread -1364206704 (LWP 4286))

  • #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 (6 sec old) ---------------------
                                      SELECT * FROM PodcastFeeds ORDER BY Title
                                      '
Setting IO Backend to Banshee.IO.Unix.IOConfig (unix)
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstaudioresample.so
Please either:
- remove it and restart.
- run with --gst-disable-segtrap and debug.
(rhythmbox:4161): 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-06-06 10:50:41 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 ***