|
Post by ylee on Dec 9, 2020 20:13:26 GMT
The moksha module comptonmod has been updated in Bodhi linux's 5.x repo. The new version now uses picom a compton fork as compton appears to unmaintained these days. As a result picom is also present in the BL5 repo.
|
|
|
Post by thewaiter on Dec 9, 2020 20:21:41 GMT
Hello I used the picom.conf example from the project git for our module Feel free to modificate it in: /usr/lib/x86_64-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 64 bit installation or /usr/lib/i386-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 32 bit installation Enjoy
|
|
|
Post by thewaiter on Dec 9, 2020 20:35:02 GMT
...and of course, big thanx to ylee for making both packages, picom and module.
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Dec 9, 2020 21:16:32 GMT
A couple notes if you already have comptonmod installed: you must use dist-upgrade not just regular update or it is skipped, and doing so removes the old compton package but forgets to remove its desktop file.
sudo apt update
sudo apt dist-upgrade
sudo rm /usr/local/share/applications/compton.desktop
|
|
|
Post by Hippytaff on Dec 9, 2020 22:05:56 GMT
I had strange behaviour with terminology after updating to this mod in vm. No right click to settings Translucent was acting strangely etc...
|
|
|
Post by thewaiter on Dec 10, 2020 6:46:58 GMT
Very weird. Let me check the conf. Interesting is, I upgraded the module in my daughter's laptop without any troubles.
Stefan
|
|
|
Post by Hippytaff on Dec 10, 2020 10:27:43 GMT
Very weird. Let me check the conf. Interesting is, I upgraded the module in my daughter's laptop without any troubles. Stefan I'll check to see if I've not deleted the old comptonmod config as you suggest, and maybe I'll reinstall it after cleaning out the old compton files. There's probably some kind of conflict going on between old and new. I'll let you know
|
|
|
Post by Hippytaff on Dec 10, 2020 15:21:48 GMT
The issue was in a VM where I'd also been messing around with different kernels and other experimental stuff, so it might not be that upgrading comptonmod broke moksha, there are other possible contributing factors. Ive set up a new VM and I'll see if I can replicate it on a fresh install.
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Dec 10, 2020 16:17:21 GMT
Hello I used the picom.conf example from the project git for our module Feel free to modificate it in: /usr/lib/x86_64-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 64 bit installation or /usr/lib/i386-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 32 bit installation FYI, anyone who wants to try another default without learning details of confugiring, just delete that file. I find I like internal defaults better after testing for a day, but of course I could go tweak individual settings if I want too. With the module provided config file, it did things like add a shadow to the right of conky and make all windows besides current one translucent, it disables the tranlucenty I'd specified in terminology, even things like a right-click menu that comes up would turn the whole app translucent and then I'd see apps behind it and desktop all at once, and I didnt like this behavior. The only reason I used compositor in the first place is for translucent conky and terminal and this works with internal default settings for me.
|
|
|
Post by Hippytaff on Dec 10, 2020 16:33:23 GMT
Hello I used the picom.conf example from the project git for our module Feel free to modificate it in: /usr/lib/x86_64-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 64 bit installation or /usr/lib/i386-linux-gnu/enlightenment/modules/comptonmod/compton.conf for 32 bit installation FYI, anyone who wants to try another default without learning details of confugiring, just delete that file. I find I like internal defaults better after testing for a day, but of course I could go tweak individual settings if I want too. With the module provided config file, it did things like add a shadow to the right of conky and make all windows besides current one translucent, it disables the tranlucenty I'd specified in terminology, even things like a right-click menu that comes up would turn the whole app translucent and then I'd see apps behind it and desktop all at once, and I didnt like this behavior. The only reason I used compositor in the first place is for translucent conky and terminal and this works with internal default settings for me. Same here, conky and translucent terminology is all I need it for. Maybe it should ship without the config file? Anyway, thanks for the research.
|
|
|
Post by thewaiter on Dec 10, 2020 18:18:16 GMT
Of course yes. I played just briefly with the conf file. If you have the better one, send me. I will place to my git and I will ask Ylee again for newer package...
Thx
Stefan
|
|
|
Post by Hippytaff on Dec 10, 2020 18:25:50 GMT
Or just internal defaults as the waiter suggested. So no conf file, or even better an example conf file thats not active?
|
|
|
Post by thewaiter on Dec 10, 2020 18:53:27 GMT
Hmmm, module without any conf? Not confusing? At least I would like to have a border drop shadow...
S
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Dec 11, 2020 1:33:32 GMT
I am still learning this myself as I'd never played before, but some might fine this GUI useful. It seems to not like the path moksha uses, so I kinda had to do a wierd workaround with links, please tell me if there is a better way to do this, but it works.... I went back to the config included with the module then changed the background opacity to 1 in unused windows,that was the change that I couldn't quite get used to... now it'll be eaiser to play with more settings...
And I got rid of the shadow on conky by unchecking the first box here
sudo apt install compton-conf sudo mv /usr/lib/x86_64-linux-gnu/enlightenment/modules/comptonmod/compton.conf ~/.config sudo chown $USER ~/.config/compton.conf sudo ln -s ~/.config/compton.conf /usr/lib/x86_64-linux-gnu/enlightenment/modules/comptonmod
Then unload/load comptonmod. Then run compton-conf. When you click apply, changes will then be immediate.
|
|
|
Post by Hippytaff on Dec 11, 2020 14:34:43 GMT
ok, so there are more config files for Terminology than I thought. Purging didn't get rid of them, though I thought that was the whole point of purge, so shows how much I know. So if new comptonmod kills terminology and as a result the whole desktop when you try and get a translucent terminology, uninstall it and get rid of ALL of the configs. I couldn't access TTY when I was fixing this, so I just about managed to install xterm by hoping I was pressing the right keys,...You can use: to find the config files that need deleteing, then reinstall it.
Doesn't solve my none translucent terminology issue though dagnamit. It's just my VM one though, os no biggie
|
|