Bug 189746

Summary:	Year cannot be entered directly in clock applet
Product:	[Fedora] Fedora	Reporter:	Radek Bíba <rbiba>
Component:	kdebase	Assignee:	Petr Rockai <prockai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	bugzilla
Target Milestone:	---	Keywords:	Regression, Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kdebase-3.5.8-5.fc8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-11-12 16:02:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Radek Bíba 2006-04-24 10:20:24 UTC

Description of problem:
Previously, clock applet allowed to jump to arbitrary year in calendar by
clicking on the button with year and entering it. Now, typing in the year and
pressing Enter does nothing.

Version-Release number of selected component (if applicable):
kdebase-3.5.2-0.2.fc5 (not sure if kdebase it the right package, though)

How reproducible:
Always

Steps to Reproduce:
1. click on clock applet in kicker
2. click on year button
3. type a year, press enter
  
Actual results:
nothing is happening; input field stays displayed, year is unchanged

Expected results:
year is changed and selected month and day in the entered year are displayed

Comment 1 Petr Rockai 2006-05-05 11:27:11 UTC

Ack, happens here too. Upstream problem apparently. Either kdebase or 
kdelibs, will look into it as soon as i roll out a decent development 
environment for fc5 kde :-).

Comment 2 Than Ngo 2006-05-19 16:52:22 UTC

anyhow i cannot reproduce this problem with current FC5-update. Please reopen it
again if it still appears. Thanks

Comment 3 Radek Bíba 2006-05-19 17:56:22 UTC

Interesting... I can reproduce it absolutely easily. Though I've found a
workaround - displayed year changes to what I entered if I click somewhere outside
the input field.

I have even the latest kde* updates (e.g. kdelibs-3.5.2-0.2.fc5) and I've even
rebooted my box since them so I'm sure I'm running the latest available KDE for
FC5.

Comment 4 Radek Bíba 2007-11-12 16:02:36 UTC

I'm not seeing this error anymore in F8.