Bug 1038909 - sunrise sunset origion time zone
Summary: sunrise sunset origion time zone
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-clocks
Version: 19
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: gnome-sig
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-06 06:38 UTC by Noori
Modified: 2015-02-17 19:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:33:30 UTC
Type: Bug


Attachments (Terms of Use)

Description Noori 2013-12-06 06:38:56 UTC
In gnome-clocks sunrise and sunset of every city that we add shows in our system time zone, but its better to show that in each city time zone or UTC.
I think its needed that gnome-clocks has an option for selecting each city sunrise sunset time to select {current, UTC, selected city time zone}.

Comment 1 Mathieu Bridon 2013-12-06 09:44:58 UTC
Thanks for the bug report.

Can I ask you to try this test package, to see if it fixes your issue?

* If you are using a 32 bits system:
  http://koji.fedoraproject.org/koji/taskinfo?taskID=6263419

* If you are using a 64 bits system:
  http://koji.fedoraproject.org/koji/taskinfo?taskID=6263418

(scroll down to find the packages)

Comment 2 Mathieu Bridon 2013-12-06 09:45:59 UTC
Note: this is the same test package as for your other bug 1038906.

Comment 3 Noori 2013-12-06 14:56:58 UTC
I test 64 bits system

Section 1 "world" time and sunrise sunset times is OK.

Section 2 "Alarm" at new alarm dialog show minute:hour (wrong) but after creating new alarm it will be shown correctly (hour:minute)

Section 3 "Chronometer" it's wrong (second:minute)

Section 4 "Stopwatch" it's OK.

Thanks

Comment 4 Noori 2013-12-06 15:01:13 UTC
Sorry I write https://bugzilla.redhat.com/show_bug.cgi?id=1038906 answers here

this bug is resolved in  http://koji.fedoraproject.org/koji/taskinfo?taskID=6263418

Thanks

Comment 5 Mathieu Bridon 2013-12-09 06:55:29 UTC
Ok, glad I found the right fix. :)

Let's follow up in 1038906 about the remaining issues.

Comment 6 Fedora Admin XMLRPC Client 2014-12-02 14:23:18 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora End Of Life 2015-01-09 20:47:58 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 8 Fedora End Of Life 2015-02-17 19:33:30 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


Note You need to log in before you can comment on or make changes to this bug.