Patrick O'Callaghan wrote:
On Sat, 2008-05-03 at 14:45 -0700, Andrew Farris wrote:
Neal Becker wrote:
I see these messages:
May 3 17:30:33 nbecker1 pulseaudio[31536]: main.c: Called SUID root and
real-time/high-priority scheduling was requested in the configuration.
However, we lack the necessary priviliges:
May 3 17:30:33 nbecker1 pulseaudio[31536]: main.c: We are not in
group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID
again.
May 3 17:30:33 nbecker1 pulseaudio[31536]: main.c: For enabling real-time
scheduling please acquire the appropriate PolicyKit priviliges, or become a
member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource
limits for this user.
But I AM in pulse-rt group. Seems strange. Either it's broken, or perhaps
this message was posted when I was not logged in? (Doesn't say what user
it's complaining about, but I'm the only account on this machine)
Use the authorizations tool in system->preferences->system to set yourself as
authorized by policykit for realtime pulseaudio. That should then take care of
it I think, and you might be right its not really running under your user at the
time (not positive about that).
And on The Other Desktop Environment (KDE) that would be where?
I don't know, try rpm -ql PolicyKit, or rpm -qa '*policy*' since I think there
is a gnome-policykit or something like that. Or you could just logout and try
it where you know it is which would have taken less time than me replying.
Using 'find' would get it for you too if you went looking for .desktop files and
grepped them for Authorizations.
Sorry for the sarcasm, but I'm getting really tired of the screwed-up
audio on Fedora. Sometimes it works, sometimes it doesn't. It was
working up till a few days ago, then it stopped. I've changed *nothing*
except for applying updates. There are no error messages or indications
of any kind of problem in the logs.
'except for applying updates'... then you changed things. Go see what changed,
thats what /var/log/yum.log, /var/log/rpm* and gpk-log are for. What updates
did you apply and when? The kernel most likely, did you boot to the new one or
not yet?
We are neck deep in prerelease time which means lots of debugging information is
reduced, the kernel is being quieted (remove 'quiet' from grub) and other
debugging is turned off... you need to install many debuginfo packages, start
with "debuginfo-install amarok pulseaudio" and go from there.
Amarok claims to be playing a track,
and even shows the equalizer histogram, but nothing is coming out of the
speakers. Yes they are plugged in, yes they are powered on, yes the
volume is turned up.
Maybe this is a Pulse Audio problem, maybe it isn't. I have *no idea*
how to start diagnosing it. I have never understood the relationship
between the multiple bits of audio software, which of them cooperate,
which are mutually exclusive, which work, which don't. Most of the docs
talk about one component with no reference to any others or how they all
fit together. The audio settings dialogue on both KDE and Gnome is a
joke. Does anyone really expect an end-user to understand this?
Let me clarify things for you. Arts should still be current and usable if you
prefer to skip using pulseaudio altogether in KDE. The same is true for alsa in
GNOME. You may select that in the settings dialogue and remove pulseaudio from
your session so the daemon isn't running and pulse should just be gone.
However, the future is pulse and because its default behavior thats what is
expected to work. Anything else both the above three is asking for brokeness
(i.e. oss).
No, end-users are not supposed to figure out bugs, testers are. Clearly
something is not perfect, and yes it should have been 'fixed' by this time, but
pointing out the obvious wastes time.
There are a number of intel audio bugs in bugzilla, you may want to search
through them. One of them is mine where I've reported sound playing too quickly
on my older intel chipset, but it does not have your 'glitchy' sound playback
issue. Mine plays fine despite running near 100% CPU at all times with
folding@home client.
I'm not running an audio editing station here. I don't have exotic
hardware, just an Intel mobo chipset. I don't even care about MIDI, I
just want my music to come out of my speakers. This really, seriously,
should not be this hard.
Other people do care about those things, which is what makes 'this' so hard.
Audio is not simple unless what you want to do is stupidly simple (like driving
a simple sine signal to an internal squeeker)... Please don't take the easy
route here and fall into 'it should just work' useless discussion.
--
Andrew Farris <lordmorgul@xxxxxxxxx> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
