Skip to content

Gamescope doesn't work with touch if nested #1606

@ShapeShifter499

Description

@ShapeShifter499

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

When started as a nested session under a already running wayland session (I.E. started in the same session as Gnome) touchscreen events do not seem to work.

It does work in a gamescope-session just fine.

Steps To Reproduce

gamescope --default-touch-mode 4 -F fsr -S auto -f -W 1280 -H 800 -e --mangoapp -- steam -gamepadui -steamos3 -steampal -steamdeck -console

Attempt to touch elements in the steam client or any started games.

Nothing happens.

Hardware information

- Distro: Arch linux
- CPU: AMD Custom APU 0405
- GPU: Advanced Micro Devices, Inc. [AMD/ATI] VanGogh [AMD Custom GPU 0405]
- Driver Version: Mesa 24.2.5-arch1.1
Steam Deck LCD with Arch Linux replacing the original SteamOS

Software information

- Desktop environment: Gnome 47
- Session type: wayland
- Gamescope version: [gamescope] [Info]  console: gamescope version 3.15.13 (gcc 14.2.1)
- Gamescope launch command(s): gamescope --default-touch-mode 4 -F fsr -S auto -f -W 1280 -H 800 -e --mangoapp -- steam -gamepadui -steamos3 -steampal -steamdeck -console

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions