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 449866 - crash in Rhythmbox Music Player: I just clicked the x ico...
crash in Rhythmbox Music Player: I just clicked the x ico...
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-21 20:15 UTC by Kamil Stawirej
Modified: 2007-06-21 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Kamil Stawirej 2007-06-21 20:15:41 UTC
What were you doing when the application crashed?
I just clicked the x icon (right upper-hand corner of the window) to close rhythmbox.


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.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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 97693696 vsize: 97693696 resident: 29851648 share: 17272832 rss: 29851648 rss_rlim: 4294967295
CPU usage: start_time: 1182456840 rtime: 222 utime: 194 stime: 28 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208481232 (LWP 3518)]
[New Thread -1256191088 (LWP 3540)]
[New Thread -1220498544 (LWP 3534)]
[New Thread -1233831024 (LWP 3532)]
[New Thread -1245131888 (LWP 3526)]
(no debugging symbols found)
0x0085b402 in __kernel_vsyscall ()

Thread 2 (Thread -1256191088 (LWP 3540))

  • #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 (6 sec old) ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-writer.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-impress.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Nie można otworzyć pliku /usr/share/applications/openoffice.org-1.9-calc.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
Nie można otworzyć pliku file:///home/kamil/Pulpit/gnome-terminal.desktop z aktywatorem panelu: Nie ma takiego pliku ani katalogu
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Introspect error: Message did not receive a reply (timeout by message bus)
could not attach to desktop process
Loading "installonlyn" plugin
Loading "installonlyn" plugin
(rhythmbox:3518): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Urządzenie lub zasoby zajęte' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-06-21 20:19:45 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Christian Kirbach 2007-06-21 20:21:33 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 ***