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 371512 - crash in Rhythmbox Music Player: messing with play queue ...
crash in Rhythmbox Music Player: messing with play queue ...
Status: RESOLVED DUPLICATE of bug 369214
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-06 13:10 UTC by mr.daniel.mcelroy
Modified: 2006-11-06 21:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description mr.daniel.mcelroy 2006-11-06 13:10:51 UTC
What were you doing when the application crashed?
messing with play queue and playlists. getting used to rhythmbox


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6.stk16 #1 SMP Wed Oct 25 17:37:07 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors ---------------------
(rhythmbox:21719): Rhythmbox-WARNING **: Couldn't get menu widget for /BrowserSourcePopup
(rhythmbox:21719): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(rhythmbox:21719): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(rhythmbox:21719): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject'
(rhythmbox:21719): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(rhythmbox:21719): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
21719: assertion failed "*bucket != NULL" file "dbus-hash.c" line 476 function remove_entry
Xlib: unexpected async reply (sequence 0x175bf8)!
** (bug-buddy:28795): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 202575872 vsize: 0 resident: 202575872 share: 0 rss: 33587200 rss_rlim: 0
CPU usage: start_time: 1162818107 rtime: 0 utime: 2863 stime: 0 cutime:2376 cstime: 0 timeout: 487 it_real_value: 0 frequency: 10

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 -1208330528 (LWP 21719)]
[New Thread -1414009968 (LWP 28199)]
[New Thread -1434989680 (LWP 28197)]
[New Thread -1361560688 (LWP 23835)]
[New Thread -1372050544 (LWP 23834)]
[New Thread -1309111408 (LWP 21729)]
[New Thread -1276789872 (LWP 21725)]
(no debugging symbols found)
0x00b7c402 in __kernel_vsyscall ()

Thread 6 (Thread -1309111408 (LWP 21729))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    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 dbus_malloc
    from /lib/libdbus-1.so.3
  • #8 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #9 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #10 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #11 dbus_connection_set_watch_functions
    from /lib/libdbus-1.so.3
  • #12 dbus_connection_flush
    from /lib/libdbus-1.so.3
  • #13 dbus_pending_call_block
    from /lib/libdbus-1.so.3
  • #14 dbus_connection_send_with_reply_and_block
    from /lib/libdbus-1.so.3
  • #15 rb_metadata_load
  • #16 rhythmdb_entry_move_to_trash
  • #17 g_thread_create_full
    from /lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6

Comment 1 James "Doc" Livingston 2006-11-06 21:31:50 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 369214 ***