Bug 678164

Summary: [abrt] empathy-2.91.6.1-5.fc15: g_list_length: Process /usr/bin/empathy-accounts was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: abrt-bot, bdpepple, cfergeau, dlesage, mclasen, mschmidt, rlat, secris1, tla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:17c1e6bc14888479650289e9617ed1f0a9412cc9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-11 09:49:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jóhann B. Guðmundsson 2011-02-16 23:07:37 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 16134 bytes
cmdline: /usr/bin/empathy-accounts --if-needed
component: empathy
Attached file: coredump, 16814080 bytes
crash_function: g_list_length
executable: /usr/bin/empathy-accounts
kernel: 2.6.38-0.rc5.git0.1.fc15.x86_64
package: empathy-2.91.6.1-5.fc15
rating: 4
reason: Process /usr/bin/empathy-accounts was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297897610
uid: 500

How to reproduce
-----
1. Started Empathy
2.
3.

Comment 1 Jóhann B. Guðmundsson 2011-02-16 23:07:40 UTC
Created attachment 479233 [details]
File: backtrace

Comment 2 Jóhann B. Guðmundsson 2011-02-16 23:15:52 UTC
Note this was the first time I ran empathy and is reproducible by going into add account ( F4 )

Comment 3 Jóhann B. Guðmundsson 2011-02-17 00:02:50 UTC
Workaround found simply run /usr/bin/empathy-accounts and create the account(s) then start empathy

Comment 4 Michal Schmidt 2011-02-18 13:19:46 UTC
Package: empathy-2.91.6.1-5.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. run "empathy-accounts"
2. it crashes within a second

Comment
-----
Perfectly reproducible.

Comment 5 Michal Schmidt 2011-02-18 13:35:39 UTC
The crash is gone after uninstalling at-spi*.

Comment 6 Tim Lauridsen 2011-02-20 08:30:20 UTC
Package: empathy-2.91.6.1-5.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. Booted Fedora 15 Alpha TC2 + Updates
2. Start "Empathy" with no accounts setup
3. The account dialog crashes.

Comment 7 Tim Lauridsen 2011-02-20 08:45:39 UTC
Removing at-api* packages and the crash dont happen.

Comment 8 David Le Sage 2011-02-28 06:46:18 UTC
Package: empathy-2.91.6.1-5.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. Empathy crashes on launch.

Comment 9 Sean 2011-02-28 10:01:44 UTC
Package: empathy-2.91.6.1-5.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1.Went to the menu and clicked on empathy
2.When Empathy finished loading it started the add accout wizard
3.Add wizard crashed

Comment 10 Sean 2011-03-02 22:35:36 UTC
Package: empathy-2.91.6.1-5.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. started empathy
2. it auto started the account wizard 
3. empathy account wizard crashed

Comment 11 abrt-bot 2012-03-20 14:19:57 UTC
Backtrace analysis of bugs across components suggests the actual bug is in component gtk3 or at-spi2-atk instead of component empathy, reassigning to gtk3.

Bugs which were found to be similar to this bug: 
  evolution: bug #678446, bug #680698
  gnome-bluetooth: bug #678048
  gtk3: bug #677909

This comment is automatically generated.

Comment 12 abrt-bot 2012-03-20 14:20:12 UTC
*** Bug 678048 has been marked as a duplicate of this bug. ***

Comment 13 Christophe Fergeau 2013-03-11 09:49:55 UTC
This is the same backtrace as bug #677909

*** This bug has been marked as a duplicate of bug 677909 ***