You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run an unconfigured labwc and terminal from a tty with labwc -C none -s xterm (can be any term including kitty)
From that terminal, run kitty with kitty --config none
Observe that the kitty window is created after ~250ms, but the terminal prompt does not appear for another ~250ms.
Further observe that all keyboard input before the display of the terminal prompt is dropped
This is an issue because it eats the first few characters of the command I want to run after opening a terminal
This delay does not occur on openbox, nor on labwc by using XWayland: env -u WAYLAND_DISPLAY kitty --config none, which reduces the startup time to just the ~250ms required to show the window; there is no delay between window showing and prompt showing.
I have reproduced this issue on the following two systems:
Laptop with 6900HX, 680M, 3070ti and hybrid graphics enabled
Desktop with 12600k, 7900XT and no hybrid graphics setup
Screenshots
A recording of this bug in action; the second time, I am typing "abcdef" after invoking kitty to demonstrate the late input capture
kitty-startup-delay.webm
Environment Details
labwc 0.7.2
kitty 0.35.1 created by Kovid Goyal
Linux 6.9.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 31 May 2024 15:14:45 +0000 x86_64
Arch Linux 6.9.3-arch1-1 (/dev/tty)
Running under: Wayland (labwc 0.7.2) missing: preferred_scale
OpenGL: '4.6 (Core Profile) Mesa 24.1.1-arch1.1' Detected version: 4.6
Frozen: False
Paths:
kitty: /usr/bin/kitty
base dir: /usr/lib/kitty
extensions dir: /usr/lib/kitty/kitty
system shell: /bin/bash
Config options different from defaults:
Important environment variables seen by the kitty process:
PATH /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:
LANG en_US.UTF-8
EDITOR emacs
SHELL /bin/bash
DISPLAY :0
WAYLAND_DISPLAY wayland-0
USER adam
XDG_SESSION_PATH /org/freedesktop/DisplayManager/Session0
XDG_SEAT seat0
XDG_SESSION_DESKTOP labwc
XDG_SESSION_TYPE wayland
XDG_GREETER_DATA_DIR /var/lib/lightdm-data/adam
XDG_CURRENT_DESKTOP wlroots
XDG_SEAT_PATH /org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS user
XDG_VTNR 7
XDG_SESSION_ID 9
XDG_RUNTIME_DIR /run/user/1000
Additional Context
It would be great if either kitty captured keyboard input sooner, so the delay doesn't eat the first chars of a command, or the delay between showing the window and prompt could be reduced without XWayland. Ideally it'd be able to capture input immediately after invocation, but I'm not sure if that's possible.
To Reproduce
labwc -C none -s xterm(can be any term including kitty)kitty --config noneThis is an issue because it eats the first few characters of the command I want to run after opening a terminal
This delay does not occur on openbox, nor on labwc by using XWayland:
env -u WAYLAND_DISPLAY kitty --config none, which reduces the startup time to just the ~250ms required to show the window; there is no delay between window showing and prompt showing.I have reproduced this issue on the following two systems:
Screenshots
A recording of this bug in action; the second time, I am typing "abcdef" after invoking kitty to demonstrate the late input capture
kitty-startup-delay.webm
Environment Details
Additional Context
It would be great if either kitty captured keyboard input sooner, so the delay doesn't eat the first chars of a command, or the delay between showing the window and prompt could be reduced without XWayland. Ideally it'd be able to capture input immediately after invocation, but I'm not sure if that's possible.