** Changed in: gtwitter (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/201766
Title:
gtwitter computes times as if local clock is set to UTC
To manage not
** Changed in: gtwitter (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
--
gtwitter computes times as if local clock is set to UTC
https://bugs.launchpad.net/bugs/201766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: gtwitter (Debian)
Status: Unknown => New
--
gtwitter computes times as if local clock is set to UTC
https://bugs.launchpad.net/bugs/201766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: gtwitter (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479348
Importance: Unknown
Status: Unknown
--
gtwitter computes times as if local clock is set to UTC
https://bugs.launchpad.net/bugs/201766
You received this bug notification because you are a me
HOSONO: I can confirm that the environment setting issued with the
application does resolve the time issue. I find that to be an
acceptable solution to my issue. I have modified my session start
command and it has resolved the time of post issue. Thank you for your
help.
--
gtwitter computes t
I can confirm the bug as well.
LSB output:
:~$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
Timezone:
:~$ cat /etc/timezone
Australia/Melbourne
--
gtwitter computes times as if local clock is set to UTC
https://bugs.launchpad.net/bugs/201766
You received this bug notifica
It is also reported on the Debian BTS, #479348.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479348
It seems to be an upstream bug.
If gTwitter is executed with the line:
> env TZ=JST gtwitter
it shows the right times.
--
gtwitter computes times as if local clock is set to UTC
https://bugs
After making adjustment in timezone (something wrong and back to correct
Europe/Rome) then I have these differences between my Gutsy system and
Hardy system:
Gutsy==
:~$ cat /etc/adjtime
1.296468 1208736310 0.00
1208736310
UTC
:~$ cat /etc/timezone
User defined
===
Output of lsb_release and adjtime from system with gtwitter (current
version) showing correct time for the posts.
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 7.10
Release:7.10
Codename: gutsy
~$ cat /etc/adjtime
1.296468 1208736310 0
I can confirm this behavior for myself at GMT+2 and all posts in twitter
are listed as "about 2 hours ago". On my Gutsy 7.10 system, the exact
same post appears with "2 minutes ago".
What is Hardy doing different than Gutsy for time?
--
gtwitter computes times as if local clock is set to UTC
htt
** Tags added: regression
--
gtwitter computes times as if local clock is set to UTC
https://bugs.launchpad.net/bugs/201766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
11 matches
Mail list logo
