search

neharob / hotot

Automatically exported from code.google.com/p/hotot
0 stars 0 forks source link

Several Errors persistently appear/ Some functions become non-responding #434

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
**Reproduce the problem/ output:
1. Launch Hotot
2. Wait a couple of seconds 
3. Error messages appear and repeatedly appear along the session
"2011-7-21 21:52:1Ooops, An API Error Occurred!
Unknow Error
HTTP Code:403
Reason:error"
4. After clicking "clear and close", they persistently appear over and over 
again.
5. Trying to click the following doesn't respond
 -"reply to MYUSERNAME" in the [Mentions column] 
 -"click to show" in My Tweets Retweeted in [Retweets column]
___________________

**Expected output:
- No display of errors, basically.
- Functions aforementioned work as intended.
___________________

**Environment:
- Hotot 1:0.9.6~hg986-0ubuntu0ppa1~natty1 via PPA @ 
https://launchpad.net/~hotot-team/+archive/ppa
- Ubuntu Natty 11.04; kernel 2.6.38-11-generic
- Gnome 2.32.1

__________________
**Additional Notes:
- In the displayed errors the date reports "2011-7-21 21:52" despite of the 
fact that it's 2011-8-21 21:52 (8 not 7)
- "reply to XUser" in [Home Timeline] column works normally and displays the 
original post being replied to.
- Attached is a debug output.
- Tried to clear all Hotot settings by removing home/.config/hotot/ and 
reconfigured the Twitter account and settings again didn't resolve the problem.

Original issue reported on code.google.com by DieSchwa...@gmail.com on 21 Aug 2011 at 8:19

Attachments:

GoogleCodeExporter commented 9 years ago 
I suffer the exact same symptoms on both Ubuntu Natty and Lucid 
(1:0.9.6~hg986-0ubuntu0ppa1~lucid1). Additionally in the Mentions view the 
reply, favorite etc. buttons don't appear at all on mouseover.

Apparently a very recent update caused these. Until then things were working 
quite nicely.

Original comment by nouseva....@gmail.com on 23 Aug 2011 at 5:18

GoogleCodeExporter commented 9 years ago 
please check your system time setting and timezone settings.

This problem may due to a wrong signature based on a wrong time.

Original comment by 5h3l...@gmail.com on 7 Oct 2011 at 12:06

GoogleCodeExporter commented 9 years ago 
- Both system time settings and timezone settings are properly configured.
- The problem disappeared since 0.9.7.

Original comment by DieSchwa...@gmail.com on 7 Oct 2011 at 12:43