Re: new attempt to solve an old problem with gkrellmsss

Jack <[email protected]> Sat, 18 Sep 2010 16:16:31 -0400
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <1284840991.25876.0@ffortso4>
On 2010.09.17 19:14, Bill Wilson wrote:
> On Wed, 15 Sep 2010 11:18:26 -0400
> Jack <[email protected]> wrote:
>>> 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.
>> The popup now is "Can't open ALSA device plughw:0.0.  Invalid  
>> argument"  Maybe I'll try running through gdb and see if I can  
>> figure out if there is something funny with my ALSA.

> I've got  another tarball for you to try, same link:
>    http://members.dslextreme.com/users/billw/test/gkrellmss.tar.gz
> It should resolve the error better, but I've also made a change which  
> I think gives it a chance of actually working.  In any case run it  
> like so:
>    $ gkrellm -debug46 -p src/gkrellmss.so
> There will be a few console diagnostic lines and the popup will show  
> some info if the open fails.  If it works, I'm still interested in  
> what the console lines say and the popup won't appear.

Console says:
  ALSA set periods min 2 (1)
  ALSA set periods first 2 (1)

Popup says:
  Can't set buffer size. ALSA device: default
  snd error: Invalid argument

After I click the popup, the console then shows
  ALSA set periods min 2 (0)
  ALSA set periods first 2 (0)


______________________________________________
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