Re: new attempt to solve an old problem with gkrellmsss
Bill Wilson <[email protected]> Wed, 15 Sep 2010 00:10:59 -0500
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Message-ID | <[email protected]> |
>> To get console error messages start gkrellm from a terminal window
>> and you should see something. If ALSA can't be opened it could be
>> because some other program already has ALSA capture opened and only
>> one program at a time can do this. In that case you either have to
>> quit the other program or let gkrellmss use the esd sound server.
>Oddly, no output at all from a console start. Even with "gkrellm -d
>0x20000" all I get is "--- GKrellM 2.3.4 ---"
>
>> To see if some other program is using capture, run:
>> $ lsof | grep pcm
>> and see if any are using capture: /dev/snd/pcmC0D0c The 'c' at the
>> end indicates it's a capture device, playback devices will end in 'p'.
>ll /dev/snd only shows by-path, seq, timer, controlC0, pcmC0D0p,
>pcmC0D0p, pcmC0D1c, pcmC0C2p.
>lsof shows only controlC0 being used, but kmix (killing it had no
>effect), knotify4, and gkrellm. I suppose I can try killing knotify4,
>but I it sounds like big problems for KDE if that is interfering.
>
>The Capture stuff is OK - but probably moot until I fix the above.
>
>I vaguely remember some issue about not finding one of the relevant
>devices, but I am in the audio group, and /dev includes mixer, dsp,
>audio, and the snd directory - all 660 permissions. I also get the
>same behavior running gkrellm as root.
I've got two things you can try:
1) Since you say you don't have a C0D0c device but do have a C0D1c device,
try this: quit gkrellm, then edit your ~/.gkrellm2/user-config file and change the line:
sound ALSA device plughw:0,0
to
sound ALSA device plughw:0,1
And restart gkrellm.
If that doesn't do any good, then...
2) Can you compile a new gkrellmss? I have a gkrellmss with additional
debugging and if you can run it the error popup should give an appropriate
error message instead of just saying "check for a console message".
It should determine if the problem is resource busy or permissions or
whatever.
In case you can, there is a tarball:
http://members.dslextreme.com/users/billw/test/gkrellmss.tar.gz
Untar it somewhere, then do:
$ cd gkrellmss
$ make
If make succeeds run:
$ gkrellm -p src/gkrellmss.so
and see what error message pops up.
The complication you might have in compiling gkrellmss is that you will
need to have some development packages installed:
fftw-dev or libfftw3-dev
libasound2-dev
libesd0-dev (optional, but needed for esound support)
These are the package names on Debian but should be similar for
other distributions.
Bill
______________________________________________
Gkrellm mailing list
[email protected]
Read archives-join-leave-set RSS feed:
http://archive.lists.netservicesgroup.com
This service is provided by The Network Services Group:
http://www.netservicesgroup.com