I had this issue yesterday and Deepspeed helped me with it and asked me to put a self-fix post on the forums.
After running eepDater I received the following error message upon restart:
I had the same error message for the module engage.
It seems the naming can get mixed up on update and the workaround appears to be correctly naming the directory that the module.so file is located in.
The path to the module.so on my system is:
Although on other systems it can be:
A good search to get the correct path is to enter the following at a command prompt:
cd /usr/lib/*linux-gnu/enlightenment/modules or: cd /usr/local/lib/enlightenment/modules
Once you have cd'd into the correct enlightenment modules directory you can ls at a command prompt to see the available directories. One of them should be the module that the error message says can't be found. In my case ecomorph and engage, although it could be any module.
Cd into the correct module and ls to see what directories are located there. There should be a directory that begins with linux-gnu and ends in 0.1.0 in my case it was linux-gnu-x86_64-0.1.0. This directory needed to be renamed to linux-gnu-x86_64-0.17.6 in my case.
A quick way to rename this directory is to use the mv command:
sudo mv linux-gnu-x86_64-0.1.0 linux-gnu-x86_64-0.17.6
There should be a space between the directory names and it is possible to use Ctl+Shift+c to copy and Ctl+Shift+v to paste in terminology.
This has solved both of my problems. I have intentionally made these instructions usable for people who might be newer to terminal commands, I hope it isn't too long.
- Charles@Bodhi likes this