sytone/obsidian-remote

Obsidian Not Opening, Pulse Audio Failing

BloxBoss6 opened this issue · 6 comments

Describe the bug
Openbox properly loads and is accessible from the browser, but the Obsidian Application never opens. When going through the logs, the main errors I see are from Autospawn and Pulse Audio, both failing and saying they cannot create a symlink.

Logs
https://pastebin.com/HgCQJJL2

Additional Context
I am running this on a Debian 11 server, that is using cifs-utils to add an smb drive from my TrueNAS system for backing up the system. I followed a tutorial on youtube for making a proxmox server with 2 vms on it. One for TrueNAS and the other for Docker.

My /etc/fstab code
//192.168.1.9/server-drive /mnt/server-drive cifs vers=3.0,credentials=/root/.smbcredentials,uid=1000,forceuid,gid=0,forcegid,noauto,nolock,x-systemd.automount 0 0

I am also getting this pulse audio issue.

I can use the keyboard, file server and console, but the obsidian app does not open.

I'll have a look this week to see if I can see anything. Need to rev the versions anyway.

did you get anywhere with this ? I have a similar issue with running this on a synology NAS unit, which obviously doesn't have a soundcard on it. Given obsidian doesn't need audio could we disable audio entirely on KasmVNC ?

Xvnc KasmVNC 1.1.0 - built Aug 12 2023 00:16:55
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation

Error: Connection refused
    at PulseAudioContext.<anonymous> (/kclient/node_modules/pulseaudio2/lib/pulse.js:120:36)
    at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
Kclient was unable to init audio, it is possible your host lacks support!!!!
Error: Access denied
    at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
Kclient was unable to init audio, it is possible your host lacks support!!!!

Hi Sirex99,

The last version that I downloaded worked for me, unsure what they changed though.

Simon.

i believe it might just be a case of removing

/startpulse.sh &

from/defaults/startwm.sh inside the container.

but the audio doesn't work.
The script /startpulse.sh is missing