Online Accounts doesn't show Twitter OAuth page

Bug #1073788 reported by Sah Lee
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Online Accounts: GNOME Control Center
Fix Released
High
Alberto Mardegan
gnome-control-center-signon (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

To reproduce:
System Settings -> Online Accounts -> Add account... -> Twitter

Expected:
Twitter OAuth page shown, asking for my login and permission

Actually:
Nothing shown, but a gray bar saying "Please authorize Ubuntu to access your Twitter account".
Even the black spinner doesn't show up.

Additional info:
I'm behind a proxy.
I can open Twitter with my browser.
I can add other accounts like Facebook and Google.
I see the same problem when adding Sina account.

Please let me know how and which if I could provide any log.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu19
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Thu Nov 1 10:51:47 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2012-08-12 (81 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to quantal on 2012-10-23 (8 days ago)
XsessionErrors: (gtk-window-decorator:2724): GLib-CRITICAL **: g_hash_table_remove_internal: assertion `hash_table != NULL' failed
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu4
 deja-dup 24.0-0ubuntu1
 gnome-control-center-signon 0.0.18-0ubuntu1
 indicator-datetime 12.10.2-0ubuntu3

Revision history for this message
Sah Lee (leesah) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
affects: gnome-control-center (Ubuntu) → gnome-control-center-signon (Ubuntu)
Revision history for this message
Alberto Mardegan (mardy) wrote :

Hi Sah, and thanks for reporting this bug!
Unfortunately, we know that Sina is not working properly. However, Twitter should be working fine. If you are confident enough to use the Terminal, could you please open it and try the following, while the Online Accounts panel is *closed*:

  killall signon-ui
  export SSOUI_LOGGING_LEVEL=2
  signon-ui

then try to reproduce the bug again (attempt to create a Twitter account) and attach the signon-ui output to this bug report. That will probably provide us enough information to understand what is going wrong.

Changed in gnome-control-center-signon:
status: New → Incomplete
importance: Undecided → High
assignee: nobody → Alberto Mardegan (mardy)
Revision history for this message
Sah Lee (leesah) wrote :

Hi Alberto,

It seems signon-ui won't open any window for me. Any clue?

Revision history for this message
Alberto Mardegan (mardy) wrote :

Yes, that's normal, it shouldn't open any window when you launch it. But when you start creating the twitter account, you should see some messages appearing in the terminal.

Revision history for this message
Sah Lee (leesah) wrote :

OK. I thought it was a shortcut to open the Online Accounts window. :-D

I tried just now. Problem reproduced. But no output in terminal.
And then I tried setting the log level to 3, still no luck.
Every time I tried I did after a reboot, so that the red gear icon on the top-right corner turns back to white again.

Revision history for this message
Walter Ribeiro (wribeirojr) wrote :

Same thing here, no messages showed in the terminal.

Revision history for this message
Alberto Mardegan (mardy) wrote :

OK, so it seems that something is broken before the request even gets to signon-ui.
Could you please do the following then:

  sudo gedit /etc/signond.conf

Then uncomment (remove the initial ";") the line with "LoggingLevel", and set the level to 2. Then save the file and quit gedit.
Then,

  killall signond

And try to create a twitter account again. It should still fail, but at least this time there will be some information logged into the /var/log/syslog file. It would be great if you could copy the last part of it, from the line "Signond SUCCESSFULLY initialized" on, and paste it here (make sure that no passwords are logged; they shouldn't be, but please double check and, if you find them, just overwrite them with some random text).

Revision history for this message
Sah Lee (leesah) wrote :

Sorry. Should've used this uploading function.

Revision history for this message
Alberto Mardegan (mardy) wrote :

Thanks Sah! It seems that there is a network error...
Can you please tell me what happens when you try to load these URLs in your browser?

https://api.twitter.com/oauth/request_token
https://api.twitter.com/oauth/access_token
https://api.twitter.com/oauth/authorize

They will probably not return any useful content, but what I'm interested in knowing is whether you get some error or whether you are redirected to other pages.
Another question: are you behind a proxy?

Revision history for this message
Sah Lee (leesah) wrote :

request_token gives 401 Unauthorized and a message "Failed to validate oauth signature and token".
access_token also gives 401 Unauthorized and no additional message.
authorize gives 403 Forbidden and a Twitter style web page saying there's a lack of some token.

Yes, I am behind a proxy. But I didn't meet any problem adding other accounts like Facebook or Google.

Revision history for this message
Walter Ribeiro (wribeirojr) wrote :

Response for the 3 URLs:

1: "There is no request token for this page. It is the special key that we need to receive from app that asked to use your account in Twitter. Please, return to site or app that sent you here and try again; probably it's just an error." (text in Portuguese, my translation)
2: blank page, no response.
3: "Failed to validate oauth signature and token"

Revision history for this message
Walter Ribeiro (wribeirojr) wrote :

For me this issue is solved, in Ubuntu 13.04

Revision history for this message
faical117 (faical117) wrote :

same issue here UBUNTU 13.04

service.cpp 179 queryDialog Got request: QMap(("Caption", QVariant(QString, "Facebook") ) ( "ClientData" , QVariant(QDBusArgument, ) ) ( "FinalUrl" , QVariant(QString, "https://www.facebook.com/connect/login_success.html") ) ( "Identity" , QVariant(uint, 4) ) ( "Mechanism" , QVariant(QString, "user_agent") ) ( "Method" , QVariant(QString, "oauth2") ) ( "OpenUrl" , QVariant(QString, "https://www.facebook.com//dialog/oauth?client_id=302061903208115&redirect_uri=https://www.facebook.com/connect/login_success.html&display=popup&type=user_agent&scope=publish_stream,read_stream,status_update,user_photos,friends_photos,xmpp_login") ) ( "StoredIdentity" , QVariant(bool, true) ) ( "UserName" , QVariant(QString, "") ) ( "requestId" , QVariant(QString, "/com/google/code/AccountsSSO/SingleSignOn/AuthSession_0") ) )
service.cpp 98 runQueue Head: SignOnUi::BrowserRequest(0xa84580)
browser-request.cpp 117 acceptNavigationRequest QUrl( "https://www.facebook.com//dialog/oauth?client_id=302061903208115&redirect_uri=https://www.facebook.com/connect/login_success.html&display=popup&type=user_agent&scope=publish_stream,read_stream,status_update,user_photos,friends_photos,xmpp_login" )
browser-request.cpp 526 buildDialog Dialog was built
request.cpp 136 setWidget Requesting widget embedding
Object::connect: No such slot SignOnUi::RequestPrivate::onEmbedError()
Object::connect: (sender name: 'request-widget')
browser-request.cpp 305 onUrlChanged Url changed: QUrl( "https://www.facebook.com//dialog/oauth?client_id=302061903208115&redirect_uri=https://www.facebook.com/connect/login_success.html&display=popup&type=user_agent&scope=publish_stream,read_stream,status_update,user_photos,friends_photos,xmpp_login" )
browser-request.cpp 324 onLoadFinished Load finished true
browser-request.cpp 693 initializeField Couldn't find element: "input[name=email]"
browser-request.cpp 693 initializeField Couldn't find element: "input[name=pass]"
browser-request.cpp 117 acceptNavigationRequest QUrl( "http://www.facebook.com/login.php?skip_api_login=1&api_key=302061903208115&signed_next=1&next=https://www.facebook.com/dialog/oauth?redirect_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html&display=popup&scope=publish_stream%2Cread_stream%2Cstatus_update%2Cuser_photos%2Cfriends_photos%2Cxmpp_login&type=user_agent&client_id=302061903208115&ret=login&cancel_uri=https://www.facebook.com/connect/login_success.html?error=access_denied&error_code=200&error_description=Permissions+error&error_reason=user_denied#_=_&display=popup" )
browser-request.cpp 156 urlIsBlocked Scheme not allowed: "http"

(process:4849): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed

Revision history for this message
Sah Lee (leesah) wrote :

Solved in my Raring too.

Revision history for this message
Alberto Mardegan (mardy) wrote :

This was most likely proxy support not working properly. Closing the bug report.

Changed in gnome-control-center-signon:
status: Incomplete → Fix Released
Changed in gnome-control-center-signon (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.