Bug 328822 - User-specific (non-root) timezone selection
Summary: User-specific (non-root) timezone selection
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_clock (show other bugs)
Version: 4.10.5
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
: 201905 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-12-15 03:02 UTC by Luke-Jr
Modified: 2021-10-08 18:56 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke-Jr 2013-12-15 03:02:03 UTC
To accomplish changing the user's local timezone for applications after KDE has been started, the TZ variable can be initialised with a path to the user's KDE config dir (eg TZ=${KDEHOME}/share/mytime). If ${KDEHOME}/share/mytime does not exist when KDE starts, it can be symlinked to /etc/localtime. 

Reproducible: Always
Comment 1 David Edmundson 2015-02-05 20:14:12 UTC
In what situation would different users be in different timezones on the same machine?

The machine can only be in one place at a time
Comment 2 Luke-Jr 2015-02-05 20:18:30 UTC
(In reply to David Edmundson from comment #1)
> In what situation would different users be in different timezones on the
> same machine?
> 
> The machine can only be in one place at a time

Terminal servers... or even just user preference (I use UTC even though I live in EST5EDT)
Comment 3 David Edmundson 2015-02-05 21:01:01 UTC
OK, 
I'm not super convinced, but I'm not super opposed either.

Feasibility:
QTimeZone internally does make a qgetenv call.
KTimeZoned does not.

So we're going to miss change signals, but it is in an area we can possibly change.

timedated which we are switching to won't support it; that's purely session; though arguably we wouldn't need it in this case.
Comment 4 David Edmundson 2015-02-06 17:59:44 UTC
*** Bug 201905 has been marked as a duplicate of this bug. ***