Bug 224782 - Bug: World clock doesn't start in local timezone
Summary: Bug: World clock doesn't start in local timezone
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: plasmoid (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 15:51 UTC by Jeffrey
Modified: 2011-05-26 18:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
World Clock vs panel clock (82.12 KB, image/png)
2010-01-29 15:53 UTC, Jeffrey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2010-01-29 15:51:02 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When logging into KDE, my World Clock doesn't start on my local timezone at all until I pass over it with the mouse, at which point it then shows whichever city and then defaults back to my timezone.

The clock should default to my local timezone immediately.

When the KDE Plasma desktop and Plasmoids are just set up to display information and are not meant as an interactive screen/desktop/computing environment, this issue requires that the desktop is interacted with initially.  In most instances this isn't an issue, but for a display-only environment it is an issue.

Thanks for KDE!
Comment 1 Jeffrey 2010-01-29 15:53:03 UTC
Created attachment 40352 [details]
World Clock vs panel clock

The world clock isn't defaulting to my local time zone until I pass over it with the mouse; the plasma panel clock starts out correctly the first time.
Comment 2 disabled account 2011-05-26 18:06:30 UTC
It works for me in 4.6.2, please reopen if this is still an issue for you.