Black strip at the bottom #254
Comments
|
Had the same problem trying to run Try running For foot it's It'd be nice if cage itself had an option likegamescope's |
|
Under Wayland, clients are required to obey the size configured by the compositor when maximized. Maybe alacritty doesn't? Maybe Cage sends the wrong size somehow? |
|
the apps take up the full available space when running in a nested sway session, so it seems like a cage problem |
|
fullscreen mode seems to fix this, but it's not the terminal size after all. the black bar stays the same size when resizing cage |
|
this occurs with foot and alacritty, but not with contour or blackbox, so it's not an issue with every terminal application also, alacritty works as expected when running in x11 mode |
|
I have just tested foot terminal in Cage and it seems the issue is with XDG decoration. When When foot has to draw its decoration client-side, it also calls xdg_surface:request:set_window_geometry() with x = 0 and y = -26 i.e. the size of decoration bar. However, I feel it should be better to handle surface geometry in surface commit but these parts are still a bit obscure for me. |
|
shouldn't disabling client-side decor be the default? since cage is a kiosk (and the -d option works for alacritty too) |
|
@Dareka826, I don't know if disabling client-side decoration should be the default or not. |
|
@joggee-fr, foot now displays a titlebar, but alacritty crashes Alacritty crash log: |
|
The following line is suspicious: Looking at this issue pointing to this comment |
|
Gentle ping, @Dareka826? |
|
Must've been an issue with the build of alacritty I was using, because after testing again your patch works just fine. Back then I was using alacritty-sixel-git from the AUR. |
|
it works now on both my distro's alacritty and a fresh build of alacritty-sixel, so it probably was just as you said, an old version of the toolkit they used. |
|
Thanks for your feedback @Dareka826. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is the strange black strip at the bottom of program launched in cage. See screen photos:
Running alacritty (virtual terminal) in cage in vt (click to show the screen photo)
Running alacritty in cage in weston (click to show the screen photo)
I am sure that this is the problem of cage, not alacritty, because:
An interesting thing:
it seems that the input events work in the area of the black strip, but very strange. For example, let's try to select some text in alacritty:
There is nothing interesting in the output of cage, only this repeating line:
or
System configuration
The text was updated successfully, but these errors were encountered: