Opened 8 months ago

Last modified 8 months ago

#33443 new defect

Audio/sound not working on Xubuntu 18.04

Reported by: FriendFX Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version: Tor: unspecified
Severity: Normal Keywords: audio, sound, Linux, Ubuntu, Xubuntu, 18.04, pulseaudio
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I have a strange audio/sound problem on my Xubuntu 18.04 LTS box, for details see

The only application I am currently aware of that is unable to produce sound (after manually starting Pulseaudio) is Tor Browser 9.0.5.

To test whether this is an issue of the Firefox release Tor Browser is based on, namely 68.5.0esr (64-bit), I downloaded that and was able to play audio successfully (e.g. on Youtube).

I had a look at the Tor Logs, but they seem to only log events related to Tor connectivity, not browser-related events.

Child Tickets

Change History (2)

comment:1 Changed 8 months ago by FriendFX

After some more research, and finding #29360, I could solve the issue by following this comment:

Initially I tried to create a symlink like so

cd Browser/.config
mv pulse pulse.orig
ln -s ~/.config/pulse

but that resulted in errors

Failed to create secure directory (.../Browser/.config/pulse): Too many levels of symbolic links)
[Child 5912, MediaPlayback #2] WARNING: 7f85ab585a10 OpenCubeb() failed to init cubeb: file /var/tmp/build/firefox-869854aeea80/dom/media/AudioStream.cpp, line 382
[Child 5912, MediaPlayback #2] WARNING: Decoder=7f85a79d5000 [OnMediaSinkAudioError]: file /var/tmp/build/firefox-869854aeea80/dom/media/MediaDecoderStateMachine.cpp, line 3639
[Child 5912, MediaPlayback #2] WARNING: Decoder=7f85a79d5000 Decode error: NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b) - OnMediaSinkAudioError: file /var/tmp/build/firefox-869854aeea80/dom/media/MediaDecoderStateMachine

The solution was to use copy instead of symlinking:

cd Browser/.config
cp -a ~/.config/pulse ./

I hope this practice doesn't cause any security/privacy issues?

Last edited 8 months ago by FriendFX (previous) (diff)

comment:2 Changed 8 months ago by FriendFX

I am currently thinking that messing with Pulseaudio settings invalidated the original pulse cookie I had after installing my system initially, but I didn't actually find where Tor Browser keeps its own pulse config: The <installfolder>/Browser/.config/pulse/ folder only included a symbolic link fd54e00ba87640399a53c282574d152c-runtime -> /tmp/pulse-eeOG1j3w9rzO and the destination folder /tmp/pulse-eeOG1j3w9rzO was empty.

Note: See TracTickets for help on using tickets.