I just started getting this error message popping up in Terminal:
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

Currently I'm working on the Japan Theme and it's started printing this message after I run a build of the default.edc file and install the theme. As far as I can tell, it's harmless and the system runs ok, but I don't like sudden unexplained messages....

It's a newly built 32-bit version 5.0 system, running under Virtual Box 6 on a Mac.

My first guess was that it's caused by some error I introduced into the theme, but rolling back today's changes doesn't make it go away. And the edje_cc compiler doesn't come up with any error messages, just some warnings which have been there for months.

Presumably more information is logged somewhere, but I don't know where to look.

Any ideas, please?

or

might show more of what is going on.

1 members found this post helpful.

Problem solved! I'd set up a script to compile/build the Japan profile I'm working on, and automatically copy the "edc" file to the themes folder. Sometimes, just doing this copy was sufficient to trigger Moksha into doing a reset and immediately display the updated theme, but on other occasions the copy just took place silently with no reset. So, I added an explicit Moksha reset as the last line of the command file. Of course, this often meant two Moksha resets in rapid succession, but I was fine with that.

For weeks, this has worked just fine; however, in the last day or two I just started getting the error messages. It appears that the system is now complaining if the command file triggers a second reset whilst the first one is still taking place. Why it should suddenly object to this beats me, but fortunately there's a simple fix. I put a sleep just after the copy to the theme folder, so that if the copy should trigger a reset, that reset will have finished by the time the second reset takes place. It slows down the build by a few seconds but I'm ok with that.