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 450684 - crash in Rhythmbox Music Player: closing the app after at...
crash in Rhythmbox Music Player: closing the app after at...
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-24 17:39 UTC by robert
Modified: 2007-06-24 22:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description robert 2007-06-24 17:39:00 UTC 
What were you doing when the application crashed?
closing the app after attempting to play a .wav file without the codec installed


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.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 558260224 vsize: 558260224 resident: 60096512 share: 22532096 rss: 60096512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182706656 rtime: 861 utime: 641 stime: 220 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496376384 (LWP 6810)]
[New Thread 1115699536 (LWP 6928)]
[New Thread 1105209680 (LWP 6872)]
[New Thread 1094719824 (LWP 6826)]
(no debugging symbols found)
0x000000330d80c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 143392

Thread 2 (Thread 1115699536 (LWP 6928))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /lib64/libgthread-2.0.so.0
  • #8 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 ??
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6 


----------- .xsession-errors ---------------------
(evolution:3389): e-data-server-WARNING **: Could not open converter for 'printable-ascii' to 'UTF-8' charset
(evolution:3389): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(rhythmbox:6810): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:6810): 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 Pedro Villavicencio 2007-06-24 22:42:58 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 ***