fulljewelry.blogg.se

Unable to connect to pulseaudio
Unable to connect to pulseaudio













unable to connect to pulseaudio

You might think that "running as a service" and "outputting audio via PulseAudio" would be compatible, especially as they're both listed on the same piece of documentation on the Mopidy website. However, there's usually a logged-in session running. The one small drawback with this approach is that the music player won't be running if the machine reboots and I haven't logged in yet. On Ubuntu there's a program called "Startup Applications" that you use to add/remove things easily. something that runs on my own user account as part of my graphical desktop login. So here's what I've got now: instead of running Mopidy as a service (using mopidyctl to control it), I'm running it as a "startup application", i.e. I suspect it's because it's running under a different user id.) (I still don't know why that should mean it's unable to connect, even after logging in. So it simply isn't there for Mopidy to connect to, until you log in. PulseAudio, however, does not run on startup, but is part of your login session. This is because if you run as a service, you're running something that starts up as soon as the computer boots, and doesn't use your login userid. The solution, as far as I can tell, for my standard Ubuntu 18.04 is: you should not do both of these things. I tried everything, setting PulseAudio to be as permissive as possible (allowing remote connections etc). I had changed Mopidy's config as well as PulseAudio's config.

unable to connect to pulseaudio

It seemed to be unable to make any sound play back, unless I manually killed pulse, after which it could start playing. However, it kept failing to connect to PulseAudio. it should be able to play music even when there's a video playing from Firefox. I had set Mopidy up to connect to PulseAudio, which seemed like a good idea since then it should "play nicely" with other things on the computer, e.g.I had set Mopidy up to run as a service, which seemed like a good idea - it's not just some application I want to start from time-to-time, it's the main music player for my flat, so I want it to be there on tap.On Ubuntu though I encountered a persistent problem: I've been enjoying using Mopidy and ncmpcpp as my music player.















Unable to connect to pulseaudio