Home » Trisquel » Issues
Submitted by jturner on Tue, 09/20/2011 - 02:05

Gwibber fails to add a new account

Project:Trisquel
Component:Programs
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed
Description

I am unable to add my identi.ca account to Gwibber in Trisquel 5.0. It says it's authorized but never finishes adding the account.

Also, 5.0 needs to be added to the Version drop down for creating issues.

ivaylo:
Tue, 09/20/2011 - 10:14
Status:active» wrong

Identi.ca was down, because it was upgraded to the latest version of Statusnet, the software that it runs on.

jturner:
Tue, 09/20/2011 - 14:58
Status:wrong» active

Identi.ca has been back up for awhile now and I still can't add my account. I get the connection screen and after I enter my credentials and select Allow the account is never added. It says "Identi.ca authorized" but the account is never added to the account list and Close is the only button available.

ivaylo:
Tue, 09/20/2011 - 15:27

Authorization works with already added account. I just tested it without accounts added, by removing my configurations. It works. The version I have is 3.0.0.1-0ubuntu3 provided by dagda-updates. I still think there is nothing wrong with Gwibber. I'm not changing the bug back to wrong until somebody else backs me up.

jturner:
Tue, 09/20/2011 - 16:16

I appreciate you testing this. I've ran rm -rf .config/gwibber .gconf/apps/gwibber .cache/gwibber and am still unable to add an account. After the failed attempt if I log into Identi.ca and look at the connections for my account I see this entry for what should be gwibber.

Unknown application - Approved about 2 minutes ago - "read-write" access.
An anonymous application

I should note, I upgraded to Trisquel 5.0 from 4.5.1 if that makes any difference.

jturner:
Tue, 09/20/2011 - 16:26

When I ran gwibber with debug on gwibber -d it was able to create the account.

ivaylo:
Wed, 09/21/2011 - 11:30
Version:»

There is now version 5.0 available for issues. Changing the versions to 5.0, because in the first comment it is said this bug is against 5.0.

jturner:
Fri, 09/23/2011 - 16:05
Status:active» closed

A workaround was found, so I guess this isn't an issue anymore?