Bug 797101 - unable to connect to any protocol on fresh install of f16
Summary: unable to connect to any protocol on fresh install of f16
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL: http://ask.fedoraproject.org/question...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 09:33 UTC by Chris Ward
Modified: 2013-02-13 10:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 10:09:29 UTC
Type: ---


Attachments (Terms of Use)

Description Chris Ward 2012-02-24 09:33:14 UTC
Description of problem:
I installed f16 recently... but i'm unable to get empathy up and running.

I did... in fact, copy over some .config and .local setting from my previous system (also running f16) so maybe i have some stale files mucking things up.

I installed empathy-3.2.2-1.fc16.x8664 and telepathy-idle-0.1.10-1.fc16.x8664.

When i launch empathy, i see the Account Assistant screen. I choose 'No, i want a new account'

But the only option i have available in 'what kind of chat account do you want' is 'jabber'. The selection box shows no other options.

When i set up my jabber account to test anyway, i get 'failed to connect' network error.'

Debug log can be found here (live for one month): 

http://pastebin.com/G57eX5YT

Comment 1 Chris Ward 2012-02-24 09:35:52 UTC
If someone could just tell me how to really force a fresh install of empathy; ie, clear out all previous config files and so forth, to see if perhaps it's not one of my stale configs, i'd give that a shot.

I've tried turning off firewall and selinux to be sure it's not one of those; didn't help.

Comment 2 Fedora End Of Life 2013-01-16 11:03:35 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 10:09:31 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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