Date: Wed, 25 Jan 2017 18:02:38 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 216327] www/chromium: Pulseaudio compiled in by default Message-ID: <bug-216327-28929-iQWXU9LHBo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216327-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-216327-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216327 --- Comment #9 from vermaden@interia.pl --- Some input from from FreeBSD Forums: And sideeffects is here, as I suspected - after I installed pulseaudio (and updated recently to the version 10) - as dependency by Chrome, sound is crippled/choppy completely from chromium, from firefox too, because firefox starts using pulseaudio dynamicaly (maybe pulse is interfering with OSS in = some way). When I need to switch sound output, I need to switch it in OSS (for s= ome apps) and also in pulse (for other apps). I also need to read extra long wi= ki pages (+ Arch linux wiki pages) about PulseProblem 10.0, google like a mani= ac and hope, that my sound will be OK and properly configured somewhere in the future. Or, of course, I can recompile chrome port every 14 days with bare OSS/ALSA support only. Or recompile everything other once a month with PulseProblem.= Or throw away PulseProblem + Chrome from my drive. It's good, so many options. I knew it!=20 https://forums.freebsd.org/threads/57366/page-2#post-341005 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216327-28929-iQWXU9LHBo>