I managed to partly fix the issue. In /usr/local/etc/qubes-rpc/, edit the split-browser-disp, in “master” section, add the line cd -- "$SB_FIREFOX_DIR", and I can launch firefox and use split-browser functions. However, simply editing that in disp-template is not sufficient. Firefox doesn’t show up automatically, and I have to manually run “split-browser-disp” and input “master” in that launched disp to have a working split-browser.
EDIT: Seems that only disp to persist channel is set up in this workaround. I can create new bookmarks and call bookmark function, but I can’t open bookmark links in the browser.
I find myself having the same problem, with same symptoms.
Sometimes the disposable will not launch Firefox, with the same error message.
Also, the split-browser functionality does not work in Firefox.
This is both in debian and fedora templates. Tried to reinstall from scratch starting from a minimal, clean template each time.
qubes-split-browser(-disp) packages v0.15, installed from qubes-contrib repos.
Tor disposables are working fine tho.
Grateful for any help.
Hmmm can you double-check that the split-browser script (in your persistent VM) contains the +WaitForSession fix? Like maybe you’ve got an old version lying around somewhere that takes precedence in your $PATH?
sudo journalctl -b in the disp1234 (after the error message has arrived in your persistent VM) might show something interesting.
I’m stumped too: I installed fedora-36-minimal-4.0.6-202205270243 in dom0, installed qubes-repo-contrib, then qubes-split-browser-disp firefox qubes-core-agent-passwordless-root, enabled 22-firefox.bash.EXAMPLE, created a -dvm based on the TemplateVM, and it just works
Anything interesting in your dysfunctional Firefox’s browser console? (Ctrl-Shift-j)
Okay so following your steps, everything works.
That prompts me to say that I’ve installed arkenfox.js in my disp templates, so I assume that it does mess up with split-browser.
Would you have any idea why ?
Sorry for forgetting this detail, made you waste your time.
Are you using that Arkenfox guide from the forum? I haven’t tested it at all, but it looks like maybe you could delete the Arkenfox autoconfig.js, and move firefox.cfg containing all those pref(...); lines to [/usr/local]/etc/split-browser/prefs/ (with a .js extension) in the persistent VM.