Bug 1311513

Summary: coordinate precision cannot be changed
Product: [Fedora] Fedora Reporter: Maurizio Paolini <paolini>
Component: kigAssignee: Kevin Kofler <kevin>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: jreznik, kevin, ovasik, rdieter, than
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kig-19.08.3-3.fc30 kig-19.08.3-3.fc31 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-12 01:14:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maurizio Paolini 2016-02-24 11:45:32 UTC
Description of problem: the number of decimal digits displayed in labels cannot be changed


Version-Release number of selected component (if applicable):
kig-15.12.1-1.fc23.i686


How reproducible: There is an input panel for changing the value, but it is
missing an "OK" button!


Steps to Reproduce:
1. Start kig
2. Open "Settings" menu
3. Chose "Set coordinate precision"

Actual results:
You can cange the number in the input field, but there is no way to
accept the value (no "OK" button visible)


Additional info: I did not yet tried to compile from git sources to see if
this is an upstream problem

Comment 1 Fedora End Of Life 2016-11-24 15:44:26 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Maurizio Paolini 2016-11-24 19:58:46 UTC
The problem is still there in Fedora 24, kig version
kig-16.08.2-1.fc24.i686

However, the problem is also present after build of the latest git version,
checked out today

Comment 3 Fedora End Of Life 2017-07-25 20:15:24 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Maurizio Paolini 2017-07-25 20:58:05 UTC
Problem still present in Fedora 25

Comment 5 Fedora End Of Life 2017-11-16 19:02:21 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-12-12 11:04:51 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 7 Maurizio Paolini 2017-12-12 14:59:32 UTC
I tested the reported bug against Fedora 27 and it is still present exactly in the form described in the initial report.

Comment 8 Ben Cotton 2018-11-27 17:50:54 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Maurizio Paolini 2018-11-27 18:23:11 UTC
The problem is still present in Fedora 29, kig version
kig-18.04.3-1.fc29.x86_64

however, what is the point of reporting bugs if they are not addressed?
The original bug report was create for a Fedora 23!

Maurizio

Comment 10 Ben Cotton 2019-10-31 20:26:42 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Ben Cotton 2019-11-27 20:03:12 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 12 Maurizio Paolini 2019-11-28 07:27:40 UTC
The problem is still present in Fedora 31

Comment 13 Kevin Kofler 2019-11-28 22:52:50 UTC
*** Bug 1777997 has been marked as a duplicate of this bug. ***

Comment 14 Kevin Kofler 2019-11-28 22:58:16 UTC
I can confirm this. I don't see a bug filed upstream at https://bugs.kde.org/ yet, can you please file one there?

Comment 15 Maurizio Paolini 2019-11-28 23:50:39 UTC
I filed a bug report upstream: https://bugs.kde.org/show_bug.cgi?id=414641

Comment 16 Kevin Kofler 2019-12-23 08:35:45 UTC
There's now an upstream fix in the release/19.12 branch: https://cgit.kde.org/kig.git/commit/?id=63e4bc0f9f82162f3b78f0c565c29359ae906ec2

Comment 17 Fedora Update System 2019-12-23 18:25:52 UTC
FEDORA-2019-cd4008c5ce has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cd4008c5ce

Comment 18 Fedora Update System 2019-12-23 18:25:52 UTC
FEDORA-2019-cd4008c5ce has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cd4008c5ce

Comment 19 Fedora Update System 2019-12-23 18:27:50 UTC
FEDORA-2019-78e69740a0 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-78e69740a0

Comment 20 Fedora Update System 2019-12-23 18:27:50 UTC
FEDORA-2019-78e69740a0 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-78e69740a0

Comment 21 Fedora Update System 2020-01-03 21:32:06 UTC
kig-19.08.3-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-78e69740a0

Comment 22 Fedora Update System 2020-01-04 22:20:58 UTC
kig-19.08.3-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-cd4008c5ce

Comment 23 Fedora Update System 2020-01-12 01:14:47 UTC
kig-19.08.3-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 24 Fedora Update System 2020-01-12 01:41:09 UTC
kig-19.08.3-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.