>From what I remember, that issue was happened before. Eflete may have a logical bug.
On Fri, Jul 6, 2018 at 12:57 AM, Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > As I've said before, the eflete issue should never have been considered an > EFL issue. If it's going to be listed as something that time needs to be > spent on then I'll debunk the possibility more formally: > > #0 0x00007ffff020ef54 in ecore_file_recursive_rm (dir=0x14d81a0 > "/home/zmike/") at lib/ecore_file/ecore_file.c:326 > #1 0x000000000045d293 in _exist_permission_popup_close_cb > (data=0x195ce80, > obj=0x400000145654, event_info=0x10) > at ../../src/bin/ui/project_common.c:60 > #2 0x00007ffff27ba9c0 in _eo_evas_smart_cb (data=0x165ad10, > event=0x7fffffffd030) > at lib/evas/canvas/evas_object_smart.c:78 > #3 0x00007fffedef8000 in _event_callback_call (obj_id=0x400000145654, > pd=0x101c5b0, desc=0x150c9f0, event_info=0x10, legacy_compare=1 '\001') at > lib/eo/eo_base_class.c:1694 > #4 0x00007fffedef8341 in _efl_object_event_callback_legacy_call > (obj_id=0x400000145654, pd=0x101c5b0, desc=0x150c9f0, event_info=0x10) at > lib/eo/eo_base_class.c:1767 > #5 0x00007fffedef83e7 in efl_event_callback_legacy_call > (obj=0x400000145654, desc=0x150c9f0, event_info=0x10) > at lib/eo/eo_base_class.c:1770 > #6 0x00007ffff27a8d54 in > _efl_canvas_object_efl_object_event_callback_legacy_call > (eo_obj=0x400000145654, obj=0x101c600, desc=0x150c9f0, event_info=0x10) at > lib/evas/canvas/evas_object_main.c:1231 > #7 0x00007fffedef83e7 in efl_event_callback_legacy_call > (obj=0x400000145654, desc=0x150c9f0, event_info=0x10) > at lib/eo/eo_base_class.c:1770 > #8 0x00007ffff27bd2b4 in evas_object_smart_callback_call > (eo_obj=0x400000145654, event=0x4ffd73 "POPUP_CLOSE_CB", event_info=0x10) > at lib/evas/canvas/evas_object_smart.c:1043 > #9 0x0000000000459438 in _popup_btn_cb (data=0x10, obj=0x40000015b679, > ei=0x0) at ../../src/bin/ui/popup.c:103 > #10 0x00007ffff27ba9c0 in _eo_evas_smart_cb (data=0xf2e990, > event=0x7fffffffd320) > at lib/evas/canvas/evas_object_smart.c:78 > #11 0x00007fffedef8000 in _event_callback_call (obj_id=0x40000015b679, > pd=0x11b6610, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0, > legacy_compare=1 '\001') at lib/eo/eo_base_class.c:1694 > #12 0x00007fffedef8341 in _efl_object_event_callback_legacy_call > (obj_id=0x40000015b679, pd=0x11b6610, desc=0x7fffee361240 > <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/eo/eo_base_class.c:1767 > #13 0x00007fffedef83e7 in efl_event_callback_legacy_call > (obj=0x40000015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, > event_info=0x0) at lib/eo/eo_base_class.c:1770 > #14 0x00007ffff27a8d54 in > _efl_canvas_object_efl_object_event_callback_legacy_call > (eo_obj=0x40000015b679, obj=0x11b6660, desc=0x7fffee361240 > <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at > lib/evas/canvas/evas_object_main.c:1231 > #15 0x00007fffedef83e7 in efl_event_callback_legacy_call > (obj=0x40000015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, > event_info=0x0) at lib/eo/eo_base_class.c:1770 > #16 0x00007ffff78582d6 in _activate (obj=0x40000015b679) at > lib/elementary/efl_ui_button.c:74 > #17 0x00007ffff7858509 in _on_clicked_signal (data=0x40000015b679, > obj=0x400000122e7a, emission=0xc43d7c "elm,action,click", > source=0x7fffedcc4208 "") at lib/elementary/efl_ui_button.c:126 > #18 0x00007ffff397f2b7 in edje_match_callback_exec_check_finals > (ssp=0xccc560, matches=0xc6b7f0, signal_states=0xccc670, > source_states=0xc743c0, sig=0xc43d7c "elm,action,click", > source=0x7fffedcc4208 "", ed=0x12a5ec0, prop=0 '\000') > at lib/edje/edje_match.c:556 > #19 0x00007ffff397f7ec in edje_match_callback_exec (ssp=0xccc560, > matches=0xc6b7f0, sig=0xc43d7c "elm,action,click", source=0x7fffedcc4208 > "", ed=0x12a5ec0, prop=0 '\000') at lib/edje/edje_match.c:711 > #20 0x00007ffff3988a09 in _edje_emit_cb (ed=0x12a5ec0, sig=0xc43d7c > "elm,action,click", src=0x7fffedcc4208 "", data=0x14ce7a0, prop=0 '\000') > at lib/edje/edje_program.c:1647 > #21 0x00007ffff3988854 in _edje_emit_handle (ed=0x12a5ec0, sig=0xc43d7c > "elm,action,click", src=0x7fffedcc4208 "", sdata=0x14ce7a0, prop=0 '\000') > at lib/edje/edje_program.c:1589 > #22 0x00007ffff3981edc in _edje_message_process (em=0x154bce0) at > lib/edje/edje_message_queue.c:783 > #23 0x00007ffff39822f4 in _edje_message_queue_process () at > lib/edje/edje_message_queue.c:886 > #24 0x00007ffff3980ede in _edje_job (data=0x0) at > lib/edje/edje_message_queue.c:260 > #25 0x00007fffee89a51f in _ecore_job_event_handler (data=0x0, type=14, > ev=0x1a09720) at lib/ecore/ecore_job.c:98 > #26 0x00007fffee8a0edd in > _ecore_event_message_handler_efl_loop_message_handler_message_call > (obj=0x40000000141f, pd=0x79bb50, message=0x4000000c8bde) at > lib/ecore/ecore_event_message_handler.c:359 > #27 0x00007fffee8ab5b1 in efl_loop_message_handler_message_call > (obj=0x40000000141f, message=0x4000000c8bde) > at lib/ecore/efl_loop_message_handler.eo.c:14 > #28 0x00007fffee8a6229 in _efl_loop_message_process (obj=0x40000000001a, > pd=0x791a60) at lib/ecore/efl_loop.c:633 > #29 0x00007fffee8a641a in efl_loop_message_process (obj=0x40000000001a) at > lib/ecore/efl_loop.c:663 > #30 0x00007fffee89ea06 in _ecore_main_loop_iterate_internal > (obj=0x40000000001a, pd=0x791a60, once_only=0) > at lib/ecore/ecore_main.c:2450 > #31 0x00007fffee89c107 in _ecore_main_loop_begin (obj=0x40000000001a, > pd=0x791a60) at lib/ecore/ecore_main.c:1183 > #32 0x00007fffee8a49f8 in _efl_loop_begin (obj=0x40000000001a, pd=0x791a60) > at lib/ecore/efl_loop.c:83 > #33 0x00007fffee8a710f in efl_loop_begin (obj=0x40000000001a) at > lib/ecore/efl_loop.eo.c:28 > #34 0x00007fffee89c281 in ecore_main_loop_begin () at > lib/ecore/ecore_main.c:1266 > #35 0x00007ffff797c68a in elm_run () at lib/elementary/elm_main.c:1273 > #36 0x000000000041bf7e in elm_main (argc=1, argv=0x7fffffffdce8) at > ../../src/bin/main.c:432 > #37 0x000000000041c025 in main (argc=1, argv=0x7fffffffdce8) at > ../../src/bin/main.c:446 > > As seen here, clearly eflete is attempting to delete my homedir and this is > not a library issue. > > On Thu, Jul 5, 2018 at 9:18 AM Stefan Schmidt <ste...@datenfreihafen.org> > wrote: > > > hello. > > > > On 04.07.2018 20:09, Stefan Schmidt wrote: > > > Hello. > > > > > > On 27.06.2018 20:17, Mike Blumenkrantz wrote: > > >> See the weekly phab report mails which lists ticket/patch counts for > > high > > >> priority items. > > >> > > >> A number of the highest priority tickets will be resolved over the > next > > 24h > > >> as patches continue to land from the review queue. If people continue > to > > >> work on the high priority tickets which are tagged with the 1.21 > > milestone > > >> then it should be possible for Stefan to begin executing an alpha > > release > > >> very soon after he returns next week. > > > > > > I am back no and catched up on mails. > > > > > > Will go through the phab queries and phab in general tomorrow to get a > > > better understanding where we stand and when we can start the alpha. > > > > So here is how I see the situation regarding the release status. > > > > Following the pre-defined queries Mike uses in the phab weekly mails I > > can see 4 showstopper issues (2 of them them to have been dealt with > > already), 10 issues raised as prio high and 4 issues tagged as > regressions. > > > > This looks like a good enough starting point to me to get an alpha out > > and getting the remaining bugs fixed. If I compare this other releases I > > managed we started the alpha actually in a worse state. (If we would > > start the alpha with zero bugs we would not need one anyway. :-) > > > > My proposal from here would be the following: > > o I tag the alpha release tomorrow and prepare and upload tarballs > > o We asked packagers to try out these tarballs to get early feedback > > from them > > o We ask application maintainers to test their app against the alpha > > release and report bugs so we can still fix them (based on Hermet's > > suggestion) > > o I run abi-checker over the alpha release to see if it detects abi/api > > breaks we need to take care of > > o I will have a look if I can figure out whats wrong with our coverity > > builds. This is going on for a while, not sure I can promise that I will > > get this fixed in time. > > o We need to spent some extra time to make sure the > > home-dir-deleted-by-eflete bug is actually an application bug and > > nothing present in efl. > > > > The following are the issues I consider for the release right now. If > > you have one that is not listed here but should, please make sure to > > update the tags accordingly so its shows up in the queries. > > > > For showstopper and high prio issues: > > https://phab.enlightenment.org/maniphest/query/_jTUZLoOpCeA/#R > > > > For regressions: > > https://phab.enlightenment.org/maniphest/query/oP4HVQ1SXYSe/#R > > > > If you disagree with any of this speak up NOW. :-) > > > > regards > > Stefan Schmidt > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Regards, Hermet ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
