When I boot into 32-bit Bodhi 5.1 Legacy (clean installation, virtual machine), I get the following error window from efreetd:
https://i.postimg.cc/TPvyBwy6/shot-2...3-16-00-18.jpg

This happens only in 32-bit Bodhi 5.1 Legacy; there's no such error when I boot into Bodhi 5.1 Standard (64-bit).

The error looks rather harmless, by the way: when I simply close the error window, everything seems to be working alright.

The error is harmless. And a known Issue. Currently it is unknown why specifically this occurs sometimes. It is not necessarily related to cpu arch or computer resources or any other factor I have identified. Efreet is a part of efl and this appears to be an efl issue. It has happened on some systems since before we forked moksha from e17. And for the record users of e23 also sometimes get the same error msg. Seems to be reported more and by more Bodhi users lately. Perhaps due to other changes in EFL. Sadly I can not duplicate it on any machine I have. Makes it a pain for me to try to debug.

However, at some point I do need to address this issue even if it is just to suppress the user from seeing the error dialog. I have one more efreet issue to debug (unrelated to this one) and Raster has suggested I generate some comprehensive backtraces and spent hours in gdb trying to understand it. I put that on hold since I was focusing on the new release and hrs in gdb tracking function calls thru EFL code could easily eat up days if not weeks on my time.

But it needs done and when i get to it I will also look and see if i can see any reason of the efreetd error msgs some users are getting.

1 members found this post helpful.

Thanks. It's only a "paper cut" though; a minor cosmetic issue without practical relevance. Not worth spending much time on, especially since it happens only in some cases....

Perhaps you could add a section "Known Issues" to the release announcement, and mention it in that section?

I've also got that message on my 5.1 legacy about slow start etc; don't recall ever getting it on 5.0. In the past I've got the efreet cache error but I've learned to ignore that one.

Since doing system update this weekend.
32 Bit Legacy on an old Dell Inspiron 5150.
Will simply ignore for now.

Am running Bodhi 5.1.0 (AppPack release) and this Efreet cache error has suddenly started happening.
Been running Bodhi for a few weeks without this error, and now it pops up whenever I login (seems
random too - maybe 50% of the time!) My PC does not have EUFI BIOS and I don't use EFI - at least
I don't explicitly choose EFI during installation/setup, if I get asked where to install GRUB/GRUB2
by the OS installer I just select the boot HDD/MBR. as mentioned before, I know I can just click 'OK'
to dismiss the error, but it can take about 10-20 seconds for it to go away before the rest of the
desktop loads up. I read somewhere after doing a quick google for the error message (specifically
referring to E17 issues) something about the cache folder needing to be deleted by the OS whenever
you reboot or shutdown system? If this folder doesn't get removed, can this cause this error to
manifest? I can't remember if I only started seeing this message after my system crashed
(causing me to unplug power to restart) which would mean the offending folder didn't get removed?

@slickmrick the efreet cache error is different. I get that one intermittently too on 64-bit, and have been getting it as long as I remember, maybe even 4.5, and deleting the efreet cache fixes it for a while. But this other one about slow start is new to me with 5.1, and so far only on legacy, and deleting the cache doesn't seem to affect it.