ungranted online accounts cause Chrome to pop-up blank tabs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Online Accounts: Account plugins |
High
|
Alberto Mardegan | ||
Bug Description
Ubuntu 13.04
Over the month I've been annoyed by Chrome popping up blank tabs, seemingly randomly. At first I blamed Unity and even discussed it with the team, but an answer to my question on AskUbuntu.com gave me a clue. When I have accounts that need to be granted permission, I get random chrome tabs popping up. Once all accounts are re-granted access, I no longer have the problem. The issue occurs when I use the dash and at other (seemingly random) times. I cannot repro this in the 5 minutes I tried by disabling accounts, they need to be ungranted or expired (sorry I don't know the right term). I can repro by rebooting the system. I have the following online accounts enabled:
Twitter
Google
Fitbit
SIP
This bug is pretty annoying and I'm willing to help debug and/or test code. I don't know exactly what packages this is coming from, but I can get version into on any you need.
| Alberto Mardegan (mardy) wrote : | #1 |
| Changed in account-plugins: | |
| status: | New → Incomplete |
| importance: | Undecided → High |
| assignee: | nobody → Alberto Mardegan (mardy) |
| Matt Fischer (mfisch) wrote : | #2 |
Is there an easy way to get the accounts to de-auth (other than time)? I power cycled because that seemed to trigger it before and no luck.
| Alberto Mardegan (mardy) wrote : | #3 |
Here's how to unauthenticate an account: first, find out the ID of the account, using the command
account-console list
Then, find out the ID of the credentials record associated with the account:
account-console show <id-of-account>
(look for the CredentialsId field). Then, remove the file
~/.cache/
and last, open seahorse, open the "Login" keyring and delete the key named "Ubuntu Web Account: id <creds-id>-3".
Hi Matthew, thanks for reporting this. This behaviour is indeed caused by OnlineAccounts, though it's of course not the expected behaviour. :-)
When you can reproduce the bug again, can you please issuing the following commands from a terminal:
killall signon-ui
export SSOUI_DAEMON_
export SSOUI_LOGGING_
signon-ui > signonui.log
Then type something in the dash (in order to trigger the bug) and then attach the signonui.log file to this bug report? Please mangle any passwords or tokens that you see in the log.