Video: MX Compton Manager

[Richard]

Pardon the intrusion, but it seems like Compton GUI is an application;
therefore, when the application stops, the effects stop.

Is it supposed to be a daemon?
Then it should keep running?

Sorry, back to my knitting.

[linexer2016]

Tried once again and this time I ensured I had clicked solidly on the Launch button in the GUI and because I did not close or stop the GUI, the terminal now says ...
mx-compton
Home Path = "/home/xxxx"
Autostart status is "true"
Found existing conf file
Compton is NOT running
Compton is NOT running
compton 4699
Compton is running

[linexer2016]

Richard, I am sure DO and I don't think you are intruding at all so don't feel obliged to go back to your knitting

[dolphin_oracle]

Tried once again and this time I ensured I had clicked solidly on the Launch button in the GUI and because I did not close or stop the GUI, the terminal now says ...
mx-compton
Home Path = "/home/xxxx"
Autostart status is "true"
Found existing conf file
Compton is NOT running
Compton is NOT running
compton 4699
Compton is running

Ok, so close the gui and then restart it from the command line (mx-compton)

[linexer2016]

DO, it seems to me that there's some mixup or conflict in the way the GUI is invoked from the Terminal versus Recently Used from the start button because depending on how one sets out to invoke the app, one gets a different end result
You see DO, if I exit the terminal screen and (as you've suggested) go into another terminal and type mx-compton that results in a pop up of the GUI resplendent with the Launch button. As I've mentioned, that's the starting point of the saga

[dolphin_oracle]

DO, it seems to me that there's some mixup or conflict in the way the GUI is invoked from the Terminal versus Recently Used from the start button because depending on how one sets out to invoke the app, one gets a different end result

should be exactly the same. the desktop file the menu uses just runs "mx-compton".

[linexer2016]

You see DO, if I exit the terminal screen and (as you've suggested) go into another terminal and type mx-compton that results in a pop up of the GUI resplendent with the Launch button. As I've mentioned, that's the starting point of the saga

[dolphin_oracle]

You see DO, if I exit the terminal screen and (as you've suggested) go into another terminal and type mx-compton that results in a pop up of the GUI resplendent with the Launch button. As I've mentioned, that's the starting point of the saga

did the terminal outpu report that compton wasn't running?

what does

Code: Select all

ps -aux |grep compton

give you?

BTW, all this has already made the script better. I'm trying to hone in on the compton launch issue. That's the meat of it I think.

[linexer2016]

No the terminal output said Compton was not running after I closed the GUI ...

ps -aux |grep compton
xxxx 5274 0.0 0.0 48660 2100 pts/0 S+ 01:34 0:00 grep compton

[linexer2016]

DO, could something be amiss in the .conf file? I've not changed the default conf file although I do use Conky 2 and it appears in there.