Re: [GnomeMeeting-list] How to run self-testing of Gnomemeeting

[Julien PUYDT <jpuydt free fr>]

No, no, no.

Stephen Liu a écrit :
> # /sbin/fuser /dev/snd/pcmC0D0p
> /dev/snd/pcmC0D0p:    4504  4504m

There you get a PID, number 4504.

> # ps ax | grep PID

There you were supposed to ps ax | grep 4504 ; this won't give you 
anything interesting.

> # ps ax | grep 4504
>  4504 ?        S      1:24 /usr/bin/artsd -F 10 -S
> 4096 -d -m artsmessage -c drkonqi -l 3 -f

This is it!

> # ps ax | grep 4504m

That isn't interesting.

Let me explain a little: each program running on your box comes with a 
number, named the "process identifier", "PID" for short. That number 
doesn't depend on the program itself, but on the time where it was launch.

Thus the goal of the above commands was:
* fuser will tell you which PID is blocking the sound device, but not 
its name ;
* ps ax | grep <the correct PID> will then allow you to see the command 
that was used to launch that program, and hence know its name.

Now, from what you gave us, we see that artsd is the culprit of your 
problems. Stop it and rerun the druid test.

Snark on #gnomemeeting