tint2 wrong position

knarh · 2023-07-22 09:18:30

Hello,
In fluxbox tint2 shows up in wrong place.
Using standart tint2 config: http://0x0.st/HeMs.txt

When it must be at the bottom, panel shows up in the top, but when panel width is not 100% , all works fine. screen: http://0x0.st/HeM-.png

When panel must be in the top, it's a little lower than it must be, but when panel width is not 100% all works fine too. screen: http://0x0.st/HeMo.png

With openbox all works great. Where's can be a problem?

thanks in advance

seth · 2023-07-22 12:56:22

Post the output of "xrandr -q" and "xwininfo" and "xprop" for the tint2 window (the cursor turns int a "+" for the latter and you can simply click the window to get the output)

Edit: oviously when the window is apparently mislocated.

Last edited by seth (2023-07-22 12:56:49)

knarh · 2023-07-22 13:11:56

xrandr -q: http://0x0.st/Heum.txt
xwininfo: http://0x0.st/Heua.txt
xprop: http://0x0.st/HeuB.txt

bar must be at the bottom, shows at the top

seth · 2023-07-22 13:32:46

This looks all ok, but I missed the fluxbox part.
Can you control the docks position via the slit config (in the rmb menu)

knarh · 2023-07-22 13:38:42

Can you control the docks position via the slit config

I didn't get the point but I can control toolbar position

upd: fluxbox's toolbar

Last edited by knarh (2023-07-22 13:39:26)

seth · 2023-07-22 13:42:04

Fluxbox has two dock-a-like things. It's toolbar and a container (the slit) that can capture other docks.
If you right-click the desktop, you should get a menu, fluxbox/configure/slit
https://man.archlinux.org/man/extra/flu … n#THE_SLIT
You can also try to run "fluxbox -no-slit"

knarh · 2023-07-22 13:46:45

I ran with -no-slit flag - nothing changed

I can control slit position but it does nothing

seth · 2023-07-22 14:09:43

So it's not captured. (Just checked, xprop/wininfo also detect the slit, not the embedded window)

What if you run "fluxbox -no-toolbar -no-slit"?

knarh · 2023-07-22 14:32:29

What if you run "fluxbox -no-toolbar -no-slit"?

nothing changed

I figure out that can I use shrink option and all works somehow, but I'm dissatisfied, so if you want - I can mark solved.

UPD: It can be a part of dock, so configuring slit position via fluxbox - configuring position of the bar, so it works somehow x2

Last edited by knarh (2023-07-22 14:41:30)

seth · 2023-07-22 15:25:51

panel_shrink just leads to a smaller panel (in the best of cases), so that's just the original workaround.
But this is reproducible and the strut is actually on the wrong edge (struts bottom, places top)
Then I disabled the struts:

strut_policy = none

…

At the same time, I cannot control the position at all.
panel_position = bottom center horizontal
panel_position = top center horizontal
panel_position = botttom left horizontal

The panel always shows up on the top or the left w/ strut_policy = none and w/ strut_policy = follow_size it's reverse, ie. top is bottom and bottom is top.
I think tint2 is pretty much self confused about its strutting and misplaces itself.

xdotool search --sync --class Tint2 windowmove 0 0 &
tint2 > /dev/null 2>&1

will wait until tint2 shows up and move it to the topleft corner of the root window.

xdotool search --class Tint2 windowmove 0 0

knarh · 2023-07-23 02:51:23

So, it is a solution?

xdotool search --sync --screen 0 --class Tint2 windowmove 0 1400 &

(1400 in my case)

upd: if i run tint2 like this

xdotool search --sync --screen 0 --class Tint2 windowmove 0 1400 &
DISPLAY=:0.0 tint2  &

there is a delay between starting tint2 and it's movement, can it be fixed?
(it starts - shows up and then moves)

Last edited by knarh (2023-07-23 04:01:41)

seth · 2023-07-23 06:48:22

No, you (or rather xdotool) has to wait for the window to show up before it can move it.
You probably want to file a bug against tint2 - why it adds proper struts but the moves itself to the wrong location - and only for some WMs - is beyond me (just as much as the non-strutting behavior)

One thing I noticed here as well is that it asks the WM to put it into an offscreen spot:

program specified location: -368, -1

and - in case it relies on that rather than placing itself - WMs will apply different sanitizing measures on such attempts (assuming the client is malicious or stupid)
So that might be a factor.

Arch Linux

#1 2023-07-22 09:18:30

tint2 wrong position

#2 2023-07-22 12:56:22

Re: tint2 wrong position

#3 2023-07-22 13:11:56

Re: tint2 wrong position

#4 2023-07-22 13:32:46

Re: tint2 wrong position

#5 2023-07-22 13:38:42

Re: tint2 wrong position

#6 2023-07-22 13:42:04

Re: tint2 wrong position

#7 2023-07-22 13:46:45

Re: tint2 wrong position

#8 2023-07-22 14:09:43

Re: tint2 wrong position

#9 2023-07-22 14:32:29

Re: tint2 wrong position

#10 2023-07-22 15:25:51

Re: tint2 wrong position

#11 2023-07-23 02:51:23

Re: tint2 wrong position

#12 2023-07-23 06:48:22

Re: tint2 wrong position

Board footer