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 491339 - crash in Rhythmbox Music Player: closing the application,...
crash in Rhythmbox Music Player: closing the application,...
Status: RESOLVED DUPLICATE of bug 484988
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-29 12:00 UTC by Stefano Costa
Modified: 2007-10-30 12:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Stefano Costa 2007-10-29 12:00:23 UTC 
Version: 0.10.1

What were you doing when the application crashed?
closing the application, rhytmbox crashed


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 74051584 vsize: 74051584 resident: 27664384 share: 14704640 rss: 27664384 rss_rlim: 4294967295
CPU usage: start_time: 1193657270 rtime: 472 utime: 391 stime: 81 cutime:0 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/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b866c0 (LWP 23998)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 173638

Thread 1 (Thread 0xb6b866c0 (LWP 23998))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 gdk_event_dispatch
    at /tmp/buildd/gtk+2.0-2.10.13/gdk/x11/gdkevents-x11.c line 2323
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7228 sec old) ---------------------
(trackerd:13369): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed
(trackerd:13369): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-30 12:00:16 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 484988 ***