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 465673 - crash in Rhythmbox Music Player: Changing order inthe pla...
crash in Rhythmbox Music Player: Changing order inthe pla...
Status: RESOLVED DUPLICATE of bug 359083
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-11 13:23 UTC by upstairs
Modified: 2007-08-23 10:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description upstairs 2007-08-11 13:23:20 UTC
What were you doing when the application crashed?
Changing order inthe playlist row


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 195776512 vsize: 195776512 resident: 53252096 share: 26775552 rss: 53252096 rss_rlim: 4294967295
CPU usage: start_time: 1186825816 rtime: 43608 utime: 38718 stime: 4890 cutime:5 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 -1208710608 (LWP 4958)]
[New Thread -1346217072 (LWP 6256)]
[New Thread -1303401584 (LWP 6253)]
[New Thread -1292911728 (LWP 6252)]
[New Thread -1282421872 (LWP 6251)]
[New Thread -1250952304 (LWP 6250)]
[New Thread -1261442160 (LWP 6249)]
[New Thread -1271932016 (LWP 6248)]
[New Thread -1220797552 (LWP 4965)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208710608 (LWP 4958))

  • #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 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #12 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #25 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
  • #27 ??
  • #28 rhythmdb_query_model_remove_entry
  • #29 rb_static_playlist_source_remove_location
  • #30 rb_static_playlist_source_remove_entry
  • #31 ??
  • #32 rb_source_delete
    from /usr/lib/librhythmbox-core.so.0
  • #33 ??
  • #34 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #35 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #36 ??
    from /lib/libgobject-2.0.so.0
  • #37 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #38 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #41 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #42 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #46 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /lib/libgobject-2.0.so.0
  • #52 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #53 ??
    from /lib/libgobject-2.0.so.0
  • #54 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #55 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #56 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #60 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #61 ??
    from /lib/libglib-2.0.so.0
  • #62 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #63 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #64 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** (rhythmbox:4958): WARNING **: Add decoder adpcm_thp (69650) please
(rhythmbox:4958): libgnomevfs-WARNING **: trying to read from a non-existing handle
(rhythmbox:4958): libgnomevfs-WARNING **: trying to read from a non-existing handle
(rhythmbox:4958): libgnomevfs-WARNING **: trying to read from a non-existing handle
** Message: <info>  Jste právě připojeni ke drátové síti.
(rhythmbox:4958): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
RhythmDB-ERROR **: file rhythmdb-property-model.c: line 653 (rhythmdb_property_model_delete_prop): assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))
aborting...
--------------------------------------------------
Comment 1 palfrey 2007-08-23 10:17:54 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 359083 ***