bl-tint2-session

hhh · 2016-07-19 05:37:46

Something's not kosher. Compare...

Open a terminal and pkill tint2
Alt+F2 and Run tint2
Look at the network manager Faenza icon
root-menu>Preferences>tint2>Restart tint2
???

Why does the icon change apprearance? Why all the flickering and why do the applets rearrange? Also, compositing should be started before tint2, so we shouldn't restart compositing at the end...
https://gitlab.com/o9000/tint2/issues/494

This also affects our autostart, compare rebooting/logging in using tint2 v bl-tint2-session...
https://forums.bunsenlabs.org/viewtopic … 850#p32850

-edit- Ah, the restart command is it's own script, but the behavior seems the same as tint2 startup.

Head_on_a_Stick · 2016-07-19 06:42:29

hhh wrote:

why do the applets rearrange?

Because of https://github.com/BunsenLabs/bunsen-co … nt2rc#L137

I always change that to "ascending" 'cos it annoys me.

I will test the others tonight, in OpenBSD atm.

johnraff · 2016-07-19 07:05:28

hhh wrote:

Why does the icon change apprearance? Why all the flickering and why do the applets rearrange?

I don't get any of that. Everything looks normal. I think a certain amount of applet reordering is to be expected if they're just loaded in as they start up.

EDIT ah for me the dropbox icon loses its background transparency after a restart with the restart script, but not with 'pkill tint2;tint2'
It seems to be the 'bl-compositor --restart' which does it.
EDIT2 confirmed - restarting compton causes the trouble. Tint2 clearly needs to be started after compton.

Last edited by johnraff (2016-07-19 07:47:08)

damo · 2016-07-19 07:51:05

^ Confirmed.

...and found a bl-compositor "bug". I'll raise an issue on github.

johnraff · 2016-07-19 08:26:43

Also please see https://forums.bunsenlabs.org/viewtopic … 861#p32861

hhh · 2016-07-19 12:14:37

https://forums.bunsenlabs.org/viewtopic … 870#p32870

Removing "bl-compositor --restart" from our tint2 scripts solves everything for me.

johnraff · 2016-07-20 04:10:44

^ That looks like the solution, plus adding a call to bl-tint2restart to the compositor restart code, to make sure tint2 is always started after compton.

johnraff · 2016-07-22 04:55:02

^Those changes are now pushed to the deuterium branches of bunsen-utilities and bunsen-pipemenus.

#1 2016-07-19 05:37:46

bl-tint2-session

#2 2016-07-19 06:42:29

Re: bl-tint2-session

#3 2016-07-19 07:05:28

Re: bl-tint2-session

#4 2016-07-19 07:51:05

Re: bl-tint2-session

#5 2016-07-19 08:26:43

Re: bl-tint2-session

#6 2016-07-19 12:14:37

Re: bl-tint2-session

#7 2016-07-20 04:10:44

Re: bl-tint2-session

#8 2016-07-22 04:55:02

Re: bl-tint2-session

Board footer