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 470364 - crash in Rhythmbox Music Player: Disabling jameno plugin
crash in Rhythmbox Music Player: Disabling jameno 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-08-26 06:59 UTC by velazquez_hm
Modified: 2007-08-27 12:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description velazquez_hm 2007-08-26 06:59:13 UTC
What were you doing when the application crashed?
Disabling jameno plugin


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

Memory status: size: 91348992 vsize: 91348992 resident: 36999168 share: 23891968 rss: 36999168 rss_rlim: 4294967295
CPU usage: start_time: 1188111293 rtime: 741 utime: 656 stime: 85 cutime:1 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 -1208284624 (LWP 10516)]
[New Thread -1219974256 (LWP 10575)]
[New Thread -1245799536 (LWP 10567)]
[New Thread -1234076784 (LWP 10520)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 2 (Thread -1219974256 (LWP 10575))

  • #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 ---------------------
(gnome-terminal:8591): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
AFD changed from -2 to -1
AFD changed from -2 to -1
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x34000df specified for 0x340b95a (Shutting d).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x34000df specified for 0x340b95a (Shutting d).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x340004f specified for 0x34000fe (Shutting d).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x340004f specified for 0x34000fe (Shutting d).
** (rhythmbox:10516): WARNING **: Unknown action (1024) in smart playlist will be ignored.
(rhythmbox:10516): 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 palfrey 2007-08-27 12:37:45 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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