Small terminal is briefly rendered in the center of the foot window on startup #1211

steven3k commented 2022年11月05日 14:51:14 +01:00

Hello,
I am using sway as a window compositor and I have small annoyance when using foot.

For some reason, when foot is launched, a smaller terminal is rendered in the center of the window for a split second. The rest of the window show the underlying desktop background (so it's probably transparent?).
Moments later the window is properly placed in its designated area of the screen.

This causes a really annoying screen flickering effect every time that foot is launched. I don't know if this is due to sway or foot but other apps/terminal emulators do not exhibit this behavior, so I'm tentatively reporting the bug angainst foot.

There are some additional oddities:

• This does not happen on my laptop monitor (eDP-1 in the following), while it happens consistently on my external 144Hz monitor (DP-1). This made me suspect that it might be related to the refresh rate, but loweing it made no difference.

• This does not usually happen if there is another instance of foot currently being executed (on any workspace)... execpt if I'm recording the output with wf-recorder (in which case it happens often).

• I tried playing around with resize-delay-ms, delayed-render-lower, delayed-render-upper, initial-window-mode, alpha, and the client/server side decorations settings but nothing made a difference.

• This happens both when using a standalone instance of foot and when using footclient.

Issue #453 looks somewhat similar, although it is talking about the client application rather than the window rendered by foot.
Maybe this is related to https://github.com/swaywm/sway/issues/2176 (but somehow other terminal emulators show up properly).

I'm using foot version: 1.13.1 +pgo +ime +graphemes -assertions and sway 1.7.
Here is the output of wlr_randr:

$ wlr-randr 
eDP-1 "Unknown 0x403D 0x00000000 (eDP-1)"
 Physical size: 310x170 mm
 Enabled: yes
 Modes:
 1920x1080 px, 60.049000 Hz (preferred, current)
 Position: 0,0
 Transform: normal
 Scale: 1.000000
DP-1 "Goldstar Company Ltd LG ULTRAGEAR 208MAYYG5C82 (DP-1 via DP)"
 Physical size: 600x340 mm
 Enabled: yes
 Modes:
 640x480 px, 59.939999 Hz
 640x480 px, 59.939999 Hz
 640x480 px, 60.000000 Hz
 720x480 px, 59.939999 Hz
 720x480 px, 60.000000 Hz
 720x576 px, 50.000000 Hz
 800x600 px, 60.317001 Hz
 1024x768 px, 60.004002 Hz
 1280x720 px, 50.000000 Hz
 1280x720 px, 59.939999 Hz
 1280x720 px, 60.000000 Hz
 1920x1080 px, 50.000000 Hz
 1920x1080 px, 59.939999 Hz
 1920x1080 px, 60.000000 Hz
 1920x1080 px, 60.000000 Hz
 1920x1080 px, 119.879997 Hz
 1920x1080 px, 120.000000 Hz
 2560x1440 px, 59.951000 Hz
 2560x1440 px, 99.945999 Hz
 2560x1440 px, 119.998001 Hz
 3840x2160 px, 23.976000 Hz
 3840x2160 px, 24.000000 Hz
 3840x2160 px, 25.000000 Hz
 3840x2160 px, 29.969999 Hz
 3840x2160 px, 30.000000 Hz
 3840x2160 px, 50.000000 Hz
 3840x2160 px, 59.939999 Hz
 3840x2160 px, 60.000000 Hz
 2560x1440 px, 143.998993 Hz (preferred, current)
 Position: 1920,0
 Transform: normal
 Scale: 1.000000

Here is my foot.ini

font=monospace:size=14
dpi-aware=no
pad=4x4
[bell]
urgent=yes
[colors]
alpha=0.9
[cursor]
color=111111 cccccc
[colors]
foreground=dddddd
background=000000
regular0=000000 # black
regular1=cc0403 # red
regular2=19cb00 # green
regular3=cecb00 # yellow
regular4=0d73cc # blue
regular5=cb1ed1 # magenta
regular6=0dcdcd # cyan
regular7=dddddd # white
bright0=767676 # bright black
bright1=f2201f # bright red
bright2=23fd00 # bright green
bright3=fffd00 # bright yellow
bright4=1a8fff # bright blue
bright5=fd28ff # bright magenta
bright6=14ffff # bright cyan
bright7=ffffff # bright white
[tweak]
font-monospace-warn=no

The attached sreencast showcases the issue and I've extracted three sets of three frames. x1.jpg shows the situation just before foot is launched, x2.jpg shows the smaller terminal being rendered inside the foot window, and x3.jpg shows the foot window a few instants later.

Hello, I am using sway as a window compositor and I have small annoyance when using foot. For some reason, when foot is launched, a smaller terminal is rendered in the center of the window for a split second. The rest of the window show the underlying desktop background (so it's probably transparent?). Moments later the window is properly placed in its designated area of the screen. This causes a really annoying screen flickering effect every time that foot is launched. I don't know if this is due to sway or foot but other apps/terminal emulators do not exhibit this behavior, so I'm tentatively reporting the bug angainst foot. There are some additional oddities: - This does not happen on my laptop monitor (eDP-1 in the following), while it happens consistently on my external 144Hz monitor (DP-1). This made me suspect that it might be related to the refresh rate, but loweing it made no difference. - This does not usually happen if there is another instance of foot currently being executed (on any workspace)... execpt if I'm recording the output with wf-recorder (in which case it happens often). - I tried playing around with resize-delay-ms, delayed-render-lower, delayed-render-upper, initial-window-mode, alpha, and the client/server side decorations settings but nothing made a difference. - This happens both when using a standalone instance of foot and when using footclient. Issue #453 looks somewhat similar, although it is talking about the client application rather than the window rendered by foot. Maybe this is related to https://github.com/swaywm/sway/issues/2176 (but somehow other terminal emulators show up properly). I'm using `foot version: 1.13.1 +pgo +ime +graphemes -assertions` and sway 1.7. Here is the output of wlr_randr: ~~~ $ wlr-randr eDP-1 "Unknown 0x403D 0x00000000 (eDP-1)" Physical size: 310x170 mm Enabled: yes Modes: 1920x1080 px, 60.049000 Hz (preferred, current) Position: 0,0 Transform: normal Scale: 1.000000 DP-1 "Goldstar Company Ltd LG ULTRAGEAR 208MAYYG5C82 (DP-1 via DP)" Physical size: 600x340 mm Enabled: yes Modes: 640x480 px, 59.939999 Hz 640x480 px, 59.939999 Hz 640x480 px, 60.000000 Hz 720x480 px, 59.939999 Hz 720x480 px, 60.000000 Hz 720x576 px, 50.000000 Hz 800x600 px, 60.317001 Hz 1024x768 px, 60.004002 Hz 1280x720 px, 50.000000 Hz 1280x720 px, 59.939999 Hz 1280x720 px, 60.000000 Hz 1920x1080 px, 50.000000 Hz 1920x1080 px, 59.939999 Hz 1920x1080 px, 60.000000 Hz 1920x1080 px, 60.000000 Hz 1920x1080 px, 119.879997 Hz 1920x1080 px, 120.000000 Hz 2560x1440 px, 59.951000 Hz 2560x1440 px, 99.945999 Hz 2560x1440 px, 119.998001 Hz 3840x2160 px, 23.976000 Hz 3840x2160 px, 24.000000 Hz 3840x2160 px, 25.000000 Hz 3840x2160 px, 29.969999 Hz 3840x2160 px, 30.000000 Hz 3840x2160 px, 50.000000 Hz 3840x2160 px, 59.939999 Hz 3840x2160 px, 60.000000 Hz 2560x1440 px, 143.998993 Hz (preferred, current) Position: 1920,0 Transform: normal Scale: 1.000000 ~~~ Here is my foot.ini ~~~ font=monospace:size=14 dpi-aware=no pad=4x4 [bell] urgent=yes [colors] alpha=0.9 [cursor] color=111111 cccccc [colors] foreground=dddddd background=000000 regular0=000000 # black regular1=cc0403 # red regular2=19cb00 # green regular3=cecb00 # yellow regular4=0d73cc # blue regular5=cb1ed1 # magenta regular6=0dcdcd # cyan regular7=dddddd # white bright0=767676 # bright black bright1=f2201f # bright red bright2=23fd00 # bright green bright3=fffd00 # bright yellow bright4=1a8fff # bright blue bright5=fd28ff # bright magenta bright6=14ffff # bright cyan bright7=ffffff # bright white [tweak] font-monospace-warn=no ~~~ The attached sreencast showcases the issue and I've extracted three sets of three frames. `x1.jpg` shows the situation just before foot is launched, `x2.jpg` shows the smaller terminal being rendered inside the foot window, and `x3.jpg` shows the foot window a few instants later.

steven3k commented 2022年11月05日 18:14:01 +01:00

I managed to solve the issue by setting initial-window-size-pixels to the size of my screen.

Perhaps the initial window size could be detected by default when not explicitly set? This would have the benefit of working nicely on screen of all sizes without needing to set an upper bound in the config file.

I managed to solve the issue by setting `initial-window-size-pixels` to the size of my screen. Perhaps the initial window size could be detected by default when not explicitly set? This would have the benefit of working nicely on screen of all sizes without needing to set an upper bound in the config file.

dnkl commented 2022年11月06日 10:17:03 +01:00

Duplicate: #1133
Upstream issue: https://github.com/swaywm/sway/issues/2176

There could be several reasons this doesn't always, or never, show up in other applications. For example, it could depend on how "agressively" the terminal emulator starts the child process (i.e. the shell).

The bottomline is it's timing dependent. The actual bug is https://github.com/swaywm/sway/issues/2176.

Setting the initial window size to the screen size is not an option since it'll look really bad on stacking compositors.

Since this is a known Sway bug, I don't think it makes sense to add workarounds to foot. Not when there already is one available (i.e. explicitly setting the initial window size).

Duplicate: https://codeberg.org/dnkl/foot/issues/1133 Upstream issue: https://github.com/swaywm/sway/issues/2176 There could be several reasons this doesn't always, or never, show up in other applications. For example, it could depend on how "agressively" the terminal emulator starts the child process (i.e. the shell). The bottomline is it's timing dependent. The actual bug **is** https://github.com/swaywm/sway/issues/2176. Setting the initial window size to the screen size is not an option since it'll look really bad on stacking compositors. Since this is a known Sway bug, I don't think it makes sense to add workarounds to foot. Not when there already is one available (i.e. explicitly setting the initial window size).