Grimblast sometimes crashes DELTARUNE with "X Error of failed request: BadRROutput"

[TheSunCat]

Program

grimblast

Maintainers of the program

@fufexan, @Misterio77

Bug or Regression?

Bug

Description

I use grimblast's area screenshot feature quite often, but it has caused DELTARUNE to crash twice today when I press the hotkey to run grimblast.

How to reproduce

Run DELTARUNE, execute /nix/store/7fjn885qk4rkxpvf8mi3fi06a30s2nh7-grimblast-0.1-unstable-2025-05-18/bin/grimblast --freeze copysave area ~/Pictures/screen/$(TZ=utc date +'screenshot_%Y-%m-%d-%H%M%S.%3N.png')

Hyprland crash reports, program logs, images, videos

journalctl tail:

Jun 07 16:30:22 zag wpa_supplicant[1899]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-83 noise=9999 txrate=6000
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] configure for grimblastVD
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] configure for grimblastVD
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] Image data for grimblastVD: /nix/store/s19jwf91403yanxl7sgmbqvsz6na960i-source/common/hm/dotfile>
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] Submitting viewport dest size 960x540 for 13518fb0
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] handlePreferredScale: 2.00 for 13518fb0
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] Image data for grimblastVD: /nix/store/s19jwf91403yanxl7sgmbqvsz6na960i-source/common/hm/dotfile>
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] Submitting viewport dest size 960x540 for 13518fb0
Jun 07 16:30:23 zag hyprpaper[2072]: [LOG] Destroying output grimblastVD
Jun 07 16:30:23 zag steam[2688]: X Error of failed request:  BadRROutput (invalid Output parameter)
Jun 07 16:30:23 zag steam[2688]:   Major opcode of failed request:  140 (RANDR)
Jun 07 16:30:23 zag steam[2688]:   Minor opcode of failed request:  9 (RRGetOutputInfo)
Jun 07 16:30:23 zag steam[2688]:   Serial number of failed request:  10519
Jun 07 16:30:23 zag steam[2688]:   Current serial number in output stream:  10519
Jun 07 16:30:23 zag steam[2688]: pid 3595 != 3594, skipping destruction (fork without exec?)
Jun 07 16:30:23 zag steam[2688]: Game Recording - game stopped [gameid=1671210]
Jun 07 16:30:23 zag steam[2688]: Removing process 11969 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3780 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3690 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3671 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3626 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3617 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3612 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3602 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3599 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3597 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3594 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3593 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3592 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3591 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3439 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3438 for gameID 1671210
Jun 07 16:30:23 zag steam[2688]: Removing process 3437 for gameID 1671210
Jun 07 16:30:25 zag wpa_supplicant[1899]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-77 noise=9999 txrate=6000

[fufexan]

Try running with GRIMBLAST_HIDE_CURSOR=0.

The default is to hide the cursor, which does so by creating a temporary monitor. Based on the log, it seems that XWayland cannot handle that and crashes.