Recent changes to bugs

Install the updated version on Ubuntu 9.04 64 bit?

Archaeomanda — Tue, 26 Jan 2010 10:09:27 -0000

I like the timer applet but I wanted to get the sound working. I noticed in an earlier thread that this was fixed in the later version, but the Ubuntu Jaunty (9.04) repository is out of date. I thought this might be the problem, so I tried uninstalling 2.0 via Synaptic, and then installing from the source followint the instructions on (http://timerapplet.sourceforge.net/). Now when I try to add it to the panel I get the message "The panel encountered a problem while loading "OAFIID:TimerApplet". Do you want to delete the applet from your configuration?"

I don't really know what to do next to try and get the current versio working. Any tips? I tried asking on the Ubuntu forum but I thought I might go straight to the source as well. I am running the 64 bit version of Ubuntu, if it makes any difference.

Thanks.

option to repeat the sound?

Anonymous — Thu, 03 Dec 2009 03:48:19 -0000

a lot of the sounds that come in linux distros by default are too short to be good at alerting the user of the timer going off. can you have an option to repeat the sound?

Doesn't play sound by default

Anonymous — Thu, 03 Dec 2009 03:47:12 -0000

Hi, the first time I used the timer applet, I didn't know sound notification was turned off by default. I expected it, and was using it to time meditation. I ended up meditating a lot longer than I meant to because I never heard it go off - doh! Does it make sense to have sounds play by default? Or have a checkbox or some note in the 'start timer' dialog so you know if it is or isn't going to make a sound? For many uses (meditation is one, but any usage where you use the computer as a timer and put your attention elsewhere, such as to a book or the TV or your family) I think sound is expected, because the icon is a kitchen timer and kitchen timers work primarily on sound, not visual effects.

It crashed

Anonymous — Sat, 24 Oct 2009 20:08:54 -0000

It crashed

timer-applet Python code contains several syntax errors

Martin Olsson — Thu, 08 Oct 2009 19:21:36 -0000

Given that I just ran into this bug a few moment ago:
https://sourceforge.net/tracker/?func=detail&aid=2874996&group_id=127778&atid=709446

... I was thinking that you probably just wrote this Python code without running it through a static analysis tool.
Since Python doesn't do static type checking, it's easy to ship buggy code; code that can never run correctly.

It would be neat if you took some time to run pylint, pyflakes and pychecker on timer-applet. This will most certainly find some real bugs!
For example, these are all the syntax _errors_ (not warnings but hard errors) that pylint finds in timer-applet.

(PS. Thanks for a great applet, I use it every day!)

mnemo@kingfish:/usr/lib/python2.6/dist-packages/timerapplet$ find . -name \*.py | xargs pylint -e
No config file found, using default configuration
************* Module controllers.TimerManagerService
E: 30:TimerManagerService.create_and_register_timer_id: Undefined variable 'uuid'
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.RuntimeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
************* Module ui.ScrollableButtonList
E: 36:ScrollableButtonList.__init__: Class 'style' has no 'base' member
************* Module timerapplet.ui.PulseButton
E: 49:PulseButton._on_timeout: Class 'window' has no 'invalidate_rect' member
E: 56:PulseButton.do_expose_event: Class 'allocation' has no 'width' member
E: 56:PulseButton.do_expose_event: Class 'allocation' has no 'height' member
************* Module timerapplet.ui.ContinueTimerDialog
E: 33:ContinueTimerDialog.__init__: Class 'vbox' has no 'props' member
E: 50:ContinueTimerDialog.__init__: Class 'vbox' has no 'pack_start' member
************* Module timerapplet.ui.PieMeter
E: 34:PieMeter.set_progress: Class 'window' has no 'invalidate_rect' member
E: 43:PieMeter.set_fill_color: Class 'window' has no 'invalidate_rect' member
E: 53:PieMeter.do_expose_event: Class 'allocation' has no 'x' member
E: 53:PieMeter.do_expose_event: Class 'allocation' has no 'width' member
E: 54:PieMeter.do_expose_event: Class 'allocation' has no 'y' member
E: 54:PieMeter.do_expose_event: Class 'allocation' has no 'height' member
E: 55:PieMeter.do_expose_event: Class 'allocation' has no 'width' member
E: 55:PieMeter.do_expose_event: Class 'allocation' has no 'height' member

timer-applet uses == when it means = (causing syntax error)

Martin Olsson — Thu, 08 Oct 2009 18:57:16 -0000

This is on one of the rare error code paths so that's why it was never found. It says:

err, debug == message.parse_error()

...and the error is that "err" is undefined. But the code was probably meant to say = instead so that "err" is written rather than read. This code is only executed if A) you enabled sound, and B) for some reason the system fails to play sounds.

Downstream bug report is here:
https://bugs.launchpad.net/ubuntu/+source/timer-applet/+bug/446568

add a note so you know what is up/due/expired

Anonymous — Sun, 04 Oct 2009 12:27:05 -0000

When the timer is up, it would be great to have reminder of what you are suppose to do.

Unfortunately, a reminder is composed of two things: 1. an alert/stimulus (flashing, sound, or something else visible/audible), 2. the context

For example, a timer is setup with inputs: 1. 45 minutes, 2. flip roast -> when the 45 mins. is up, a popup tells us to flip the roast!

I think this is a great application. I use it all the time, but sometimes I forget what the timer is for. Having an integrated context would make this application solve the reminder problem beyond alarm clock or egg timer traditional way.

crashes when sound fails to play

Anonymous — Sun, 20 Sep 2009 20:11:26 -0000

Ubuntu's crash detector notified me of this error when timers complete:

Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/timerapplet/controllers/TimerApplet.py", line 97, in bus_event
err, debug == message.parse_error()
NameError: global name 'err' is not defined

Obviously, the == (comparison) should be an = (assignment).

Small typo in description

Havoc Xphere — Mon, 29 Jun 2009 11:09:36 -0000

The description listed when adding the applet to a gnome panel. ("recive")

Fedora 10 - Applet doesn't redraw correctly after restart

Anonymous — Thu, 07 May 2009 19:19:07 -0000

timer-applet 2.0.1 running on Fedora 10. After finish a cycle, when the timer is flashing, right-click 'Restart' does not redraw the applet, but leaves a weird border from the area that was flashing. Example attached.