Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximize is not working and fullscreen is not fullscreen #6203

Open
munzirtaha opened this issue Sep 28, 2024 · 3 comments · May be fixed by #6383
Open

Maximize is not working and fullscreen is not fullscreen #6203

munzirtaha opened this issue Sep 28, 2024 · 3 comments · May be fixed by #6383
Labels
bug Something isn't working

Comments

@munzirtaha
Copy link

munzirtaha commented Sep 28, 2024

What Operating System(s) are you seeing this problem on?

Arch Linux (KDE)

Which Wayland compositor or X11 Window manager(s) are you using?

Wayland

WezTerm version

20240922-151228-2b76c63b

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

I set the wezterm gui to start maximized using window:gui_window():maximize() and the whole config is in the screenshot. Nothing happened and it started in a normal small window. I then replaced that line with toggle_fullscreen(). This time it started almost fullscreen except of the bottom edge. I thought first @wez has added a copyright border and I took a couple of seconds to realize that was firefox running in the background. I changed the theme to show the problem in a better way and attached a fullscreen of my display
wezterm

wezterm-maximize.log

To Reproduce

With my config, I set a keyboard shortcut to start wezterm. Every time I start it I get that problem.

Configuration

wezterm.on('gui-startup', function(cmd)
local tab, pane, window = mux.spawn_window(cmd or {})
--window:gui_window():maximize()
window:gui_window():toggle_fullscreen()
end)

Expected Behavior

To maximize in case of maximize() and really fullscreen in case of toggle_fullscreen()

Logs

Attahced: WEZTERM_LOG=debug wezterm start --always-new-process 2> /tmp/wezterm-maximize.log

Anything else?

No response

@munzirtaha munzirtaha added the bug Something isn't working label Sep 28, 2024
@LehanMusthafa
Copy link

I am too facing this issue on my computer.

What Operating System(s) are you seeing this problem on?
Fedora 40 (Gnome)

Which Wayland compositor or X11 Window manager(s) are you using?
Wayland

WezTerm version
wezterm-nightly-fedora40

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, I only have the nightly build available for my device.

@rustyworks
Copy link

rustyworks commented Oct 3, 2024

Hello, I use Wayland too (KDE Neon).

I use this configuration to maximize the windows

local wezterm = require 'wezterm'
local mux = wezterm.mux
local config = wezterm.config_builder()

wezterm.on('gui-startup', function(cmd)
  local tab, pane, window = mux.spawn_window(cmd or {})
  window:gui_window():maximize()
end)

config.enable_wayland = false

return config

enabled_wayland will use X11 protocol instead of wayland (but surprisingly, when I set this as false, it make the maximize scripts works).

@Felixoid
Copy link

Felixoid commented Nov 8, 2024

Facing the same issue
image

@devmatteini devmatteini linked a pull request Nov 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants