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 349101 - crash on Rhythmbox Music Player
crash on Rhythmbox Music Player
Status: RESOLVED DUPLICATE of bug 346800
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 349100 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-28 15:57 UTC by Andy Wingo
Modified: 2006-07-28 16:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Andy Wingo 2006-07-28 15:57:32 UTC
What were you doing when the application crashed?
just opening rhythmbox :-(


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.90 2006-07-24 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 217694208 vsize: 217694208 resident: 42446848 share: 16850944 rss: 42446848 rss_rlim: -1
CPU usage: start_time: 1154102196 rtime: 297 utime: 274 stime: 23 cutime:4 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 48002780559792 (LWP 18917)]
0x00002ba880074dbf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 48002780559792 (LWP 18917))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 IA__g_logv
  • #6 IA__g_log
    at gmessages.c line 517
  • #7 IA__g_assert_warning
    at gmessages.c line 552
  • #8 gtk_tree_model_filter_convert_path_to_child_path
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 gtk_tree_model_filter_convert_child_iter_to_iter
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #13 IA__g_signal_emit
    at gsignal.c line 2241
  • #14 gtk_tree_store_set_valist
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 gtk_tree_store_set
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 rb_sourcelist_get_type
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #20 IA__g_signal_emit
    at gsignal.c line 2241
  • #21 g_object_dispatch_properties_changed
    at gobject.c line 561
  • #22 IA__g_object_set_valist
    at gobjectnotifyqueue.c line 123
  • #23 IA__g_object_set
    at gobject.c line 1181
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #27 IA__g_signal_emit
    at gsignal.c line 2241
  • #28 rhythmdb_query_model_remove_entry
  • #29 IA__g_closure_invoke
    at gclosure.c line 490
  • #30 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #31 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #32 IA__g_signal_emit
    at gsignal.c line 2241
  • #33 rhythmdb_add_uri
  • #34 IA__g_main_context_dispatch
    at gmain.c line 2043
  • #35 g_main_context_iterate
    at gmain.c line 2675
  • #36 IA__g_main_loop_run
    at gmain.c line 2879
  • #37 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Andy Wingo 2006-07-28 16:00:01 UTC
*** Bug 349100 has been marked as a duplicate of this bug. ***
Comment 2 Andy Wingo 2006-07-28 16:01:07 UTC
If I kill Avahi (0.6.11), this no longer happens.
Comment 3 William Jon McCann 2006-07-28 16:03:06 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 346800 ***