kitty
No description set
- Developed at X11:terminals
- Sources inherited from project openSUSE:Factory
-
4
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.1:Staging:FactoryCandidates/kitty && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| fix-librsync-leap.patch | 0000001261 1.23 KB | |
| kitty-0.26.3.tar.gz | 0006055457 5.77 MB | |
| kitty.changes | 0000102178 99.8 KB | |
| kitty.spec | 0000004179 4.08 KB | |
| optional-disable-docs.patch | 0000002160 2.11 KB |
Revision 12 (latest revision is 31)
Dominique Leuenberger (dimstar_suse)
accepted
request 1006016
from
Michael Vetter (jubalh)
(revision 12)
- Update to 0.26.3:
* Wayland: Mark windows in which a bell occurs as urgent on compositors
that support the xdg-activation protocol
* Allow passing null bytes through the system clipboard (#5483)
* ssh kitten: Fix KITTY_PUBLIC_KEY not being encoded properly
when transmitting (#5496)
* Sessions: Allow controlling which OS Window is active via
the focus_os_window directive
* Wayland: Fix for bug in NVIDIA drivers that prevents
transparency working (#5479)
* Wayland: Fix for a bug that could cause kitty to become
non-responsive when using multiple OS windows in a single
instance on some compositors (#5495)
* Wayland: Fix for a bug preventing kitty from starting on
Hyprland when using a non-unit scale (#5467)
* Wayland: Generate a XDG_ACTIVATION_TOKEN when opening URLs
or running programs in the background via the launch action
* Fix a regression that caused kitty not to restore SIGPIPE
after python nukes it when launching children. Affects bash
which does not sanitize its signal mask. (#5500)
* Fix a use-after-free when handling fake mouse clicks and the
action causes windows to be removed/re-allocated (#5506)
Comments 2
Not sure how or why, but after the rebuild with gcc 12 kitty does something weird for me. Almost randomly freezes or forces to hang my keyboard, and it stops working until I unplug and plug it back. Tried 4 different cables with the same keyboard, and another 2. Got a pretty large (~8GB) debug log from it, not sure if I should open a bug report or bring it upstream so I will just a post a link to it here: https://drive.google.com/file/d/124tmeTheFMebT5ZUk-gGSOAKmT6pYu7n/view?usp=sharing.
Setting
sync_to_monitor noseem to solve the issue. Weird, but I'm also ~~lazy~~ too busy to debug it further ^-^