[BUG] Screen Record Hybrid setup

[Cleboost]

Step 1. Before you submit

• I have read the above instructions and am sure that this is supposed to be posted here.
• I've successfully updated to the latest versions following the updating guide.
• I've successfully updated the system packages to the latest.
• I've ticked the checkboxes without reading their contents

Step 2. Version info

Version info

◄ 0s ◎ caelestia -v                                                                                                                             ⌂ 15:10
Packages:
    caelestia-shell 1.3.2-1
    caelestia-cli-git 1.0.1.r13.g8399eee-1
    caelestia-meta r151.cadf1e2-1

Caelestia:
    Last commit: 1a69a48730842c5e77b746d751ac337edd20b796
    Commit message: env: add windows to SDL_VIDEODRIVER  Fixes #128 

Shell:
     caelestia-shell 1.3.2, revision 547b9bfcdd97c683211817a6ffcc7b6af7ae5cdc, distrubuted by: AUR (package: caelestia-shell)

Quickshell:
    quickshell 0.2.0, revision e9a574d919a89602d2868621576b2ccae54a5cb0, distributed by: AUR (package: quickshell-git)
                                                                                                                                                       
◄ 0s ◎ 

Step 3. Describe the issue

When I start recording, the record crashes.
I've tried to search for the problem and saw that the list (look for the logs) show only my internal screen (laptop screen). I think it's a problem with hybrid computer. My externals screens are not detected by caelesia because they are connected to my dGPU.

Do you have an idea if it's a bug or missed config?

PS: With prime-run caelestia record it works fine.

◄ 0s ◎ caelestia record                                       ⌂ 14:06
gsr error: display "DP-3" not found, expected one of:
  "screen"
  "eDP-1"    (1920x1080+0+0)
                                                                     
◄ 0s ◎ 

◄ 0s ◎ hyprctl monitors                                       ⌂ 14:08
Monitor eDP-1 (ID 0):
	1920x1080@144.00301 at 0x0
	description: BOE 0x0A11
	make: BOE
	model: 0x0A11
	physical size (mm): 380x220
	serial: 
	active workspace: 10 (10)
	special workspace: 0 ()
	reserved: 60 10 10 10
	scale: 1.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: true
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
	disabled: false
	currentFormat: XRGB8888
	mirrorOf: none
	availableModes: 1920x1080@144.00Hz 1920x1080@60.00Hz 1680x1050@144.00Hz 1280x1024@144.00Hz 1440x900@144.00Hz 1280x800@144.00Hz 1280x720@144.00Hz 1024x768@144.00Hz 800x600@144.00Hz 640x480@144.00Hz 

Monitor DP-2 (ID 1):
	1920x1080@143.99899 at 1920x0
	description: ASUSTek COMPUTER INC VY279HGE S7LMQS001610
	make: ASUSTek COMPUTER INC
	model: VY279HGE
	physical size (mm): 600x340
	serial: S7LMQS001610
	active workspace: 1 (1)
	special workspace: 0 ()
	reserved: 60 10 10 10
	scale: 1.00
	transform: 0
	focused: no
	dpmsStatus: 1
	vrr: false
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
	disabled: false
	currentFormat: XRGB8888
	mirrorOf: none
	availableModes: 1920x1080@60.00Hz 1920x1080@144.00Hz 1920x1080@119.88Hz 1920x1080@120.00Hz 1920x1080@100.00Hz 1920x1080@59.94Hz 1920x1080@50.00Hz 1680x1050@59.95Hz 1280x1024@75.03Hz 1280x1024@60.02Hz 1440x900@59.89Hz 1280x960@60.00Hz 1152x864@75.00Hz 1280x720@60.00Hz 1280x720@59.94Hz 1280x720@50.00Hz 1440x576@50.00Hz 1024x768@85.00Hz 1024x768@75.03Hz 1024x768@70.07Hz 1024x768@60.00Hz 1440x480@59.94Hz 800x600@75.00Hz 800x600@72.19Hz 800x600@60.32Hz 800x600@56.25Hz 720x576@50.00Hz 720x480@59.94Hz 640x480@75.00Hz 640x480@59.94Hz 640x480@59.93Hz 

Monitor DP-3 (ID 2):
	1680x1050@59.88300 at 3840x0
	description: Eizo Nanao Corporation EV2216W 70457074
	make: Eizo Nanao Corporation
	model: EV2216W
	physical size (mm): 480x300
	serial: 70457074
	active workspace: 11 (11)
	special workspace: 0 ()
	reserved: 60 10 10 10
	scale: 1.00
	transform: 0
	focused: yes
	dpmsStatus: 1
	vrr: false
	solitary: 0
	solitaryBlockedBy: windowed mode,missing candidate
	activelyTearing: false
	tearingBlockedBy: next frame is not torn,user settings,missing candidate
	directScanoutTo: 0
	directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
	disabled: false
	currentFormat: XRGB8888
	mirrorOf: none
	availableModes: 1680x1050@59.88Hz 1280x1024@60.02Hz 1280x960@60.00Hz 1280x720@60.00Hz 1280x720@59.94Hz 1024x768@60.00Hz 800x600@60.32Hz 720x480@59.94Hz 640x480@59.94Hz 640x480@59.93Hz 

Reminder

• I agree that it's usually impossible for others to help me without my logs.

[izom03]

Same issue for me

[izom03]

It's really dirty fix, but I just added wrapper for gpu-screen-recorder:

#!/bin/sh
exec prime-run /usr/bin/gpu-screen-recorder "$@"

[Cleboost]

I have also a local fix but I just want to report for a global fix.

[dec05eba]

The proper fix would be for caelestia to use the -w portal option with gpu screen recorder

[soramanew]

The proper fix would be for caelestia to use the -w portal option with gpu screen recorder

Unfortunately that would make the portal dialog open every time you want to record, making full screen and region record useless (as you would need to pick it via the portal instead).

[dec05eba]

The proper fix would be for caelestia to use the -w portal option with gpu screen recorder

Unfortunately that would make the portal dialog open every time you want to record, making full screen and region record useless (as you would need to pick it via the portal instead).

Yes, the UI would have to be redesigned but thats the design wayland devs have decided. I cant add support for recording a monitor connected to another gpu without desktop portal because there is a bug in mesa or the intel driver that segfaults the program when doing that. One temporary solution would be for gpu screen recorder to automatically use prime-run/DRI_PRIME by detecting which gpu the target monitor is associated with, which would work in this case when you dont manually select a codec, etc.