Bug 971681

Summary: Empathy Preferences won't open
Product: [Fedora] Fedora Reporter: apollo21b
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: atigro, bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 15:29:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description apollo21b 2013-06-07 06:50:27 UTC
Description of problem:
Clicking on "Preferences" in Empathy menu just closes the contact list and does nothing.

Version-Release number of selected component (if applicable):
empathy-3.8.3-1.fc19 (64-bit)

How reproducible:
Every time

Steps to Reproduce:
1. Open Empathy
2. Click Empathy -> Preferences


Additional info:

I just installed F19 beta and did all the updates with "sudo yum update", which appeared to work fine. I set up accounts with Facebook, Google, and AIM.

On Empathy open I get:
Jun  7 02:28:54 fedora /etc/gdm/Xsession[1179]: (empathy:2652): folks-WARNING **: backend-store.vala:405: Error preparing Backend 'ofono': GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files

On clicking Empathy -> Preferences:
Jun  7 02:28:58 fedora /etc/gdm/Xsession[1179]: (empathy:2652): GLib-CRITICAL **: g_bytes_get_data: assertion `bytes != NULL' failed
Jun  7 02:28:58 fedora /etc/gdm/Xsession[1179]: (empathy:2652): GLib-CRITICAL **: g_string_prepend: assertion `val != NULL' failed
...
Jun  7 02:28:58 fedora /etc/gdm/Xsession[1179]: (empathy:2652): GLib-CRITICAL **: g_string_prepend: assertion `val != NULL' failed
Jun  7 02:28:58 fedora /etc/gdm/Xsession[1179]: empathy: symbol lookup error: /lib64/libwebkitgtk-3.0.so.0: undefined symbol: hb_icu_script_to_script

Comment 1 apollo21b 2013-06-07 19:42:14 UTC
So I kind of got rid of Fedora already. I'm not that experienced with Linux and decided I didn't want bleeding edge + beta on top of that. Sorry for the trouble. Feel free to delete this bug report or whatever, but I won't be able to check anything to help solve it.

Comment 2 Fedora End Of Life 2015-01-09 18:21:15 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 3 Fedora End Of Life 2015-02-17 15:29:28 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.