Re: new attempt to solve an old problem with gkrellmsss

Jack <[email protected]> Tue, 14 Sep 2010 17:06:08 -0400
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <1284498368.23095.0@ffortso4>
On 2010.09.14 14:52, Bill Wilson wrote:
> On Sat, 04 Sep 2010 13:40:51 -0400 Jack  
> <[email protected]> wrote:

>> I've resurfaced an old problem, and wanted to see if there was ever  
>> any resolution.  It's mentioned in a thread on the Gentoo forums at  
>> http://forums.gentoo.org/viewtopic-t-236638.html, and searching  
>> shows up at least one other thread.  In that case, the solution  
>> seemed to be creating a ~/.asoundrc, but I have not had any luck  
>> with that yet.

>> The problem is that when gkrellmss starts, I get a popup: Can't open  
>> ALSA monitoring.  Look for an "ALSA lib" console error message.  I  
>> now see nothing at all about alsa in my capture of stderr from my X  
>> session, and nothing in /var/log/messages or in dmesg.  The  
>> gkrellmss panel has  "Sound error? Click here to try to open."  In  
>> the past, clicking would eventually get it to work.  Now it just  
>> gives the same popup.
> 
> 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.

______________________________________________
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