Things get clearer. (Sorry for the delay: jobhunting hell.)
On 17 May 2010, Tanu Kaskinen told this:
That seemed strange, because the X11 properties are set
automatically, and the user probably usually doesn't know anything about
the existence of the X11 properties. That means
On 16 May 2010, Colin Guthrie said:
'Twas brillig, and Tanu Kaskinen at 16/05/10 13:11 did gyre and gimble:
If I got the wrong impression and you were aware of this already, then
I'd like to hear about concrete situations where it does make sense to
configure the server address in client.conf
On 16 May 2010, Tanu Kaskinen spake thusly:
On Sat, 2010-05-15 at 22:43 +0100, Nix wrote:
But I'm getting this when I try to *start* the user-configured server
on that machine, via e.g. start-pulseaudio-x11!
With this in place, how are you supposed to start PA at all? (I'm not
even
440 /home/nix% /usr/bin/pulseaudio --start
N: main.c: User-configured server at sound.srvr.nix, not autospawning.
Shouldn't this check autospawn_fd, or *something* initialized only when
autospawning? Or am I missing something? (I suspect I must
On 15 May 2010, Tanu Kaskinen uttered the following:
On Sat, 2010-05-15 at 15:38 +0100, Nix wrote:
Obviously I'm missing something, but this hunk of this change:
snip
Proof:
n...@mutilate 440 /home/nix% /usr/bin/pulseaudio --start
N: main.c: User-configured server at sound.srvr.nix
On 23 Apr 2010, Colin Guthrie told this:
'Twas brillig, and Nix at 23/04/10 00:43 did gyre and gimble:
Fedora, at least, doesn't use ck-launch-session: it uses
ck-xinit-session, which is not in upstream console-kit at all; it's in
the RH-specific xinit package.
Can you say which pacakge
On 22 Apr 2010, John Frankish uttered the following:
This is fixed by adding:
ck-launch-session to .xsession, as in
$ cat .xsession
..
dbus-launch --sh-syntax --exit-with-session
ck-launch-session
Which has no manpage and no support for --help (it tries to exec
'--help', but doesn't emit
On 19 Apr 2010, Lennart Poettering outgrape:
On Fri, 16.04.10 21:02, Jan Braun (janbr...@gmx.de) wrote:
xterms ssh'd to otheru...@localhost .
Why would you ssh to the local machine?
'cos it forwards your X cookie and authentication agent connection for
you. (Of course you can do the X cookie
On 18 Apr 2010, David Henningsson spake thusly:
Both of them were tested by Daniel, and AFAIK neither have been applied
upstream.
These are both alsa-plugin things, right?
In that case, they can't fix the hangs I reported back in February,
since these are hangs experienced even --- especially
On 22 Feb 2010, Paul Menzel stated:
Am Montag, den 22.02.2010, 18:50 + schrieb Nix:
Ever since I started using PA 0.9.21 (and possibly before: it's been
long enough that my memory has faded), lots of applications have started
hanging hard when fast-forwarded/rewound. This includes MPD
of fast-forwards/rewinds, nothing is audible but
stuttering. I've tried to record it, but parec has no man page and it is
not obvious how to use it, e.g.:
n...@mutilate 33 /home/nix% parec --device=Monitor of Internal Audio Analog
Stereo --file-format=flac --record --verbose foo.flac
Failed to open
Ever since I started using PA 0.9.21 (and possibly before: it's been
long enough that my memory has faded), lots of applications have started
hanging hard when fast-forwarded/rewound. This includes MPD and every
single video player I own capable of fullscreen playback. As you might
imagine, having
On 9 Feb 2010, olin verbalised:
OK, so that's X11. I cannot figure out what PA's mechanism for this is. I sort
of get the sense, from this per-user-login server model that PA has the
horrible one-persone/one-computer model of the person at the console is the
person using the computer, which
On 28 Jan 2010, Colin Guthrie stated:
'Twas brillig, and Colin Guthrie at 23/01/10 13:38 did gyre and gimble:
Seems that since using stable-queue my paplay just freezes. It seems to
be polling happily but is stuck in the DRAINED state.
For references, this appears to be a client-side bug.
On 22 Jan 2010, Colin Guthrie said:
Could you also try this one (on top of the previous one):
http://git.0pointer.de/?p=pulseaudio.git;a=patch;h=84782f24c5f43456430c796bd12f9face24f0573
Actually, it wuold probably be best to use the stable-queue branch as
this contains the recommended patches
On 14 Jan 2010, Lennart Poettering outgrape:
On Sat, 09.01.10 23:06, Nix (n...@esperi.org.uk) wrote:
(symptoms also observed with qemu, world of goo and scorched3d, yes I
tried to run *that* over the network, I'm a glutton for punishment).
This only happens with a remote connection
On 9 Jan 2010, Daniel Chen said:
On Sat, Jan 9, 2010 at 6:28 PM, Nix n...@esperi.org.uk wrote:
No it doesn't, not consistently anyway: remote qemu just started
chopping even though pavucontrol was running. The diagnosis in Debian
bug 533039 looks accurate to me: the plugin is disconnecting
I've just tried to use the PulseAudio ALSA plugin for the first time (I
thought it might be a better way to do remote audio than relying on
everything supporting bloody esound, and alas some things just don't do
anything else).
Unfortunately the results are not pretty. With no other clients
On 9 Jan 2010, n...@esperi.org.uk uttered the following:
More oddly yet, if I start pavucontrol, whether locally or remotely,
before the remote application, the entire session is flawless: if I
start it while the choppy playback is going on, the choppiness vanishes.
No it doesn't, not
On 30 Nov 2009, Colin Guthrie told this:
'Twas brillig, and Nix at 29/11/09 21:12 did gyre and gimble:
A full clone shows me the tag, but a 'git pull' or 'git remote update
origin' refuses to download it.
The tag is made form the stable-queue branch so chances are you don't see it
because
On 29 Nov 2009, Colin Guthrie stated:
'Twas brillig, and Nix at 28/11/09 14:29 did gyre and gimble:
On 23 Nov 2009, Lennart Poettering told this:
Mostly bug fixes, and the device manager module Colin worked on.
This doesn't appear to have any git branches or tags associated with it,
nor any
On 23 Nov 2009, Lennart Poettering told this:
Mostly bug fixes, and the device manager module Colin worked on.
This doesn't appear to have any git branches or tags associated with it,
nor any git comments indicating which commit might be the right one to
work from.
On 2 Oct 2009, Lennart Poettering said:
Also, for some weird reason Marco modifies the default udev rules
heavily. Which is really something he shouldn't do.
He doesn't use the default rules at all (thinks they're ugly or
something, there's much too much on this on the Debian BTS). So he has
to
On 29 Sep 2009, Lennart Poettering outgrape:
(Btw, I use stow myself. and if configure detects a /usr/local/stow
directory it will install itself there automatically)
That's why I thought you'd probably apply it :) for a 'house of cards
built on symlinks' very few changes are needed: something
On 27 Sep 2009, Colin Guthrie uttered the following:
If you really, really want to cock about with the real location after
install, then just use unionfs mounts rather than a house of cards
built on symlinks.
Three thousand plus unionfs mounts? That strikes me as, well, insane :)
there are
There are multiple package management systems out there which implement
packages using symlinks. The recent (otherwise useful) check to ensure that
a re-executed pulseaudio is actually reexecuting itself unfortunately breaks
in the presence of all these packaging systems, because PA_BINARY refers
On 13 Jun 2009, Lennart Poettering verbalised:
On Sat, 13.06.09 17:07, Nix (n...@esperi.org.uk) wrote:
Plus: anything can make function calls, but personally after one
experience too many with libdbus killing my entire application without
warning or notice because it disliked something I'd
On 27 May 2009, Lennart Poettering outgrape:
On Thu, 28.05.09 04:53, Patrick Shirkey (pshir...@boosthardware.com) wrote:
I think it is useful that you have the internal api calls so dbus is not
a requirement for communicating with PA.
I am sorry to inform you that eventually PA will use
On 7 Jun 2009, Lennart Poettering said:
Nothing is future proof. I never made guarantees of API/ABI stability,
nor will ever make any.
In that case the likelihood of PA ever becoming a serious
infrastructural component are nil.
Imagine the X or libc developers said the same thing!
On 13 May 2009, Jason Taylor spake thusly:
shouldn't the directory be ~/.config/pulseaudio now ?
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
That's very non-Unixlike. Unix tradition has always been that if you
need multiple per-user configuration files, you put them
On 10 Jun 2009, Felipe Contreras stated:
What do you propose instead? Have a $version-stable branch for each
and every release? That doesn't scale, the repository will be polluted
with branches that nobody use any more.
Yes, exactly. Branches are (very) cheap.
(In any case, someone might
On 21 Dec 2008, Colin Guthrie verbalised:
Per-user mode is usually the way to go and should be the default on
Ubunutu (as far as i know). This mode allows proper integration info the
console-kit for knowing which user is active (e.g. if you loging 1
user at a time) and thus grants and
If anyone's interested in getting glitch-free playback working on
hardware too old to have an HPET, you too can force the kernel to use
your TSC as a high-res timer source with Jeff Hansen's patch here:
http://lkml.org/lkml/2008/10/10/235
It's probably best used only on a system that you know
On 29 Sep 2008, Lennart Poettering told this:
On Fri, 26.09.08 19:29, Nix ([EMAIL PROTECTED]) wrote:
i) the alsa source and sink don't work together: if I try I get -EBUSY
on the second one to initialize, every time. Maybe my SBLive card is
just too cheap and old, but this does mean module
On 26 Sep 2008, [EMAIL PROTECTED] uttered the following:
Freshly-compiled PA 0.9.12:
[EMAIL PROTECTED] 167 /home/nix% start-pulseaudio-x11
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root priviliges.
I: caps.c: Limited capabilities successfully
On 25 Nov 2007, Lennart Poettering uttered the following:
On Fri, 23.11.07 00:00, Nix ([EMAIL PROTECTED]) wrote:
The error from ALSA has changed but is still, well... an error:
[EMAIL PROTECTED] 90 /home/nix% /usr/bin/pulseaudio -vv --daemonize=no
pulseaudio: modules/module-alsa-sink.c:177
On 25 Nov 2007, Lennart Poettering told this:
On Thu, 22.11.07 22:29, Nix ([EMAIL PROTECTED]) wrote:
How did this ever work?
(you probably want to point out somewhere that this needs the unreleased
PolicyKit 0.7 as well.)
No it doesn't need 0.7. The whole point of this check
On 20 Nov 2007, Lennart Poettering told this:
On Sun, 04.11.07 12:16, Nix ([EMAIL PROTECTED]) wrote:
hades# /usr/bin/pulseaudio --daemonize=no
E: module-alsa-sink.c: Failed to set hardware parameters: Inappropriate
ioctl for device
E: module.c: Failed to load module module-alsa-sink
38 matches
Mail list logo