Bug 487454

Summary:	empathy crash will adding New contact to contact list
Product:	[Fedora] Fedora	Reporter:	A S Alam <aalam>
Component:	empathy	Assignee:	Peter Gordon <peter>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	abhixecutor, bdpepple, desktop-bugs, mshao, peter
Target Milestone:	---	Keywords:	Desktop
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-11-09 20:41:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description A S Alam 2009-02-26 04:21:04 UTC

Description of problem:
Application crash while adding contact/buddy (yahoo) to contact list,

Version-Release number of selected component (if applicable):
empathy-2.24.1-1.fc10.x86_64

How reproducible:
Everytime during adding buddy

Steps to Reproduce:
1. login to Yahoo account to empathy (Alt+F2 emapthy and add yahoo account)
2. add some new contact while provide identifier/Alias
3.
  
Actual results:
application crash when Add button pressed

Expected results:
work normal and add contact to list

Additional info:
not tested with with our protocol

Comment 1 Abhinav 2009-04-09 05:29:28 UTC

i am also facing same problem ..
got this while running it from konsole


** (empathy:4779): CRITICAL **: dbus_g_connection_get_connection: assertion `gconnection' failed
process 4779: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5758.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

Comment 2 A S Alam 2009-05-27 06:59:38 UTC

working in rawhide with following package:
empathy-2.26.1-1

Comment 3 Brian Pepple 2009-11-09 20:41:37 UTC

Closing since this appears to be fixed.