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 477524 - crash in Rhythmbox Music Player: minimizing it.
crash in Rhythmbox Music Player: minimizing it.
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-16 16:07 UTC by faemir
Modified: 2007-09-20 17:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description faemir 2007-09-16 16:07:15 UTC
What were you doing when the application crashed?
minimizing it.


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

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 118669312 vsize: 118669312 resident: 28008448 share: 16482304 rss: 28008448 rss_rlim: 4294967295
CPU usage: start_time: 1189958738 rtime: 176 utime: 146 stime: 30 cutime:2 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208174880 (LWP 4655)]
[New Thread -1266832496 (LWP 4676)]
[New Thread -1231680624 (LWP 4675)]
[New Thread -1221190768 (LWP 4673)]
[New Thread -1245512816 (LWP 4670)]
[New Thread -1256002672 (LWP 4664)]
(no debugging symbols found)
0x00a36402 in __kernel_vsyscall ()

Thread 3 (Thread -1231680624 (LWP 4675))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/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/i686/nosegneg/libc.so.6


----------- .xsession-errors ---------------------
Can't have a partition outside the disk!
--- Hash table keys for warning below:
--> file:///home/faemir
(nautilus:4639): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
QWidget::setMinimumSize: The smallest allowed size is (0,0)
QComboBox::setCurrentItem: (speakerComboBox) Index 1 out of range
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
(rhythmbox:4655): 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-20 17:22:18 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 ***