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 473716 - crash in Rhythmbox Music Player: listining to radio
crash in Rhythmbox Music Player: listining to radio
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-04 21:59 UTC by beso315
Modified: 2007-09-05 17:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description beso315 2007-09-04 21:59:16 UTC
What were you doing when the application crashed?
listining to radio


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: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 168300544 vsize: 168300544 resident: 56012800 share: 40226816 rss: 56012800 rss_rlim: 4294967295
CPU usage: start_time: 1188943007 rtime: 847 utime: 780 stime: 67 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 -1208563152 (LWP 4145)]
[New Thread -1330443376 (LWP 4193)]
[New Thread -1264460912 (LWP 4190)]
[New Thread -1319953520 (LWP 4183)]
[New Thread -1277600880 (LWP 4150)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1330443376 (LWP 4193))

  • #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 ??


----------- .xsession-errors ---------------------
(nautilus:3042): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:3042): Eel-WARNING **: Error starting command ''/home/beso/Desktop/drive_d/Small videos/S.AMR'': Failed to execute child process "/home/beso/Desktop/drive_d/Small videos/S.AMR" (No such file
(nautilus:3042): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:3042): Eel-WARNING **: Error starting command ''/home/beso/Desktop/drive_d/Small videos/S.AMR'': Failed to execute child process "/home/beso/Desktop/drive_d/Small videos/S.AMR" (No such file
(rhythmbox:4145): 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-09-05 17:10:38 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 ***