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 445872 - crash in Rhythmbox Music Player: I was closing the applic...
crash in Rhythmbox Music Player: I was closing the applic...
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-09 21:36 UTC by Per Thomas Jahr
Modified: 2007-06-09 23:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Per Thomas Jahr 2007-06-09 21:36:04 UTC
What were you doing when the application crashed?
I was closing the application and it crashed. The same seems to happen with the volume control (Volume Applet 2.18.0).


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.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: 252989440 vsize: 252989440 resident: 164323328 share: 26185728 rss: 164323328 rss_rlim: 4294967295
CPU usage: start_time: 1181424698 rtime: 2671 utime: 2588 stime: 83 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 -1209042384 (LWP 5776)]
[New Thread 77749136 (LWP 5898)]
[New Thread -1330648176 (LWP 5857)]
[New Thread -1274029168 (LWP 5796)]
[New Thread -1236812912 (LWP 5783)]
(no debugging symbols found)
0x00e14402 in __kernel_vsyscall ()

Thread 2 (Thread 77749136 (LWP 5898))

  • #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 ---------------------
V4L2Grabber::~V4L2Grabber(): deleted.
V4L2Grabber::~V4L2Grabber(): wait().
V4L2Grabber::~V4L2Grabber(): deleted.
ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to create IPC semaphore
Loading "installonlyn" plugin
kbuildsycoca running...
Reusing existing ksycoca
(rhythmbox:5776): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:5776): 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...
Xlib: unexpected async reply (sequence 0x38de7)!
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-09 23:18:10 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 ***