------- Original Message ------- On Tuesday, April 11th, 2023 at 12:34 PM, Rich Shepard <[email protected]> wrote:
> On Tue, 11 Apr 2023, Ben Koenig wrote: > > > Well that kind of depends on what the problem is. You need to be more > > specific than "it don't work" because there are a bunch of things that can > > happen and each one speaks to a different underlying cause. > > > When you run it in the terminal, does it hang and hold onto the prompt? > > Does it run and immediately exit? > > > Ben, > > Well. Now a different response: > $ ./ZoomLauncher > ZoomLauncher started. > Zoom path is: /opt/zoom > cmd line: > Start subprocess: /opt/zoom/zoom sucessfully, process pid: 5709 > Class App Lib Possible Culprit Flags > > ... > > > zoom started. > No PulseAudio daemon running, or not running as session daemon. you shouldn't be getting that error. 14.2 pulseaudio works out-of-the-box. > ... > > zoom started. > zoom started. > Fontconfig warning: "/etc/fonts/fonts.conf", line 102: unknown element "blank" > Client: Breakpad is using Single Client Mode! client fd = -1 > Exit zoom as another zoom instance is running! > zoom exited normally, exit code is 0 . > ZoomLauncher exit. > > And: > $ pulseaudio > E: [pulseaudio] pid.c: Daemon already running. > E: [pulseaudio] main.c: pa_pid_file_create() failed. > Don't do that. FFS dude, daemons are not something you just call directly. You don't check the status of an apache webserver by typing httpd, and you don't check the status of the pulseaudio sound server by typing pulseaudio. There's a very strong chance that your various background daemons are all running out of order and you need to reboot to make sure everything has loaded in the correct order. You never just execute pulse directly you have to make sure it gets called appropriately so that it ties into the rest of the desktop session. -Ben
