Re: [Dorset] Ready
Thanks to John's excellent suggestion about aplay on the command line, I have now been able to make the clock work on 10.10 and SimplyMEPIS8.5 without any apparent trouble. However, there may be some holes in the Mono implementation used by 10.04 that result in unreliability when initiating a thread from a timer handler(which is allowed, even mandatory, in the original dot net). I will check which Mono versions are being used by 10.10 and 10.04 to confirm. Simono On Tue, 2010-10-19 at 18:46 +0100, John Carlyle-Clarke wrote: > On 19/10/10 17:13, Simon O'Riordan wrote: > > Incidentally, did I remember to tell users to set the permissions of > > Sounder1e to 'executable' after download? I think that's the error. > > Meanwhile, I'm continuing testing. > > Hi Simon... > > I tried this just now and it seems to hide the error, but doesn't > produce any sound. > > How should Sounder1e be executed? > > joh...@liberator:~/simono$ ./Sounder1e wakebjorn.wav > ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse > Segmentation fault > joh...@liberator:~/simono$ ./Sounder1e > ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse > Segmentation fault > > > -- > 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 -- 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
Re: [Dorset] Ready
On Tue, 2010-10-19 at 16:48 +0100, John Carlyle-Clarke wrote: > On 19/10/10 16:11, Simon O'Riordan wrote: > > The 'Alarm Clock' utility is now ready for download. Read the Readme, > > choose your type, and if you want, give me feedback so I can improve it. > > Simono > > I think the gold standard is that it should be at least as good as using > "at". For example:- > > joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:45 > job 8 at Tue Oct 19 16:45:00 2010 > joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:50 > job 9 at Tue Oct 19 16:50:00 2010 > joh...@liberator:~/simono$ atq > 8 Tue Oct 19 16:45:00 2010 a johncc > 9 Tue Oct 19 16:50:00 2010 a johncc > joh...@liberator:~/simono$ atrm 9 > joh...@liberator:~/simono$ atq > 8 Tue Oct 19 16:45:00 2010 a johncc > joh...@liberator:~/simono$ > > So as a suggested feature list:- > > * execution of arbitrary commands when alarms go off, as well as a > preset for sounds (perhaps scan for aplay, paplay, play, mplayer ...) > * add/remove/list multiple alarms > * persist alarms to a text file in ~/config between instances > > Perhaps you could also look into splitting it into a daemon and a front > end, communicating with sockets? > > Best regards, > > John Isn't this the thing about Open Source? Simon makes the source code available, and other people can add their own desired bells and whistles. Cheers, PM -- 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
Re: [Dorset] Ready
Now that you mention it, today my Process version won't work on my 10.04 no matter what I do(apart from running the base application in the debugger). But it does work on 10.10. The error is very strange, could have sworn it was working on both yesterday. But maybe I'm mistaken again. Interestingly, the 10.04 Monodevelop doesn't have a debugger, but the 10.10 version does; when putting in debug info manually(if in doubt, print it out) I'm not getting any information at all, which suggests that Mono isn't properly invoking Process.Start() on 10.04 for this application. Which is strange because it was doing perfectly well with other programmes. On a happier note, the Interop version works on 10.04. Simono ps-Code for Sounder1e on way. On Tue, 2010-10-19 at 18:46 +0100, John Carlyle-Clarke wrote: > On 19/10/10 17:13, Simon O'Riordan wrote: > > Incidentally, did I remember to tell users to set the permissions of > > Sounder1e to 'executable' after download? I think that's the error. > > Meanwhile, I'm continuing testing. > > Hi Simon... > > I tried this just now and it seems to hide the error, but doesn't > produce any sound. > > How should Sounder1e be executed? > > joh...@liberator:~/simono$ ./Sounder1e wakebjorn.wav > ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse > Segmentation fault > joh...@liberator:~/simono$ ./Sounder1e > ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse > Segmentation fault > > > -- > 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 -- 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
Re: [Dorset] Ready
On 19/10/10 17:13, Simon O'Riordan wrote: Incidentally, did I remember to tell users to set the permissions of Sounder1e to 'executable' after download? I think that's the error. Meanwhile, I'm continuing testing. Hi Simon... I tried this just now and it seems to hide the error, but doesn't produce any sound. How should Sounder1e be executed? joh...@liberator:~/simono$ ./Sounder1e wakebjorn.wav ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse Segmentation fault joh...@liberator:~/simono$ ./Sounder1e ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM pulse Segmentation fault -- 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
Re: [Dorset] Ready
Hi John, looks like a 'File Not Found' error; unless I've put something diabolically wrong up there. The /simono folder should contain that exact file plus all the others. Snooze is possible, needs a little thought. I'll tidy up the code, and send it to you off-list. I'll run a test using a manual mono command, I've been scripting the launch. Simono On Tue, 2010-10-19 at 16:34 +0100, John Carlyle-Clarke wrote: > On 19/10/10 16:11, Simon O'Riordan wrote: > > The 'Alarm Clock' utility is now ready for download. Read the Readme, > > choose your type, and if you want, give me feedback so I can improve it. > > Simono > > I think I tried the process version, in that I got everything that is in > the top-level directory and ran "mono LClock.exe". > > I get a lot of:- > > xdg-open: unexpected argument '/home/johncc/simono/wakemyst.wav' > Try 'xdg-open --help' for more information. > > ... instead of any sound. > > One comment on the UI - it would be nice to get feedback of whether the > alarm is set, and when it's going to go off. If you're really going for > it, how about snooze too? > > Are you going to release the source, out of interest? > > -- > 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 -- 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
Re: [Dorset] Ready
On Tue, 2010-10-19 at 16:48 +0100, John Carlyle-Clarke wrote: > I think the gold standard is that it should be at least as good as using > "at". For example:- > > joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:45 > job 8 at Tue Oct 19 16:45:00 2010 > joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:50 > job 9 at Tue Oct 19 16:50:00 2010 > joh...@liberator:~/simono$ atq > 8 Tue Oct 19 16:45:00 2010 a johncc > 9 Tue Oct 19 16:50:00 2010 a johncc > joh...@liberator:~/simono$ atrm 9 > joh...@liberator:~/simono$ atq > 8 Tue Oct 19 16:45:00 2010 a johncc > joh...@liberator:~/simono$ > > So as a suggested feature list:- > > * execution of arbitrary commands when alarms go off, as well as a > preset for sounds (perhaps scan for aplay, paplay, play, mplayer ...) > * add/remove/list multiple alarms > * persist alarms to a text file in ~/config between instances > > Perhaps you could also look into splitting it into a daemon and a front > end, communicating with sockets? John, I'll certainly look into it. Incidentally, did I remember to tell users to set the permissions of Sounder1e to 'executable' after download? I think that's the error. Meanwhile, I'm continuing testing. Simono -- 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
Re: [Dorset] Ready
On 19/10/10 16:11, Simon O'Riordan wrote: The 'Alarm Clock' utility is now ready for download. Read the Readme, choose your type, and if you want, give me feedback so I can improve it. Simono I think the gold standard is that it should be at least as good as using "at". For example:- joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:45 job 8 at Tue Oct 19 16:45:00 2010 joh...@liberator:~/simono$ echo "aplay wakejap.wav" | at 16:50 job 9 at Tue Oct 19 16:50:00 2010 joh...@liberator:~/simono$ atq 8 Tue Oct 19 16:45:00 2010 a johncc 9 Tue Oct 19 16:50:00 2010 a johncc joh...@liberator:~/simono$ atrm 9 joh...@liberator:~/simono$ atq 8 Tue Oct 19 16:45:00 2010 a johncc joh...@liberator:~/simono$ So as a suggested feature list:- * execution of arbitrary commands when alarms go off, as well as a preset for sounds (perhaps scan for aplay, paplay, play, mplayer ...) * add/remove/list multiple alarms * persist alarms to a text file in ~/config between instances Perhaps you could also look into splitting it into a daemon and a front end, communicating with sockets? Best regards, John -- 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
Re: [Dorset] Ready
On 19/10/10 16:11, Simon O'Riordan wrote: The 'Alarm Clock' utility is now ready for download. Read the Readme, choose your type, and if you want, give me feedback so I can improve it. Simono I think I tried the process version, in that I got everything that is in the top-level directory and ran "mono LClock.exe". I get a lot of:- xdg-open: unexpected argument '/home/johncc/simono/wakemyst.wav' Try 'xdg-open --help' for more information. ... instead of any sound. One comment on the UI - it would be nice to get feedback of whether the alarm is set, and when it's going to go off. If you're really going for it, how about snooze too? Are you going to release the source, out of interest? -- 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
[Dorset] Ready
The 'Alarm Clock' utility is now ready for download. Read the Readme, choose your type, and if you want, give me feedback so I can improve it. Simono -- 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
