-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
Running sunshine activates accessibility screen reader on some Linux distros #1303
Comments
This likely isn't going to result in any change to Sunshine, so closing. Fedora does not provide any package named |
Same happens in ubuntu 22.04. |
Same issue on Fedora 38. No, Fedora does not ship I don't see how this is not a Sunshine problem. Is it possible to have this issue re-opened? System info: |
I have this issue with the flatpak's systemd startup enabling screen reader. Manually running |
Just tried v0.21.0 of sunshine-fedora-38-amd64.rpm from releases and this issue still persists. Same behavior as I described above. I did not see any notes of this being fixed, but wanted to comment to indicate the issue is still active. Here are my current system deets:
Note: I am running Wayland. Edit: I wanted to 2nd what Nitrousoxide said... this issue is happening when starting sunshine via the systemd service. The service completely fails to start on boot, so I always have to start it manually. I start it with the command As an aside, for any here with the same issue, I simply run |
I think fedora has another service named |
This also happens on arch based systems using gnome. ran into it today. The toggle in accessibility does not even show it as toggled, but screen reader activates on user level systemd |
I've looked at [Unit]
Description=Sunshine is a self-hosted game stream host for Moonlight.
StartLimitIntervalSec=500
StartLimitBurst=5
After=graphical-session.target
[Service]
ExecStart=flatpak run dev.lizardbyte.sunshine
ExecStop=flatpak kill dev.lizardbyte.sunshine
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=default.target |
Chiming in here that this has been an issue for me as well and @eaglesemanation's solution worked for me. I'm on Ubuntu 23.10. The issue cropped up when I swapped GPUs (Nvidia --> AMD) and reinstalled my OS. Under Nvidia and X11, this wasn't an issue I encountered (but have not gone further down that particular debug rabbit hole). |
It also seems to cause some weird keyboard behaviour in Firefox. I found toggling "Screen Reader" on and off in Accessibility > Seeing works as a workaround. |
never have i ever been jumpscared by |
This version of the systemd service file fixed the screen reader issue for me, but it still seemed to start Sunshine before the desktop was ready sometimes. I had the best luck adding a .desktop file to the for the flatpak
Since autostart files always wait for the compositor to be ready fully before starting up it's seemed like the most reliable way to ensure sunshine doesn't start too early, as adding a wait timer to the systemd entry may or may not be long enough on any given boot (without getting excessively long at least). By having the autostart .desktop file start the systemd service rather than the flatpak (or binary if installed via the package manager) you still get the benefits of systemd recovering from a crash of Sunlight while a simple direct run of the application would not. |
Just chipping in to say that this issue is still occurring with Fedora 38. I'd rather not modify any files, as I have a tendency to destroy my system by doing so. |
This seems to work for me. It doesn't seem to invoke orca (the screen reader) on my testing. Adding
|
We probably need to do something like this to check the users environment. But instead of checking if X session is started, check if any supported DE is started. |
If I read correctly this error is applicable when used in systemd to automatically launch during startup. However, I have this error always, even if my system is fully started. I only start sunshine manually when needed, so I find it hard to believe its an error due to some dependency of desktop not fully started in my case. Also on my system it only occurs when I use the Gnome GUI to start Sunshine. If I open it through a terminal it launches fine. So my guess is that its somehow related to 'how' its being started. See also my issue here, which is closed due to being a duplicate, but contains a lot of info on my system. |
I have the same Issue, and just like @Michael-Yongshi I'm starting sunshine manually from the GUI (Fedora 39). It's really annoying so a fix of any sort would be highly appreciated. |
Anyone is free to submit a PR |
I use this as my service file, and it seems to avoid invoking orca (the TTS accessibility tool that the suggested service file always seems to invoke.
It is potentially not as robust since it's just sleeping for 10 seconds on boot to give the desktop enough time to finish starting rather than looking for a proper .target. However I've not found a good way stop it from starting up |
I have the same issue on Ubuntu 22.04 . |
I had found a solution some months ago and wrote it on the Discord channel, I will copy it here, maybe it can help the devs. I've just had the same problem with Fedora 39. I resolved editing sunshine.service inside /usr/lib/systemd/user The original file
I deleted the lines "PartOf", "Wants", "After", like it's showed in the example on
|
@AXL1994 great, it works for me too, thanks! |
Same issue in ubuntu 2204. The desktop file is |
This fix works for me in ubuntu 24.04 |
I'm getting the same issue in v2024.613.3910, using Fedora 40 and Gnome. Editing the systemd unit as noted by @AXL1994 resolved the issue |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
On nobara linux, which is a fedora 37 fork, the sunshine service fails to start, install and possibly be created at all.
Running 'systemctl --user start sunshine' opens corectrl and activates the screen reader, stopping the service does not deactivate either. I have to go through the gnome settings/accessibility/ screeen reader shows to be disabled, but activating and deactivating stops the tts service.
My work around was to manually create/start/enable the service with an alternative name, sunshine1.service. This allowed the application to operate
Expected Behavior
No response
Additional Context
No response
Host Operating System
Linux
Operating System Version
Nobara 37
Architecture
64 bit
Sunshine commit or version
19.1
Package
Linux - rpm
GPU Type
AMD
GPU Model
rx6700xt
GPU Driver/Mesa Version
Mesa 23.0.2 - Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev c5) Subsystem: XFX Limited Device 6606 Kernel driver in use: amdgpu Kernel modules: amdgpu --
Capture Method (Linux Only)
Defaults
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: