-
I have a kind of cursed display setup: Ghostty is handling the cursor size incorrectly on 1 and 2. System information: Ghostty 1.0.0-main+4b4d4062 (built from AUR ghostty-git)
out.mp4 |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 12 replies
-
Converting to Q&A because I recall some users in the beta hitting this and it's a desktop config issue. We don't render or configure the cursor in any way. |
Beta Was this translation helpful? Give feedback.
-
Looks like a gtk issue: should be fixed in next gtk release (?) |
Beta Was this translation helpful? Give feedback.
-
I have the same issue on KDE Plasma 6 under Wayland. So far I haven't seen that issue with other applications, does anyone know a workaround?
|
Beta Was this translation helpful? Give feedback.
-
I also encountered the same cursor issue with gtk 4.17.1. ❯ ghostty --version
Ghostty 1.0.0-dev+0000000
Version
- version: 1.0.0-dev+0000000
- channel: tip
Build Config
- Zig version: 0.13.0
- build mode : builtin.OptimizeMode.ReleaseFast
- app runtime: apprt.Runtime.gtk
- font engine: font.main.Backend.fontconfig_freetype
- renderer : renderer.OpenGL
- libxev : main.Backend.io_uring
- GTK version:
build : 4.17.1
runtime : 4.17.1
- libadwaita : enabled
build : 1.6.2
runtime : 1.6.2 |
Beta Was this translation helpful? Give feedback.
-
Setting the |
Beta Was this translation helpful? Give feedback.
-
Launching on Endeavour OS KDE Plasma 6 (Wayland) with
or not... if the display is in portrait mode the issue comes back, seems to work on landscape mode displays. I have two portrait and two landscape monitors. Scaling set to 100% on each in Display Configuration. |
Beta Was this translation helpful? Give feedback.
-
Fixed for me (Hyprland on NixOS): (pkgs.ghostty.override {
wrapGAppsHook4 = pkgs.wrapGAppsNoGuiHook.override {
isGraphical = true;
gtk3 =
(pkgs.__splicedPackages.gtk4.override {
wayland-protocols = pkgs.wayland-protocols.overrideAttrs (o: rec {
version = "1.41";
src = pkgs.fetchurl {
url = "https://gitlab.freedesktop.org/wayland/${o.pname}/-/releases/${version}/downloads/${o.pname}-${version}.tar.xz";
hash = "sha256-J4a2sbeZZeMT8sKJwSB1ue1wDUGESBDFGv2hDuMpV2s=";
};
});
}).overrideAttrs
(o: rec {
version = "4.17.6";
src = pkgs.fetchurl {
url = "mirror://gnome/sources/gtk/${lib.versions.majorMinor version}/gtk-${version}.tar.xz";
hash = "sha256-366boSY/hK+oOklNsu0UxzksZ4QLZzC/om63n94eE6E=";
};
postFixup = ''
demos=(gtk4-demo gtk4-demo-application gtk4-widget-factory)
for program in ''${demos[@]}; do
wrapProgram $dev/bin/$program \
--prefix XDG_DATA_DIRS : "$GSETTINGS_SCHEMAS_PATH:$out/share/gsettings-schemas/${o.pname}-${version}"
done
# Cannot be in postInstall, otherwise _multioutDocs hook in preFixup will move right back.
moveToOutput "share/doc" "$devdoc"
'';
});
};
}) |
Beta Was this translation helpful? Give feedback.
Looks like a gtk issue:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7760
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6212
https://blogs.kde.org/2024/10/09/cursor-size-problems-in-wayland-explained/
should be fixed in next gtk release (?)