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 473803 - crash in Rhythmbox Music Player: Rhythmbox crashed when I...
crash in Rhythmbox Music Player: Rhythmbox crashed when I...
Status: RESOLVED DUPLICATE of bug 452703
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-05 06:38 UTC by Hussam Al-Tayeb
Modified: 2007-09-05 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Hussam Al-Tayeb 2007-09-05 06:38:55 UTC 
Version: 0.11.1

What were you doing when the application crashed?
Rhythmbox crashed when I physically deleted 30 files from my music library while rhythmbox was open


Distribution: Unknown
Gnome Release: 2.18.3 2007-07-07 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-ARCH #1 SMP PREEMPT Fri Aug 31 19:54:09 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: gnome

Memory status: size: 100716544 vsize: 100716544 resident: 31506432 share: 18247680 rss: 31506432 rss_rlim: 4294967295
CPU usage: start_time: 1188973562 rtime: 803 utime: 748 stime: 55 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229375792 (LWP 18760)]
[New Thread -1280316528 (LWP 18775)]
[New Thread -1235461232 (LWP 18768)]
0xb7fc9410 in __kernel_vsyscall ()

+ Trace 160570

Thread 1 (Thread -1229375792 (LWP 18760))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 rhythmdb_property_model_delete_prop
    at rhythmdb-property-model.c line 653
  • #11 rhythmdb_property_model_prop_changed_cb
    at rhythmdb-property-model.c line 537
  • #12 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
    at rb-marshal.c line 500
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #16 IA__g_signal_emit
    at gsignal.c line 2243
  • #17 rhythmdb_query_model_entry_changed_cb
    at rhythmdb-query-model.c line 906
  • #18 rb_marshal_VOID__BOXED_POINTER
    at rb-marshal.c line 588
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #22 IA__g_signal_emit
    at gsignal.c line 2243
  • #23 emit_entry_changed
    at rhythmdb.c line 949
  • #24 IA__g_hash_table_foreach
    at ghash.c line 680
  • #25 rhythmdb_commit_internal
    at rhythmdb.c line 1067
  • #26 rhythmdb_process_one_event
    at rhythmdb.c line 1980
  • #27 rb_async_queue_watch_dispatch
    at rb-async-queue-watch.c line 61
  • #28 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #29 g_main_context_iterate
    at gmain.c line 2694
  • #30 IA__g_main_loop_run
    at gmain.c line 2898
  • #31 IA__gtk_main
    at gtkmain.c line 1154
  • #32 main
    at main.c line 306
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-09-05 17:37:45 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 452703 ***






Comment 2


Hussam Al-Tayeb





          2007-09-05 21:17:30 UTC
        



(In reply to comment #1)
> 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 452703 ***
> 

This may be my fault for neglecting to add this information. I saw this bug in svn trunk r5336 (That's after 452703 was fixed.)