[SOLVED] efreetd error-message

Rosika · 01-08-2020, 07:05 AM

Hello cordx,

thank you so much for checking and reporting your results (and thanks also for the link).

Quote:

my dmesg results are exactly the same and my checkrestart are almost identical except that i have htop added to my list.

At least that´s good to know.

My journalctl didn´t give me any error-related messages regarding efreet either.
Thanks for the lnav-suggestion. I installed it and must say I´m really pleased with it. Very nice programme.

But neither does this one give me any clues regarding efreet or efreetd. It almost seems as if everything should be O.K.
The only thing mysterious is the error message which keeps popping up (but only once a day with the first start).

Anyway thank you a lot for putting so much time and effort into helping me. It´s much appreciated.

Have a nice day and many greetings.
Rosika

cordx · 01-08-2020, 04:00 PM

Rosika,

i was happy to help and am glad to hear that other than the error message and a slightly slower boot your system seems to be working well.

lnav has a nice feature where you can press e to go to the next error message or shift + e to move to the previous one. w does the the same for warnings.

a nice day and many greetings to you as well
cordx

Rosika · 01-09-2020, 06:15 AM

@cordx:

Thank you for the tips regarding lnav. Good to know.

Thankfully Bodhi works well in all the other respects. So this error-message seems to be a (minor) quirk at most.
Plus: only at first boot.

I´ll keep looking around for a little while longer though. If I encounter something worth investigating I´ll post it here.
As the efreetd-error seems to be connected to the phenomenon of slow boot I tend to go in that direction.

I found something on http://www.ubuntubuzz.com/2012/01/ho...u-booting.html .
Particularly this section:

Quote:

Speed Up Ubuntu Booting Time via Grub

here's to do it, open your grub configuration file (/etc/default/grub) and find this line GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”, do as follows :

sudo gedit /etc/default/grub

replace GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash” with GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash profile”.
save and exit
sudo update-grub2
sudo reboot

Grub does a search for all the necessary drivers to load, Instead of making Grub search for required drivers, the profiling actually makes Grub remember every necessary driver to work, This action will cutting down all of the driver load times.

after your system up, edit /etc/default/grub and remove some option which we have added before.

sudo gedit /etc/default/grub

replace GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash profile” with GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”.
save and exit
sudo update-grub2

Greetings.
Rosika

rbtylee · 01-10-2020, 02:55 PM

It seems people with slow computers sometimes have this issue. As i never do with moksha even on my older machines and running moksha in a VM I suspect other factors may be at play here. Regardless, I am going to increase the amount of time Moksha waits for this process to complete. Enlightenment (e23+) made this change recently and we will follow suit. So hopefully by next weekend or perhaps sooner I will update the Moksha version in the repos with this change and several others. If things go well and I don't note any major issues with Moksha in git.

Rosika · 01-11-2020, 07:36 AM

@rbtylee:

Hello and thank you for the effort.

Quote:

It seems people with slow computers sometimes have this issue.

Yes, I´m convinced by now that this is the main issue as the pop-up keeps complaining about this ("Is your system very slow on start [...]")

Quote:

I am going to increase the amount of time Moksha waits for this process to complete.

That would be great. Thanks.

In the meantime I followed the instructions given on http://www.ubuntubuzz.com/2012/01/ho...u-booting.html regarding increasing ubuntu booting time. I described them in my previous post.
Changing /etc/default/grub, rebooting and then changing it back might has given some improvement. But I´ll still have to test a bit more.

Anyhow my boot today for the first time didn´t result in giving me the efreetd-error-message.
But I´m still not quite sure about it as I encountered some difficulty in starting Bodhi today. Virt-manager gave me the message

Quote:

internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required

The VM was in a paused state and I could´t get it running again.

Yet I discovered that kvm was already running. "ps aux | grep -i kvm" indicated as much. So I killed the respective process and started the VM again. Everything was fine now.

I still don´t know how this came about but it´s working fine now.
I was mentioning this just to point out that today´s boot was a bit different. So I´ll be be able to tell you if boot-time has improved only at a later point.

Thanks for your help and I´ll keep you posted.

Greetings.
Rosika

rbtylee · 01-11-2020, 08:57 AM

Moksha has been updated. Perhaps I should have did more testing of some of the recent changes but hopefully there will be no problems.

I doubled the timeout for the efreet daemon. That should help with slower systems.

Rosika · 01-11-2020, 09:41 AM

@rbtylee:

Hi and thank your for updating moksha.

I´ve just logged into my Bodhi VM and and ran sudo apt-get update; and sudo apt-get upgrade.
And it worked. Moksha was updated. Thanks.

I rebooted and all went well.
But when running

Code:

 sudo  checkrestart -a

from the debian-goodies package I still get the following output:

Code:

lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
Found 3 processes using old versions of upgraded files
(3 distinct programs)
(3 distinct packages)
These processes (3) do not seem to have an associated init script to restart them:
moksha:
	851	/usr/bin/enlightenment
libefl-bin:
	852	/usr/bin/efreetd
pulseaudio:
	968	/usr/bin/pulseaudio

So moksha and libefl-bin still seem to be using old versions of upgraded files. But how can I restart them?
Or rather: What do I have to do, if anything?

Thanks in advance.

Greetings.
Rosika

rbtylee · 01-11-2020, 10:50 AM

Restart moksha from the menu if that concerns you. (it is under About Operating System) Or log out and log back in or reboot.

Rosika · 01-11-2020, 11:04 AM

@rbtylee:

Thanks for the help.
Yet neither of the methods worked. I still get the same output.

Nevertheless the latest moksha version seems to be installed now:

Code:

ii  moksha                              20200111bodhi30.3.1                       i386         Moksha Desktop

I just wanted to make sure it works and got a bit confused by the above-mentioned output of sudo checkrestart -a

So let´s hope for the best now.

Thanks again for all your help and effort.

I´m curious how the boot will work tomorrow. I´ll keep you posted.

Greetings.
Rosika

Rosika · 01-13-2020, 07:59 AM

@all:

I think it´s more or less safe by now to tell you that the measures taken seemed to have worked well.
On two different days I started Bodhi in my VM and didn´t get the efreetd-error message. That´s really great.

So thank you very much for the help and thank you @rbtylee for increasing the amount of time Moksha waits for this process to complete.

On a sidenote:

As far as checkestart is concerned I think all is good now. I looked up the manpages and the option "-a" with which I started the command is described as:

Quote:

-a, --all
Process all deleted files regardless of location. This makes the
program analyse deleted files even if they would be discarded
because they are located in locations, such as /tmp , which are
known to produce false positives. [...]

So I used the command without the "-a" parameter and got this output:

Code:

 sudo checkrestart
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
Found 0 processes using old versions of upgraded files

So it seems everything is fine now.

Thanks again all of you for your phantastic help. It´s much appreciated.

Greetings.
Rosika