FWIW I've just checked this with one of my instances.
I'm unable to replicate the issue with Guacamole 1.0.0, MySQL 5.7.27,
Ubuntu 16.04.6, Pacific TZ.
In the past I've found weird things can happen around timezones and so I
did try setting different TZ's in Guacamole (keeping the system TZ
intact) but couldn't get it to operate differently.
As I recall this was a new installation of 1.0.0, if yours is an upgrade
I wonder if there's some hangover that's causing an issue from your
0.9.13 install?
On 9/10/2019 11:57 a.m., Nick Couchman wrote:
On Tue, Oct 8, 2019 at 6:45 PM Nick Couchman <[email protected]
<mailto:[email protected]>> wrote:
On Tue, Oct 8, 2019 at 5:57 PM Nick Couchman <[email protected]
<mailto:[email protected]>> wrote:
On Mon, Oct 7, 2019 at 1:02 PM Steven Pollock
<[email protected] <mailto:[email protected]>> wrote:
Thanks Nick,
I have the 0.9.13 & 1.0.0 side by side and they have
exactly the same system time and are using the same
backend DB.
I'll have to spin up 1.0.0 and see what happens, but I'm
testing with git code (not sure exact version right now) and
PostgreSQL as the DB, and I am not seeing this behavior. I go
into the GUI, create a test user, set the user's access times
and account validity dates, along with timezone, and the dates
do not move. I can subsequently go in and adjust them and
they stay consistent with what I input on the GUI side.
I'll see what happens on 1.0.0.
I have confirmed that version 1.0.0 with PostgreSQL behaves as
expected - the date does not change when the user account is
created/saved.
It appears to work fine for me on version 1.0.0. My database server
is 5.5.60-MariaDB MariaDB Server, running on CentOS7.
-Nick
