Red Hat Bugzilla – Bug 462686
Crash probably in evolution-data-server?
Last modified: 2018-04-11 04:01:59 EDT
Description of problem:
When starting pidgin, I couldn't get it start, even though I killed pidgin repeatedly. THe only thing I got was the attached backtrace. From looking at the backtrace, it looked to me like e-d-s could be involved, so I killedevo and the result was that pidgin started smoothly. Unfortunately, no backtrace of e-d-s.
Version-Release number of selected component (if applicable):
Created attachment 317053 [details]
If you pass to eds some crap, then it will crash, yeah, that's possible:
#8 0x00007ffff0be4275 in gevo_load_addressbook (uri=0x9c11f4 "\001",
book=0x80, error=0x1) at gevo-util.c:142
#9 0x00007ffff0be3734 in load_timeout (data=0x9b0bd0) at gevolution.c:304
See the uri value; the 'book' and 'error' are suspicious too. It's out of evo scope, I'm afraid, because the source file comes from the other application.
I agree. Looks like the bad GError is what did it in, since that's the only thing that gets passed to e_book_new_system_addressbook(). This is an issue with Pidgin's EDS integration.
Changing component, though it's not clear this is reproducible for the Pidgin folks.
All the calls to gevo_load_addressbook in pidgin pass an explicit NULL for the error argument. Bad stacktrace, methinks.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Matej, is this still an issue with F-10 updates?
I haven't dared to use EDS-piding link since it destroyed my EDS contacts database.
Closing as INSUFFICIENT_DATA.