On Monday, February 14, 2011 08:58:39 AM Ng Oon-Ee wrote: > On Sun, 2011-02-13 at 18:36 -0600, Gene Kodadek wrote: > > On Sunday, February 13, 2011 07:52:37 PM Colin Guthrie wrote: > > > 'Twas brillig, and Gene Kodadek at 13/02/11 19:19 did gyre and gimble: > > > > All right, here goes. Here are the steps I took: after starting > > > > Jack: > > > > > > > > 1) pulseaudio -vvvv > > > > 2) start-pulseaudio-x11 > > > > 3) start-pulseaudio-kde > > > > 4) loaded jack modules (got an error message telling me they > > > > were > > > > already > > > > loaded) > > > > > > > Here is the verbose output from that whole mess: > > > I don't see any mention of the jack modules in the PA verbose output > > > there. > > > > > > As no other sinks are available (udev-detect is run and detects your > > > alsa cards, but as jackd is running and has the cards open already, > > > it > > > correctly reports the alsa devices as "busy" and thus doesn't create > > > sinks/sources for them directly), the "dummy output" is > > > automatically > > > loaded but obviously as the name suggests, the sound effectively > > > goes to /dev/null. > > > > > > Can you post the error messages you get from and the commands you > > > use to load the jack modules (basically step 4 in your list)? > > > > > > That should help to debug further. > > > > > > For the benefit of yourself and Tanu, the screens in Phonon should > > > look > > > a little like the screenshots here: http://pulseaudio.org/wiki/KDE > > > > > > Col > > > > [gene at bruce ~]$ pulseaudio -L module-jack-sink -L module-jack-source > > E: pid.c: Daemon already running. > > E: main.c: pa_pid_file_create() failed. > > <Rant warning> > > You're an Arch Linux user. Does it not occur to you that 'daemon already > running' means exactly what it says? > > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at mail.0pointer.de > https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss Another question: after I'd uninstalled all of the pulseaudio related software, ditched all of the config files, and reverted all my settings, something was still writing a .pulse and .pulse-cookie directory and file to my ~ directory. It caused some problems. Any idea what program might have been doing that?
