Bug#712841: qcontrol: Fan error reported on TS109

2014-01-15 Thread Dermot O'Dwyer
reak; No errors in logs. The rest of qcontrol continues working OK (manual led/buzzer commands). Dermot On 9 January 2014 20:04, Ian Campbell wrote: > On Thu, 2014-01-09 at 09:46 +, Dermot O'Dwyer wrote: >> On 3 January 2014 00:19, Ian Campbell wrote: >> > Dermon, d

Bug#712841: qcontrol: Fan error reported on TS109

2014-01-09 Thread Dermot O'Dwyer
On 3 January 2014 00:19, Ian Campbell wrote: > Dermon, does commenting out the content of temp_high and temp_low in > qcontrol.conf and rebooting still end up with fan_error getting called > lots? Yes, fan_error still gets called when there are empty temp_high and temp_low functions. Dermot --

Bug#712841: qcontrol: Fan error reported on TS109

2013-07-05 Thread Dermot O'Dwyer
On 30 June 2013 15:58, Ian Campbell wrote: > In 0.4.2-7+wheezy2 the fan_error function would have been empty, so do > you know for sure it wasn't being triggered previously too? I reinstalled 0.4.2-7+wheezy2 and added beep to the fan error function. Got plenty of beeps so it would appear that it

Bug#712841: qcontrol: Fan error reported on TS109

2013-06-19 Thread Dermot O'Dwyer
Package: qcontrol Version: 0.5.1-3 Severity: important Tags: upstream On a TS109, after upgrading from 0.4.2-7+wheezy2 to 0.5.1-3 qcontrol then reports fan error in syslog and beeping every minute approximately. Setting SOUND_BUZZER=no in /etc/default/qcontrol does not stop the beeping. I have l

Bug#652373: gnucash: Crashes when trying to disable a scheduled transaction

2011-12-16 Thread Dermot O'Dwyer
Package: gnucash Version: 1:2.4.8-1 Severity: normal Dear Maintainer, * What led up to the situation? A scheduled transaction was scheduled to run once. It has run and I am trying to disable it as it is not currently needed. * What exactly did you do (or not do) that was effective (or

Bug#652370: apticron: Number of packages no longer reported in subject

2011-12-16 Thread Dermot O'Dwyer
Package: apticron Version: 1.1.51 Severity: normal Tags: patch Hello, Changes in Bug #621730 mean the number of packages do not get reported in the subject of the email. MAILX_SUBJECT is defined before NUM_PACKAGES is known. Moving the custom subject block after the NUM_PACKAGES definition resolv

Bug#596919: apticron: DIFF_ONLY reports incorrect number of "packages previously reported to you pending an upgrade"

2010-09-17 Thread Dermot O'Dwyer
I've done some more comprehensive testing on a full system to come up with this: - echo -e "\n(there are other `cat $LAST_RUN_FILE |wc -l` packages previously reported to you pending an upgrade!)" + echo -e "\n(there are $(grep -xf $LAST_RUN_FILE $TMPFILE |wc -l) other p

Bug#596919: apticron: DIFF_ONLY reports incorrect number of "packages previously reported to you pending an upgrade"

2010-09-14 Thread Dermot O'Dwyer
Sorry, The patch should probably be "grep -xF" instead of "grep -F" Regards, Dermot --- apticron 2010-08-30 03:03:39.0 +0100 +++ apticron.modified 2010-09-15 04:19:03.0 +0100 @@ -209,7 +209,7 @@ done if [ "$DIFF_ONLY" = "1" ] && [ -e "$LAST_RUN_FILE" ]; then - echo -e "\n(t

Bug#596919: apticron: DIFF_ONLY reports incorrect number of "packages previously reported to you pending an upgrade"

2010-09-14 Thread Dermot O'Dwyer
Package: apticron Version: 1.1.42 Severity: normal Tags: patch Hello, With DIFF_ONLY set apticron reports that there are X# packages previously reported to you pending an upgrade even if an apt-get dist-upgrade has been run in the period between the current and previous apticron runs. Apticron s