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 415598 - Rhythmbox crashes when user chose quit menu item.
Rhythmbox crashes when user chose quit menu item.
Status: RESOLVED DUPLICATE of bug 401299
Product: rhythmbox
Classification: Other
Component: general
0.9.8
Other opensolaris
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-07 06:31 UTC by Tim Miao
Modified: 2007-06-03 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim Miao 2007-03-07 06:31:37 UTC
Steps to reproduce:
1. Launch rhythmbox.
2. Finish the basic settings.
3. Click the top menu Music->Quit to quit the rhythmbox.


Stack trace:
1480:   rhythmbox
-----------------  lwp# 1 / thread# 1  --------------------
 d2b3e5a5 waitid   (0, 672, 8046500, 3)
 d2b31516 waitpid  (672, 8046614, 0) + 70
 d1cb8972 libgnomeui_segv_handle (6, 0, 80466c0) + ba
 d2b3cc2f __sighndlr (6, 0, 80466c0, d1cb88b8) + f
 d2b321ab call_user_handler (6, 0, 80466c0) + 2b8
 d2b32352 sigacthandler (6, 0, 80466c0) + c2
 --- called from signal handler with signal 6 (SIGABRT) ---
 d2b3e135 _lwp_kill (1, 6) + 15
 d2af64a2 raise    (6) + 22
 d2ad4ad4 abort    (0, 0, d2121e44, 0, 824d600, 1) + 64
 d20bb1f4 g_logv   (0, 8, cf7b301c, 8046dfc) + 340
 d20bb21d g_log    (0, 8, cf7b301c, cf7b3008, b0, cf7b2fec) + 25
 cf7ad07d atk_relation_set_get_n_relations (0, 0, cf2e3148, cfb66c94, cfb3a0c1, 0) + 5d
 cf2bdc61 impl_accessibility_accessible_get_relation_set (890c394, 804702c) + 3d
 cf2bb409 _ORBIT_skel_small_Accessibility_Accessible_getRelationSet (890c394, 8046f30, 0, 8046ee0, 804702c, cf2bdc24) + 11
 cfb4129a ORBit_POAObject_invoke (890dbd0, 8046f30, 0, 8046ee0, 8046f68, 804702c) + 22
 cfb45689 ORBit_OAObject_invoke (890dbd0, 8046f30, 0, 8046ee0, 8046f68, 804702c) + 21
 cfb3308b ORBit_small_invoke_adaptor (890dbd0, 8954080, cf2e0a48, 8046f68, 804702c) + 2b3
 cfb416d2 ORBit_POAObject_handle_request (890dbd0, 8852c74, 0, 0, 0, 8954080) + 32a
 cfb41ad0 ORBit_POAObject_invoke_incoming_request (890dbd0, 8954080, 804702c) + 54
 cfb41f56 ORBit_POA_handle_request (8187890, 8954080, 8954098) + 2ea
 cfb45487 ORBit_handle_request (8187818, 8954080) + 4b
 cfb3027a giop_connection_handle_input (83cd4d0) + 2e2
 cfb4b6b1 link_connection_io_handler (0, 1, 83cd4d0) + 55
 cfb4d2d5 link_source_dispatch (841a7f8, cfb4b65c, 83cd4d0) + 41
 d20b371d g_main_dispatch (8171a40) + 1d9
 d20b480d g_main_context_dispatch (8171a40) + 85
 d20b4c2a g_main_context_iterate (8171a40, 1, 1, 8100378) + 3ce
 d20b522c g_main_loop_run (888a438) + 1b8
 d258ad36 gtk_main (8047400, 80472e8, d2bfb7c0, d2b3fce5, d2ac639c, 29) + b2
 08079487 main     (1, 804732c, 8047334) + 497
 08078332 _start   (1, 8047468, 0, 8047472, 8047493, 80474c7) + 7a
-----------------  lwp# 7 / thread# 7  --------------------
 d2b3cb89 lwp_park (0, cd2fde38, 0)
 d2b36d02 cond_wait_queue (87d9f20, 824b7c8, cd2fde38, 0) + 3e
 d2b37097 cond_wait_common (87d9f20, 824b7c8, cd2fde38) + 1e1
 d2b372bc _cond_timedwait (87d9f20, 824b7c8, cd2fdeb8) + 4a
 d2b3734b cond_timedwait (87d9f20, 824b7c8, cd2fdeb8) + 27
 d2b37388 pthread_cond_timedwait (87d9f20, 824b7c8, cd2fdeb8) + 21
 d1e7165e g_cond_timed_wait_posix_impl (87d9f20, 824b7c8, cd2fdf48) + 5a
 d20958f7 g_async_queue_pop_intern_unlocked (824b7a8, 0, cd2fdf48) + 8b
 d2095d14 g_async_queue_timed_pop (824b7a8, cd2fdf48) + 5c
 080b04a5 read_queue (824b7a8, 824a0b4) + 85
 080b0c62 action_thread_main (824a020) + 2a
 d20ce966 g_thread_create_proxy (81f2140) + 11a
 d2b3c8d2 _thr_setup (cd400800) + 52
 d2b3cb30 _lwp_start (cd400800, 0, 0, 0, 0, 0)


Other information:
This bug can be found with rhythmbox 0.9.8 on gnome2.17.91.
Comment 1 Philip Withnall 2007-06-03 10:54:23 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 401299 ***