|
Post by Hippytaff on Dec 13, 2020 19:18:46 GMT
So after a few days trouble shooting with the assistance of ryenigma on Discord, we wittled it down and it turns out somewhere along the way 3d acceleration in virtualbox had been disabled, which meant the new comptonmod didn't work. The strange thing is the original comptonmod was working fine on that machine, as far as I was aware nothing had changed other than the module, but anyway, mystery solved.
|
|
|
Post by Hippytaff on Dec 13, 2020 21:01:33 GMT
For reference Vitualbox settings need to be as shown for comptonmod to do it's thing. Graphics controller: VMSVGA, 3D Acceleration: Checked.
|
|
|
Post by Hippytaff on Dec 14, 2020 11:49:32 GMT
I came across the issue of Compton module conflicting with the engage module. Steps to reproduce: 1) Enable Engage module in extensions. Move it anywhere. Like Top edge. 2) Then enable Compton module. 3) If issue doesn't appear immediately, then logout and login again. A black rectangular box appears around the engage bar. If we move the engage bar from top to bottom. Or left. The black rectangle seems to move along with it I am not sure if this has been reported before. Sorry if it has been already. Now that I’ve sorted my VB issues with comptonmod I’ll try to replicate and investigate this further. EDIT - I have had a play and it works fine with my current compton.conf. It plays up without a config file, and possibly the default config, but I haven't tested that yet. I've attached the config I am using. (courtesy of Enigma). It didn't seem to make a difference which module was turned on first, but after adding compton.config you will need to reload the module. Compton.conf It needs to be called compton.conf and it lives in: Let us know if it works for you. Cheers
|
|
nanini
Member
Posts: 8
Likes: 6
|
Post by nanini on Dec 14, 2020 20:45:08 GMT
Let us know if it works for you. Cheers I tried using the config above. Unfortunately it is more or less the same. It worked for some time when I had a pcmanfm window open. Suddenly as soon as I maximized the window it started again. It does seem to work on the desktop, but once we open any window it gets triggered again. During some other times, it works but upon logout and login it gets triggered again. Each time I kept reloading it. In only case in which Compton works correctly is when I disable the Engage dock altogether. So I have to choose. Either use Compton or use Engage, can't use both.
|
|
|
Post by ryenigma on Dec 14, 2020 23:19:54 GMT
nanini I am looking at your issues as well but I can't quite figure exactly what you are explaining. Is there a chance you can post a screen shot of this issue? Also I am assuming you are running Bodhi 5.1 but is it on a native system or under a virtual environment? On my virtual system it seems to be working just fine but I am willing to try it on metal if you can supply me with some more information. Thanks.
|
|
nanini
Member
Posts: 8
Likes: 6
|
Post by nanini on Dec 15, 2020 10:06:24 GMT
nanini I am looking at your issues as well but I can't quite figure exactly what you are explaining. Is there a chance you can post a screen shot of this issue? Also I am assuming you are running Bodhi 5.1 but is it on a native system or under a virtual environment? On my virtual system it seems to be working just fine but I am willing to try it on metal if you can supply me with some more information. Thanks. Hello I am using bodhi 6 on a native system. I used the above compton config provided. I was facing an issue, which you can see in the screenshot below. I figured out the issue. The problem was that somehow I had both compton as well as picom installed. Compton was from the previous installation. So I removed the installed compton and updated to the latest picom from github. Then logged out and reloaded compton module. And now the issue does not appear.
|
|
|
Post by Hippytaff on Dec 15, 2020 10:21:06 GMT
Glad you resolved the issue and Thanks for the update. 🙂
|
|
|
Post by thewaiter on Dec 15, 2020 12:46:31 GMT
Very interesting
The new compton module package was arranged to replace previous compton package and compton.conf with new picom package and its config. Anyway, I am also glad you sorted that out.
Stefan
|
|
sparkill
Member
bolivia
Posts: 39
Likes: 40
|
Post by sparkill on Jan 17, 2022 3:15:27 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... <button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button>
And I got rid of the shadow on conky by unchecking the first box here
<button disabled="" class="c-attachment-insert--linked o-btn--sm">Attachment Deleted</button>
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.
This solved my problem..
|
|