[Bug 1030] Review request: xbmc - Media center

http://bugzilla.rpmfusion.org/show_bug.cgi?id=1030 --- Comment #22 from rc040203(a)freenet.de 2010-01-14 04:57:39 --- (In reply to comment #20) Different kinds of audio related issues. unable to control audio volume" to always "full volume"/"very low volume". What exactly happens seems to be machine-, account- and xbmc-built/version/patch dependent. AFAIU, xbmc in a standalone-session tries to use alsa => I am likely facing the zoo of problems related to initializing alsa. The script tries to launch pulseaudio and then to fallback to "native xbmc" if pulseaudio is not available, using "pulse-session". pulse-session doesn't exist under Fedora => xbmc-standalone always falls back to using "native xbmc". => If we indent to always use pulse-audio, this script needs to be modified. May-be something along the lines of: /usr/bin/pulseaudio --start --log-target=syslog --use-pid-file /usr/bin/xbmc -fs --standalone "$@" /usr/bin/pulseaudio --kill --use-pid-file I am not sure. Yes, this is what I am referring to. Well, not for me: Testcase: Reboot into GDM; login into an xbmc-session; try to play an audio file. On one machine this appears to work, on another one I am receiving "failed to initialize audio device" warnings or am unable to control the audio volume. What exactly happens seems to depend upon the account I using to launch such an xbmx-session. On freshly created accounts, I am receiving "faild to initialize audio device", on previously used accounts, I typically end up with sound but without ability to control the audio volume. -- Configure bugmail: http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.