Bug 1279115 - Empathy will not connect to google accounts after resuming from suspend; requires new session
Empathy will not connect to google accounts after resuming from suspend; requ...
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: empathy (Show other bugs)
23
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-07 19:08 EST by Dimitris
Modified: 2016-07-23 21:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-23 21:59:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dimitris 2015-11-07 19:08:17 EST
Description of problem:

After resuming from suspend, and the network reconnects, empathy will fail to reconnect to Google accounts.  Requires logging out and back it to connect again.

Version-Release number of selected component (if applicable):

3.12.11-1.fc23

How reproducible:

Almost every time

Steps to Reproduce:
1. Empathy connected to Google IM accounts (from gnome-online-accounts, so OAuth).
2. Suspend laptop, resume after some time.
3. Network connects but empathy doesn't: both accounts show "authentication error".
4. Attempting to reconnect them from the empathy contact list window by clicking on the "Reconnect" button leads to the same message.
5. Logging out and then back in fixes the problem.

Actual results:

Regression: Need logout/login to get empathy to work again

Expected results:

Return to previous behavior where empathy successfully reconnected upon resume.

Additional info:
Comment 1 Dimitris 2016-07-23 21:59:27 EDT
Haven't seen this in a while, both before and after upgrading to F24.

Note You need to log in before you can comment on or make changes to this bug.