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

Qsynth causes audio output to disappear in Debian and shouldn't be autostarted #5118

Closed
4 tasks done
mYnDstrEAm opened this issue Nov 3, 2023 · 3 comments
Closed
4 tasks done

Comments

@mYnDstrEAm
Copy link

mYnDstrEAm commented Nov 3, 2023

Bug description

Since a recent upgrade Lutris bundles QSynth. That it was running due to Lutris caused a No output or input devices found problem in Debian where no sound device is available. See that link for details. I'm not sure how that can be prevented but think that simply preventing it from starting would suffice since quitting it once in the process manager got the audio to work again.

How to Reproduce

Steps to reproduce the behavior:

  1. Upgrade Lutris in Debian 12 with the Debian 12 repo of Lutris.
  2. Click the volume icon in the tray bar to see that no audio output is possible anymore. It could be that some actions in between are needed, most likely a reboot.

Expected behavior

To not start qsynth or to not cause any problems to the audio output. It's unclear why it comes bundled with it now.

Log output

Unrelated to lutris itself in terms of Lutris outputs.

System Information

Debian 12 with KDE
Only an internal soundcard

Media (optional)

No response

Checklist:

  • I'm not asking for support with a game or the wine runner.
  • I have followed the above mentioned guides and have all the graphics and wine dependencies installed.
  • I have checked for existing issues that describe my problem prior to opening this one.
  • I understand that improperly formatted bug reports may be closed without explanation.
@strycore
Copy link
Member

I don't know why Lutris would bundle Qsynth. We have fluidsynth in the recommended packages, but that's different.
You should be able to remove Qsynth if it's causing issues. Fluidsynth as been marked as a soft dependencies which mean it can be uninstalled as well without affecting Lutris (other than not providing MIDI sound) but that change is for 0.5.15 (shipping soon)

@mYnDstrEAm
Copy link
Author

I still have the problem whenever rebooting since qsynth gets autostarted. I have Lutris version 0.5.14 (shown in Apper and when running lutris --version; apparently it was manually installed). aptitude why qsynth still shows lutris depends fluidsynth and fluidsynth recommends qsynth. I didn't install it myself so it seems like it gets automatically installed and this could also cause the same problem for other Linux users.

I just removed qsynth now (sudo apt-get remove qsynth) and hope it doesn't cause any problems. Maybe one can specify whether or not dependencies' recommended packages are installed or not or something similar so that you can prevent qsynth from getting installed if it's not needed anyway.

@strycore
Copy link
Member

@lutris lutris locked as resolved and limited conversation to collaborators Feb 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants