Bug 106360 - alarm.py: fails alarm for next day
Summary: alarm.py: fails alarm for next day
Alias: None
Product: amarok
Classification: Applications
Component: Tools/Script Manager (show other bugs)
Version: 1.2.3
Platform: Debian testing Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Amarok Developers
Depends on:
Reported: 2005-05-27 02:20 UTC by Adeodato Simó
Modified: 2006-06-11 12:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Adeodato Simó 2005-05-27 02:20:57 UTC
Hello, I got this report at the Debian BTS (http://bugs.debian.org/309856, 
reported by Cruz Fernandez <cruz@chuchuwa.com.ar>): 
The alarm.py script (in /usr/share/apps/amarok/scripts/alarm/ ) doesn't 
work for a time of the next day, because it asumes the time is of the 
current day. 
Possible solution, add the seconds in a day to secondsleft: 
<             if secondsleft < 0: 
<               secondsleft += 60 * 60 * 24 
Nevertheless, I see in the page of the script 
(http://www.kde-apps.org/content/show.php?content=23160) that there's a more 
recent version than the one that amarok ships. At a first glance, it seems 
that it fixes Cruz's problem, so updatating it globally would be an option 
Comment 1 Greg Meyer 2006-03-01 03:20:57 UTC
Alarm.py has been removed from amaroK proper so I am closing this bug.