xclock -twentyfour option ignored

Bug #394430 reported by Josh Kupershmidt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
x11-apps (Debian)
Won't Fix
Unknown
x11-apps (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: xorg

(This bug report arises from Ubuntu Question 75465 :
 https://answers.launchpad.net/ubuntu/+source/xclock/+question/75465 )

This bug dates to at least 2006. Basically, running "xclock -digital" should give you a small window with a digital clock. Adding the option "-twentyfour" is supposed to force the clock to display the time in 24-hour format. Similarly, the option "-twelve" is supposed to force the clock to display the time in 12-hour format.

What actually happens is that xclock's digital output will be the same regardless of the -twelve or -twentyfour flag passed. For me and the original poster of Question 75465, the time is always displayed in twelve-hour format. There is an ancient debian bug about the same problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352967

I'm experiencing this issue on Intrepid. I am using version 1:7.4~5ubuntu3 of the 'xorg' package. Running Xorg -version says:

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux jk-d420 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 i686
Build Date: 09 March 2009 10:48:54AM
xorg-server 2:1.5.2-2ubuntu3.1 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present

Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → x11-apps (Ubuntu)
Revision history for this message
Rob W. Brooks (rob-atomicpenguin) wrote :

Thanks for including the related Debian bug.

Changed in x11-apps (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
tags: added: intrepid
Timo Aaltonen (tjaalton)
Changed in x11-apps (Ubuntu):
importance: Undecided → Low
Changed in x11-apps (Debian):
status: Unknown → Won't Fix
Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in x11-apps (Ubuntu):
status: Confirmed → New
status: New → Incomplete
tags: added: maverick
tags: added: natty
Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

Looks like Josh should have set status back from Incomplete. I'm seeing the same issue here so setting to Confirmed.

Changed in x11-apps (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Simon Le Pine (simonguide) wrote :

Found this as it is affecting me in CrunchBang. Interesting side note, if one uses the -b (brief) argument the clock shows properly in 24-hour time.

Changed in x11-apps (Debian):
status: Won't Fix → Fix Released
Changed in x11-apps (Debian):
status: Fix Released → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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