Alarm Clock Applet

unable to set the alarm beyond 13:49:49 in jaunty

Bug #333700 reported by manishmahabir
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Alarm Clock Applet
Fix Released
Critical
Johannes H. Jensen
Declined for Trunk by Johannes H. Jensen

Bug Description

i am unable to unable to set the alarm beyond 13:49:49.
if i type anything more than 13 in hrs and 49 in min and seconds, as soon as i press enter the time automatically is set as 13 in hrs and 49 in min and sec.
i am using 0.2.4 on jaunty fully updated as on 24th Feb.
i am adding the screenshot....

Revision history for this message
manishmahabir (manishmahabir) wrote :
Revision history for this message
manishmahabir (manishmahabir) wrote :

the same file when installed in intreped works fine.

Revision history for this message
Johannes H. Jensen (joh) wrote :

Thank you for your bug report, I'll look into it.

Revision history for this message
Mike Auty (mike-auty) wrote :

Hmmm, I've had a poke about using gtkparasite, and found that it appears to be related to the gtkspinbuttons, in that they're stopping the time elements being moved above 13, 49 and 49 respectively (that means you can't even set times of 08:55:55).

After a bit more digging, it appears this is identical to the upstream gnome bug 551740. It appears it can be fixed by setting a 0 page_size value. Attached is a patch that fixes this issue by setting all the page_size values to 0 in the glade file...

[1] http://bugzilla.gnome.org/show_bug.cgi?id=551740

Revision history for this message
Johannes H. Jensen (joh) wrote :

Thanks for the patch and comments, Mike! I've applied your patch and committed the changes. Could you please test the latest revision (124) and confirm that it's now indeed working correctly in jaunty?

Changed in alarm-clock:
assignee: nobody → joh
importance: Undecided → Critical
status: New → In Progress
Revision history for this message
Johannes H. Jensen (joh) wrote :

Actually, this bug was fixed in rev 120 but a release containing it has not yet been done. I'll prepare a 0.2.5 release shortly.

Changed in alarm-clock:
status: In Progress → Fix Committed
Johannes H. Jensen (joh)
Changed in alarm-clock:
status: Fix Committed → Fix Released
Revision history for this message
Mike Auty (mike-auty) wrote :

Hiya, I don't actually use Jaunty, I just needed an alarm clock today, so built an ebuild for Gentoo. I'm using the latest gnome-2.26 packages, and that's probably why I hit the problem. I didn't check the development branch to spot the fix, and I saw this open bug.

I've just built from r124, and the problem is indeed fixed, thanks for pushing out a new release. 5:)

Revision history for this message
manishmahabir (manishmahabir) wrote :

it works fine now.thanks for your efforts!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.