Bug 1009303

Created attachment 799138 [details]
File: backtrace

Created attachment 799139 [details]
File: cgroup

Created attachment 799140 [details]
File: core_backtrace

Created attachment 799141 [details]
File: dso_list

Created attachment 799142 [details]
File: environ

Created attachment 799143 [details]
File: exploitable

Created attachment 799144 [details]
File: limits

Created attachment 799145 [details]
File: maps

Created attachment 799146 [details]
File: open_fds

Created attachment 799147 [details]
File: proc_pid_status

Created attachment 799148 [details]
File: var_log_messages

Adam, was this a one-time crash, or is it reproducible ?

And how was gnome-contacts started ?

It seems to happen each time I try to get information on an XMPP contact in Empathy.

After updating to GNOME 3.9.92 and running Empathy I hit https://bugzilla.redhat.com/show_bug.cgi?id=1010080 which abrt thinks is new. Right now I can't get Empathy to believe it's online to see if I still get this crash when trying to get info on a contact.

also happens if I do the same thing with a Facebook contact. Note, I haven't done GNOME Contacts' initial setup wizard yet: perhaps this bug happens when you try to get Information on a contact from Empathy before doing that?

Try open contact from activities.

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        gnome-contacts -i 79e32013dc66ac4218513ea0fd7866768f76f8fa
crash_function: contacts_app_selection_changed
executable:     /usr/bin/gnome-contacts
kernel:         3.11.3-301.fc20.x86_64
package:        gnome-contacts-3.10-1.fc20
reason:         Process /usr/bin/gnome-contacts was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

I wanted to show some information about one person from Empathy communicator, and then I saw the crash report. I have this link from GUI ABRT, I don't know how to add more information, because when GUI finds that bug was reported, it doesn't gave chance to add information to existing bug report.
Fedora 20 Alpha with Gnome 3.10 64 bit. Gnome-contacts-3.10-1.fc20

Description of problem:

I was using GNOME Search and journalctl going to use %100 CPU and crashed.Strange part is I was also opening Rhythmbox and journalctl also going to %100 but gnome-contacts also crashed again. 

Version-Release number of selected component:

Gnome-contacts-3.10.1-1.fc20.x86_64

I ran into this problem by selecting 'Information' from empathy contact context menu.
After launching gnome-contacts directly and selecting 'primary contact store' it no longer crashes when invoked from empathy.

gnome-contacts-3.10.1-1.fc20.x86_64

The same thing happened just here.

In the empathy chat window I selected Contact -> Information and gnome contacts had crashed.
After starting it manually and selecting primary contact store, no more crashes.

Version 3.10.1-1.fc20 also.

Another user experienced a similar problem:

1) start empathy
2) start conversation with someone
3) click on Contact->Information
4) crash

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        gnome-contacts -i 225757a955b3ae34f6e64f350ec1d7bfae7261e1
crash_function: contacts_app_selection_changed
executable:     /usr/bin/gnome-contacts
kernel:         3.12.7-300.fc20.x86_64
package:        gnome-contacts-3.10.1-1.fc20
reason:         gnome-contacts killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

i get the same Crash as the reporter above me

I can reproduce this on the liveUSB of F20, or in a freshly installed account:

1. Open Online Accounts.
2. Add an account with chat enabled.
3. Wait for contacts to load.
4. Go to gnome-shell and search for a contact, click such contact.

Expected:
5. gnome-contacts opens with such contact loaded.

Actual:
5. gnome-contacts crashes with this trace.

Fix:
Open gnome-contacts independently, and select a default addressbook source.
After doing this, the crash is gone.


Seems g-c doesn't know what to do if there's no default adddressbook source.

Occurs when try to open finded with "GNOME Search" contact.

Another user experienced a similar problem:

I have an owncloud account in my Gnome online accounts. The problem occured when I search for a contact via the gnome shell and then hit enter.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        gnome-contacts -i 23011fcb9ed13a2624cb4bc49ec2f14ba51e80e3
crash_function: contacts_app_selection_changed
executable:     /usr/bin/gnome-contacts
kernel:         3.14.4-200.fc20.x86_64
package:        gnome-contacts-3.10.1-1.fc20
reason:         gnome-contacts killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Crash when attempting to add an XMPP contact in Empathy.  I did not open gnome-contacts.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        gnome-contacts -i 9afe9707aad16e65a3bbb2cab0486d94dc497cf8
crash_function: contacts_app_selection_changed
executable:     /usr/bin/gnome-contacts
kernel:         3.14.7-200.fc20.x86_64
package:        gnome-contacts-3.10.1-1.fc20
reason:         gnome-contacts killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

I faced this as well when trying to view information about an XMPP contact.

[nazgul@localhost ~]$ yum info gnome-contacts
Geladene Plugins: langpacks
Installierte Pakete
Name       : gnome-contacts
Architektur : x86_64
Version    : 3.10.1
Ausgabe    : 1.fc20

Also reproducible for me.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.