Thanks jr. I seem to have left some error-trapping code in the executable which was causing a start failure(and presumably the same for the library). The remaining problem is the instability of the Mono front end when things don't run sweetly. I think that if I get this boilerplate stuff fixed so that it executes cleanly without bashing the clock interface, then I can return to using a .so with interop.(Which I was quite proud of, as this is a cross-platform area which won't be disappearing soon).
Having said which, if you go to Users And Groups in the Ubuntu interface, you can add users to 'audio' and 'pulse-access'. Simono On Mon, 2010-10-18 at 17:34 +0100, jr wrote: > On 18 October 2010 16:55, Simon O'Riordan <[email protected]> wrote: > > .. just that my previous experiences hadn't led me to expect any nasties. > > I daresay we' ve all been there. :-) > > > I'm getting some peculiar effects, the ALSA programme doesn't execute in > > some directories, it does in others, which leads me to believe that > > there really may be some permission issues with the ALSA/pulse PCM > > setup. > > what about the ownership of the ALSA files and libraries? (on my > slackware box it's all root:root by default) > > also, is the execute problem the same for all users? > -- Next meeting: Crown Hotel, Blandford Forum, Tuesday 2010-11-02 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
