Bug 700588 - Can't connect to gtalk; RequestConnection failed: Failed to execute program /usr/libexec/telepathy-gabble: Success
Summary: Can't connect to gtalk; RequestConnection failed: Failed to execute program /...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-28 18:07 UTC by Josef
Modified: 2015-02-18 13:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 13:33:11 UTC
Type: ---


Attachments (Terms of Use)
output from empathy-debugger (5.22 KB, text/x-log)
2011-04-28 18:07 UTC, Josef
no flags Details

Description Josef 2011-04-28 18:07:36 UTC
Created attachment 495625 [details]
output from empathy-debugger

Did an update of f15/rawhide a couple of hours ago and now Empathy can't connect to my google talk-account.

version is 0.12-1.f15.

attaching the log from empathy-debugger.

Comment 1 Brian Pepple 2011-04-28 18:13:00 UTC
What version of selinux-policy do you have installed?

Comment 2 Josef 2011-04-28 18:59:38 UTC
it's 3.9.16-16.fc15.

the telepathy-butterfly is working though.

Comment 3 Brian Pepple 2011-04-28 19:06:05 UTC
(In reply to comment #2)
> it's 3.9.16-16.fc15.

There was a bad selinux-policy that was pushed to updates-testing (which you have installed), that broke telepathy. Please update to the latest version of selinux-policy that is in bodhi (or wait for it to be pushed to updates-testing in the next day or so). That should fix your problem.

Comment 4 Fedora End Of Life 2013-04-03 19:14:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Fedora End Of Life 2015-01-09 21:48:56 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 6 Fedora End Of Life 2015-02-18 13:33:11 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.