Closed githubrsys closed 10 years ago
This was caused while libturpial was not installed. I think it would make sense, that the requirements are checked before compile process. After installing libturpial git development branch, removing the local config and installing turpial again I was able to connect to the timeline.
Hi,
I got the latest development branch on opensuse 13.1 ran setup.py, removed all local settings folders and fired up turipal.
I was able to add two accounts without problem, but when it comes to column setup, I am stuck. The accounts are greyed out and I cannot add a column.
So I killed turipal and started it again from cli and face a 403 error on json request but I am 100% sure to have set my password correct as it was accepted on former creation.
turpial -d \ Message: pygobject_register_sinkfunc is deprecated (GstObject) DEBUG::Using gst as sound system /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/init.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) DEBUG:AppConfig:Started DEBUG:AppConfig:CONFIG_FILE: /home/myUsername/.config/turpial/config DEBUG:AppConfig:FILTERS_FILE: /home/myUsername/.config/turpial/filtered DEBUG:AppConfig:FRIENDS_FILE: /home/myUsername/.config/turpial/friends DEBUG:AppConfig:Loaded configuration DEBUG:change me:Started DEBUG:AccountConfig:CACHEDIR: /home/myUsername/.cache/turpial/twitterAccount1-twitter/images DEBUG:AccountConfig:CONFIGFILE: /home/myUsername/.config/turpial/accounts/twitterAccount1-twitter/config DEBUG:AccountConfig:Loaded configuration DEBUG:Controller:Starting Turpial 3.0 DEBUG:TurpialHTTP:Validated SSL cert for host: api.twitter.com INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): api.twitter.com DEBUG:requests.packages.urllib3.connectionpool:"GET /1.1/account/verify_credentials.json HTTP/1.1" 200 1040 INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): api.twitter.com DEBUG:requests.packages.urllib3.connectionpool:"GET /1.1/lists/list.json?screen_name=twitterAccount1 HTTP/1.1" 403 0
Any ideas ?