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 450652 - crash in Rhythmbox Music Player: Added a new artist's alb...
crash in Rhythmbox Music Player: Added a new artist's alb...
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 16:12 UTC by biv
Modified: 2007-06-24 16:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description biv 2007-06-24 16:12:07 UTC
What were you doing when the application crashed?
Added a new artist's album to the playlist.


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 168218624 vsize: 168218624 resident: 39542784 share: 19865600 rss: 39542784 rss_rlim: 4294967295
CPU usage: start_time: 1182681775 rtime: 9740 utime: 8641 stime: 1099 cutime:1 cstime: 2 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 -1208149760 (LWP 3347)]
[New Thread -1234007152 (LWP 14437)]
[New Thread -1311036528 (LWP 14436)]
[New Thread -1426424944 (LWP 14430)]
[New Thread -1436914800 (LWP 14424)]
[New Thread -1332016240 (LWP 3861)]
[New Thread -1245312112 (LWP 3354)]
(no debugging symbols found)
0x007d1402 in __kernel_vsyscall ()

Thread 3 (Thread -1311036528 (LWP 14436))

  • #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 (7 sec old) ---------------------
  gtk.threads_enter()
/usr/lib/python2.5/site-packages/BitTorrent/GUI.py:28: GtkDeprecationWarning: gtk.threads_enter is deprecated, use gtk.gdk.threads_enter instead
  gtk.threads_enter()
/usr/lib/python2.5/site-packages/BitTorrent/GUI.py:30: GtkDeprecationWarning: gtk.threads_leave is deprecated, use gtk.gdk.threads_leave instead
  gtk.threads_leave()
Предупреждение менеджера окон: неверный параметр WM_TRANSIENT_FOR окна 0x65 указан для 0xc30d3c ().
totem-video-thumbnailer: 'file:///root/Desktop/Ref%C3%A9ns%20da%20Cidade%20-%20Independente%20--%20Jamendo%20-%20OGG%20Vorbis%20q7%20-%202007.06.07%20%5Bwww.jamendo.com%5D/01%20-%20setembro.ogg' isn't
Reason: Media contains no supported video streams.
/usr/bin/bittorrent:3785: GtkDeprecationWarning: gtk.threads_leave is deprecated, use gtk.gdk.threads_leave instead
  gtk.threads_leave()
(rhythmbox:3347): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Устройство или ресурс занято' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-24 16:13:28 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 ***