Gnome Scheduler - hours & minutes fields limited to max of 14 & 49

[DilbertDave]

Binary package hint: gnome-schedule

When creating a new job it is not possible to specify a minutes value greater than 49.
To replicate:
  Open Gnome Schedule
  Click New
  Select 'A Task That Launches One Time'
  In the time minutes field using the Up arrow will only increase the value to 49 minutes.
     Manually entering a value greater than 49 will result in it being saved as 49 minutes.

I'm currently running 9.04 (Jaunty) and Gnome Schedule 2.0.2

[Edit] following on from Glavspirt's comment I can confirm that the hours are limited to a maximum of 14. When I tested this at 20:25 today the up arrow did not increase the hour value as expected (the down arrow was of course disabled). When I reset the date to tomorrow I too could not increase the hour value beyond 14.

[Glavspirt (cerera)]

I have the same trouble, but the hours are limited too to 14 hours.

[GauteHope (eg)]

Following this: http://bugzilla.gnome.org/show_bug.cgi?id=551740

The pagesize has been set to 0 and logically stuff works, fixed in HEAD. A new release is on its way, with better 'support' for X applications and bugfixes, this needs testing but seems to work alright on Ubuntu setups.

[DilbertDave (dave-onthefencedevelopment)]

I've just installed the patch on my Jaunty installation but the issue remains, i.e. I still cannot schedule a task for later than 14:49

[GauteHope (eg)]

Patch ? Did you try a fresh clone of gnome-schedule:
$ git clone git://git.gnome.org/gnome-schedule

Remember to either install it in a prefix, ie "currentdir/inst" (after a clone):
$ cd gnome-schedule
$ ./autogen --prefix=$(pwd)/inst
$ make && make install

and run it from there (remember the ./):
$ cd inst/bin
$ ./gnome-schedule

You need normal gnome build tools.

- gaute

[GauteHope (eg)]

Removed bug watch as this is a different project and has very little to do with gnome-schedule, except they suffered the same problem in pygtk.

- gaute

[Frederick IV Barbarossa (f3rn4nd0-n3gr0)]

(I don't use the Gnome Scheduler, but I suspect this might be the same bug.)
I have the same problem, but in the Alarm plugin in the Audacious Audio Player.
I can't set the alarm to bigger times than 13h and 49m.
(I'm using Ubuntu 9.04.)

[GauteHope (eg)]

This has been resolved in the newest version of Gnome-schedule.

[Rashid Khan (launchnoir-3-fliplap)]

I know this has been resolved in the newest version, but as of today there's no deb or tarball of it.

There is an easy fix for those that only want to repair their gnome-schedule installation and not deal with downloading everything required to build gnome-schedule from SVN (for example those of us in countries where we pay by the kilobyte for data).

Open gnome-schedule.glade (/usr/share/gnome-schedule on ubuntu) with your text editor of choice. Do a search for "10 10" and replace it with "0 0", without the quotes of course. No fuss, no muss, all fixed.

[Chris Coulson (chrisccoulson)]

This should not be fix released, as the new version is not in Ubuntu yet

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-schedule - 2.1.0-0ubuntu1

---------------
gnome-schedule (2.1.0-0ubuntu1) karmic; urgency=low

  * New upstream version (LP: #377332):
    - Use correct page_size in GtkAdjustment's (LP: #370754).
    - Don't only show desktop file in GNOME (LP: #370828).
  * debian/control:
    - Build-depend on intltool.
    - Update Standards-Version to 3.8.2 - no changes required.

 -- Chris Coulson <email address hidden> Sun, 09 Aug 2009 00:30:33 +0100

[Frederick IV Barbarossa (f3rn4nd0-n3gr0)]

Nope. I still have this problem in the Alarm plugin in Audacious. Can't set it to times later than 13h49m.
I suspect this is the same bug.
I found a "patch", but it's not for the distribution or package version I'm using.
http://bugs.gentoo.org/272016

[Chris Coulson (chrisccoulson)]

This bug is about gnome-schedule, and is now fixed - if you have an issue with audacious then you need to report that separately.

[Frederick IV Barbarossa (f3rn4nd0-n3gr0)]

OK.
Because it is the same problem and it appeared at the same time, I thought it was not a problem in gnome-schedule itself, but a common one between gnome-schedule and audacious, and that it was being caused by some common library, or so, that both used.
I'll try to search better in here for my bug, and if I can't find it I'll make a report myself.