Skip to content

kitty crashes with BadRRCrtc  #1006

@daenney

Description

@daenney

Kitty sometimes crashes after the display it's on has gone through a sleep->wake cycle (turned off the monitor or system comes out of standby).

This is what I end up with in the journal:

Sep 22 12:21:41 monoceros kitty.desktop[60717]: X Error of failed request:  BadRRCrtc (invalid Crtc parameter)
Sep 22 12:21:41 monoceros kitty.desktop[60717]:   Major opcode of failed request:  140 (RANDR)
Sep 22 12:21:41 monoceros kitty.desktop[60717]:   Minor opcode of failed request:  20 (RRGetCrtcInfo)
Sep 22 12:21:41 monoceros kitty.desktop[60717]:   Crtc id in failed request: 0x20
Sep 22 12:21:41 monoceros kitty.desktop[60717]:   Serial number of failed request:  3225
Sep 22 12:21:41 monoceros kitty.desktop[60717]:   Current serial number in output stream:  3225

Environment:

  • Kernel: 4.18.9-arch1-1-ARCH
  • Wayland/wayland-protocols: 1.16
  • GNOME Shell: 3.30 (this also happened on 3.28)
  • Kitty: 0.12.1
  • WAYLAND_DISPLAY=wayland-0
  • XDG_SESSION_TYPE=wayland
  • DISPLAY=:0

Possibly related, or not, I've been seeing these a lot in the journal too:

Sep 22 12:21:46 monoceros org.gnome.Shell.desktop[60717]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a0000e (kitty)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions