stef

BitTwister: so you are saying boot to command line (no X server) and use
the command:

PULSE_SERVER_TYPE=personal

Mine is currently set to none.

Am I understanding you correctly? Anything else?

david w. hodgins

I would go ahead an re-enable it with X running, and then restart X, or
possibly reboot, just to ensure every thing is starting ok. Also a
guaranteed way to kill anything already using the sound system.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

david w. hodgins

If you're making the change at the command line, use a text editor such as
mcedit /etc/sysconfig/pulseaudio
to change the server type line. Make sure you have mcedit installed, and
su to root.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

bit twister

Set it same as mine, Yes, and remember, it was a Wild A$$ Guess (WAG)


/bin/rm -f ~stef/.pulserc

As others have suggested, everyone in the audio group which I
suggested very early in the thread.

stef

OK so done that but cannot enable the "Automatic Routing from ALSA to
PulseAudio, using MCC" without getting the usual "...pointing to the null
device..." error.

How do I enable the automatic routing with x-server down--via the CML?

Thanks.

bit twister

I do not have a clue.

If I had dinked up my install by screwing around, and I have more than
once, I just bite the bullet and do a clean install.
Goes much faster if you have made a copy of install in another partition.

I always set the system up at run level 3. If I want gui, I type startx

All users on the system are in the audio group.
As Bittwister, in the KDE Control Center --> Sound & Multimedia -->
System Notifications,
I disable all sound for KDE System Notifications and The KDE Window Manager.

Under Sound System, I set Auto-suspend to 1 second.

stef

OK, thanks. I will check on these settings....

stef

BitTwister,

I understand the above. but really, what are the advantages? It takes
time for x to start and while I love the CML (command line), I work
mostly win x up and running and a CML emulator.

D oyu do most of your work using the CML?

bit twister

If I dink up the X server, it's easy enough to fix it.

Also my ~/.bash_profile, ~/.bashrc and ~/.bash_logout run
when logging in/out at runlevel 3.


I do not see where that is an issue. Unless you boot the box and walk
away for awhile. I never timed it, but it just seems longer for me
to get to the point to enter my password at runlevel 5 than at 3.


I try to use the proper tool for the job. :-)

For anything repetitive, I'll write a script.

Running down command files and viewing contents for someone with
a problem is a bit of a chore with gui tools.

stef

Those would run equally when using level 5

Wouls it not be a factor if you are in the middle of a task and find out
you need x and go startx, etc.?

I'm still new at Linux so bear with me....