efl... thats elf spelled funny. they have pointy ears.

EFL = Enlightenment Foundation Libraries

https://www.enlightenment.org/about-efl

I maybe discovered a bug. Although I didn't install the right way so I guess it's probably invalid. This is the second time this has happened to me tho, so not a one time quirk.

[FYI - I just noticed the popup dialog for screenshot, first time using printscreen since new Moksha. ]

https://i.imgur.com/S9u4DXh.jpg

Both time this happened when I was using firefox (which of course is the app I run most often). Something weird about maximizing. If you see in the screenshot the title bar goes all the way across, but the firefox inner-window hasn't expanded to the whole window, and you can see my desktop thru it. I don't think there should be any way to cause this on purpose...

I don't know what I've done to cause it either time, just switching tabs and stuff. I'll pay attention in case it happens again, in case it does happen to be a real bug, I'll try to figure out how to repeat it. For all I know a firefox update happened recently too, I don't pay much attention as there's usually lots of things updating as I don't think of it all that often.

And while I'm at it... the other thing that's weird is conky, although I haven't spent any time on it.

I had it configured to go to the upper-right corner. Always worked fine. After this moksha, it goes to the upper left corner. I haven't touched .conkyrc in many months.

Will the next moksha version fix this attached error.

Right now, still access it through terminology by sudo synaptic.

1 members found this post helpful.

look for threads on policykit. that may be the problem.

settings ---- apps ---- startup apps and make sure policykit is added and active. should work and also maybe a reboot if it doesn't. i think that is what you need. sorry very busy out in the garden and vineyards.

That error has absolutely nothing to do with Moksha. It instead has to do with how one of our applications, esudo, is packaged and a conflict with this app and another application policy-kit. I did not package esudo so I am not responsible for the issues this causes. I would indeed like some kind of fix for the 5.1 release. I am just unsure what kind of fix would be best considering this is already a done deal. esudo is in our repo packaged as it is and after the fact it is not clear how to deal with the problems this causes when a policy-kit update overwrites it. As to fixing this now on your machine, there are multiple posts all over this forum with two different ways of addressing this issue.

1 members found this post helpful.

Oops, I should have known Moksha was unable to load something broke.

I do not remember the fix (within a month ago) I used to run synaptic normally, but it screwed up other programs, they stalled and loaded about minute later.

For now, just sticking with sudo synaptic to run it.

1 members found this post helpful.

it is fixable as such - you asked and we offered direction.

As of today Moksha 3.1 is now in the Bodhi linux 5.x main repo. Also efl stuff has been updated to efl 1.21.1. I had hoped to update to an efl 1.22 or even efl 1.23 but there seems to be an upstream problem causing moksha to segfault in certain situations. There should be no problems updating but if there is please report here or to me personally. To update/upgrade do the usual sudo apt update && sudo apt upgrade.

1 members found this post helpful.

robert - what kind of issues should i look for or run into? thanks my friend.

1 members found this post helpful.

I know of no known new issues upgrading to moksha 3.1 + efl 1.21.1. That doesn't mean they don't exist. But, for the record, moksha and some of our modules now have new settings and that can cause problems. It shouldn't as I think I have dealt with it all in the code properly. In case it does, you may need to delete your hidden ~/.e folder. I have did this upgrade multiple times on both hardware and virtual machines with no problems. So i don't anticipate the new settings will cause any issues. But if programmers could always anticipate issues with code then all software would be bug free

1 members found this post helpful.

ok great! thanks Robert!

1 members found this post helpful.