KDE Linux Steam controller request remote access dialog

Help
,
1

I’m using KDE Linux (which is wayland) and when I start my steam controller a dialog pops up saying “remote control requested - input devices”. Steam and vivaldi (both flatpaks) are auto-started at boot.

Steam starts in big picture and if I start the controller with steam focused the dialog doesn’t appear, but appears when I switch to vivaldi.

I’ve read up for a few hours on previous comments and merges I can find and I’ve tried adding steam and vivaldi to the xdp permissions store :
flatpak permission-set kde-authorized vivaldi com.vivaldi.Vivaldi yes
flatpak permission-set kde-authorized steam com.valvesoftware.Steam yes

I think I maybe misunderstand something. Does anyone have anything to help?

2

UPDATE: I restarted with no applications EXCEPT steam in big picture and as soon as I minimize steam the dialog appears. I have KDE connect installed but online reports said this was not the problem after they disabled it.

3

Hi! Based on what’s listed here - XDG Portal Pre-Authorization | Developer - I don’t know if the input devices side of that persistent permissions store has been implemented yet, perhaps just the remote desktop part?

For when it is - based on the man pages for flatpak-permission-set, the format of that command would be flatpak permission-set TABLE ID APP_ID [PERMISSION], where:

  • TABLE is the permission table being used (kde-authorized in this case)
  • ID is the name of the permission being granted - so instead of something like “vivaldi” or “steam”, it would likely have to be something like “input-devices”
4

Thanks, that agrees with my misunderstanding, I wasn’t trusting that it was ‘input devices’ that needed permission due to lots of complaints about the dialog being useless. Do you know how can I find out what the actual name is?

5

I’d have to defer to folks closer to the work there - but I don’t think it’s actually implemented yet. The merge request that created the table and implemented the permission for remote desktop, doesn’t look like it also includes an input capture component, and I don’t see any other relevant-looking changes committed yet in that repository.

Is the access at least being remembered during the same session?

6

OK that clarifies things so I’ll wait on that being implemented, but it seems strange because I was thinking from my online research that remote controls were the reason for the change.
And as for remembering, it does for some time but not all l the time, I mean that after an hour I would expect it to remember but not from morning to late afternoon. So I just leave it on for now, it’s not terrible on batteries.