'Twas brillig, and Chris at 26/07/10 23:40 did gyre and gimble:
On Fri, 2010-07-23 at 08:58 +0100, Colin Guthrie wrote:
'Twas brillig, and Chris at 23/07/10 02:04 did gyre and gimble:
What is the best way to start PA for debugging and still have all the
usual clients running?
If you mean
On Tue, 2010-07-27 at 08:37 +0100, Colin Guthrie wrote:
'Twas brillig, and Chris at 26/07/10 23:40 did gyre and gimble:
On Fri, 2010-07-23 at 08:58 +0100, Colin Guthrie wrote:
'Twas brillig, and Chris at 23/07/10 02:04 did gyre and gimble:
What is the best way to start PA for debugging and
On Fri, 2010-07-23 at 08:58 +0100, Colin Guthrie wrote:
'Twas brillig, and Chris at 23/07/10 02:04 did gyre and gimble:
What is the best way to start PA for debugging and still have all the
usual clients running?
If you mean having all the clients connect (e.g. applications with
On Fri, Jul 23, 2010 at 03:04:01AM CEST, Chris wrote:
What is the best way to start PA for debugging and still have all the
usual clients running?
You are probably best off to run pulseaudio in a terminal with - specified
on the command-line. This will give you a rather verbose log of what
On 2010-07-23 03:04, Chris wrote:
What is the best way to start PA for debugging and still have all the
usual clients running?
pacmd set-log-level 4
...if your log target is set to syslog, just watch it grow :-)
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
What is the best way to start PA for debugging and still have all the
usual clients running?
--
Chris
KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
___
pulseaudio-discuss mailing list
