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
I installed kitty a few days ago via the Fedora store. I set it up with zsh, oh-my-zsh and powerlevel10k. Everything worked fine so far. I used kitty to work with node, rails and go. No problems. Today when I wanted to start kitty, the terminal window pops up shortly and immediately crashes. I uninstalled kitty via the store and installed again via shell command from the website.
When I started via command line I got the same behavior as before, with the error message: [144 22:29:20.318282] [glfw error 65544]: Wayland: fatal display error: Broken pipe
I had reinstalled my laptop last Saturday and a few days before I had already encountered the same behavior, also on Fedora 36.
Before I had kitty installed for several weeks, with no issues at all.
I got kitty working again by deleting the kitty folder from ~/.cache. I did try to remove the files contained in the directory one by one but kitty kept crashing. Only after I removed the whole folder did it start up again. This is how I got the environment details below.
To Reproduce
I don't know how to reproduce the behaviour definitely
Environment details
kitty 0.25.0 created by Kovid Goyal
Linux fedora 5.17.8-300.fc36.x86_64 #1 SMP PREEMPT Mon May 16 01:00:37 UTC 2022 x86_64
S
Kernel 5.17.8-300.fc36.x86_64 on an x86_64 (/dev/tty)
Running under: Wayland
Frozen: True
Paths:
kitty: /home/marcus/.local/kitty.app/bin/kitty
base dir: /home/marcus/.local/kitty.app/lib/kitty
extensions dir: /home/marcus/.local/kitty.app/lib/kitty-extensions
system shell: /usr/bin/zsh
Loaded config files:
/home/marcus/.config/kitty/kitty.conf
Config options different from defaults:
font_family MesloLGS NF
font_size 14.0
Colors:
background #1c2836
color1 #f9555f
color10 #34bb99
color11 #ffff55
color12 #589cf5
color13 #e75598
color14 #3978bb
color2 #20af89
color3 #fdf029
color4 #589cf5
color5 #934d95
color6 #1e9ee6
color7 #bbbbbb
color8 #545454
color9 #fa8b8e
cursor #bbbbbb
foreground #ffffff
selection_background #b4d5ff
selection_foreground #1c2836
Important environment variables seen by the kitty process:
PATH /home/marcus/.local/kitty.app/bin:/home/marcus/.rbenv/plugins/ruby-build/bin:/home/marcus/.rbenv/shims:/home/marcus/.rbenv/bin:/home/marcus/.volta/bin:/home/marcus/.deno/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin
LANG en_US.UTF-8
EDITOR /usr/bin/nano
SHELL /usr/bin/zsh
DISPLAY :0
WAYLAND_DISPLAY wayland-0
USER marcus
XDG_CURRENT_DESKTOP GNOME
XDG_MENU_PREFIX gnome-
XDG_DATA_DIRS /home/marcus/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
XDG_SESSION_DESKTOP gnome
XDG_RUNTIME_DIR /run/user/1000
XDG_SESSION_TYPE wayland
XDG_SESSION_CLASS user
The text was updated successfully, but these errors were encountered:
Describe the bug
I installed kitty a few days ago via the Fedora store. I set it up with
zsh
,oh-my-zsh
andpowerlevel10k
. Everything worked fine so far. I used kitty to work with node, rails and go. No problems. Today when I wanted to start kitty, the terminal window pops up shortly and immediately crashes. I uninstalled kitty via the store and installed again via shell command from the website.When I started via command line I got the same behavior as before, with the error message:
[144 22:29:20.318282] [glfw error 65544]: Wayland: fatal display error: Broken pipe
I had reinstalled my laptop last Saturday and a few days before I had already encountered the same behavior, also on Fedora 36.
Before I had kitty installed for several weeks, with no issues at all.
I got kitty working again by deleting the
kitty
folder from~/.cache
. I did try to remove the files contained in the directory one by one but kitty kept crashing. Only after I removed the whole folder did it start up again. This is how I got the environment details below.To Reproduce
I don't know how to reproduce the behaviour definitely
Environment details
The text was updated successfully, but these errors were encountered: