Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gamescope not working at all #1642

Open
3 of 6 tasks
Anonyku05 opened this issue Nov 28, 2024 · 1 comment
Open
3 of 6 tasks

Gamescope not working at all #1642

Anonyku05 opened this issue Nov 28, 2024 · 1 comment

Comments

@Anonyku05
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

Good evening,
I’m having a small issue with the application "gamescope," which is used to launch games/applications at a specific resolution. It used to work well, but after reinstalling Debian, I’m now getting this error message:

wlserver: [backend/headless/backend.c:82] Creating headless backend
MESA-INTEL: warning: Haswell Vulkan support is incomplete
vulkan: selecting physical device 'AMD Radeon RX 470 Graphics (RADV POLARIS10)': queue family 1
vulkan: physical device does not support DRM format modifiers
vulkan: supported DRM formats for sampling usage:
vulkan: 0x34325241
vulkan: 0x34325258
vulkan: 0x3231564E
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:18] Starting headless backend
wlserver: [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
wlserver: [xwayland/server.c:92] Starting Xwayland on :2
wlserver: [types/wlr_surface.c:748] New wlr_surface 0x5630080539b0 (res 0x56300804b0c0)
wlserver: [xwayland/server.c:250] Xserver is ready
pipewire: pw_context_connect failed
Warning: failed to setup PipeWire, screen capture won't be available
(EE) failed to read Wayland events: Broken pipe

I’m not sure what to do to fix this issue. Any help would be greatly appreciated!

PS: I'm forcing letterboxing because of a modpack in Minecraft that is meant to be played like that

Steps To Reproduce

1- Start gamescope with the following command: gamescope -w 1280 -h 1024 -f -- minecraft-launcher
2- Having the error

Hardware information

- Distro: Debian 12 (12.8.0)
- CPU: I7 4790k
- GPU: AMD RX 470
- Driver Version: _Will add_

Software information

- Desktop environment: KDE Plasma 6
- Session type: Wayland
- Gamescope version: Latest to date
- Gamescope launch command(s): gamescope -w 1280 -h 1024 -f -- minecraft-launcher

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

No response

@matte-schwartz
Copy link

I'm unfamiliar with Debian packaging. Is it up-to-date with the latest release of gamescope (3.15.14), or are you referring to the latest Debian 12 release? If the latter, what's the version reported by your package manager?

If Debian logs coredumps it would be helpful to see a coredump as well (coredumpctl, look for the number associated with Gamescope's core dump, and then coredumpctl info <x>) since there's not much to go on based on the log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants