Bug 644913 - [abrt] empathy-2.32.0.1-2.fc14: magazine_chain_pop_head: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Summary: [abrt] empathy-2.32.0.1-2.fc14: magazine_chain_pop_head: Process /usr/bin/emp...
Keywords:
Status: CLOSED DUPLICATE of bug 641532
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b8dec07b80f5fed0613f6360e45...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-20 15:37 UTC by drade
Modified: 2010-11-10 16:49 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-10 16:49:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (42.67 KB, text/plain)
2010-10-20 15:37 UTC, drade
no flags Details

Description drade 2010-10-20 15:37:18 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: empathy
component: empathy
crash_function: magazine_chain_pop_head
executable: /usr/bin/empathy
kernel: 2.6.35.6-45.fc14.i686
package: empathy-2.32.0.1-2.fc14
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1287673741
uid: 500

comment
-----
Fedora 14 i686
Linux Kernel 2.6.35.6
gnome 2.32

When running Empathy and added the msn protocol, this crash happens. Also msn keeps saying network error. 

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

Comment 1 drade 2010-10-20 15:37:20 UTC
Created attachment 454597 [details]
File: backtrace

Comment 2 Yann Droneaud 2010-10-29 13:32:02 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Creating a jabber account. Deleting, recreating, deleting, recreating.

Comment 3 Elcrapocrew 2010-11-04 08:05:58 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I was setting up my empathy to connect to our open fire chat server here at work and crash it went
2.
3.

Comment 4 jbox_ny 2010-11-05 07:04:57 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I was adding my gmail account info and it all went through the first time
2. but I didn't see any of my contacts load up so as I was logged in, I retyped my password in account info
3. That's when Empathy crashed.

Comment 5 john r davis jr 2010-11-05 10:20:03 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.opened empathy
2.created new yahoo account
3.right-clicked n a user and it crashed

Comment 6 Renich Bon Ciric 2010-11-05 18:20:59 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


Comment
-----
I dunno... it just happened...

Comment 7 Renich Bon Ciric 2010-11-05 18:51:54 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


Comment
-----
I dunno... it just happened...

Comment 8 David Strohmayer 2010-11-06 18:28:40 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Changed the RESSOURCE of my jabber account
2. Accepted untructed connection to my jabber server
3.

Comment 9 Brian Pepple 2010-11-06 18:40:53 UTC
(In reply to comment #8)
> -----
> 1. Changed the RESSOURCE of my jabber account
> 2. Accepted untructed connection to my jabber server
> 3.

That crash is most likely due to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=31412

Comment 10 Dick Thomas 2010-11-08 19:59:42 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I was not using the app at the time and hadn't done any thing for a while with it
it just randomly crashed

Comment 11 Sergey Gerasimov 2010-11-09 08:37:47 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. changing connection setting to ssl and reconnecting

Comment 12 Damien Grassart 2010-11-09 14:15:34 UTC
Package: empathy-2.32.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Went to manage accounts.
2. Selected a Google Talk account
3. Expanded the advanced section and enabled "Ignore SSL certificate errors"
4. Empathy crashed.

Comment
-----
I wanted to enable that since I get an error each time I connect, due to my login domain being different from the talk.google.com server domain.

Comment 13 Brian Pepple 2010-11-09 14:40:26 UTC
(In reply to comment #12)
> How to reproduce
> -----
> 1. Went to manage accounts.
> 2. Selected a Google Talk account
> 3. Expanded the advanced section and enabled "Ignore SSL certificate errors"
> 4. Empathy crashed.
> 
> Comment
> -----
> I wanted to enable that since I get an error each time I connect, due to my
> login domain being different from the talk.google.com server domain.

Damien, there is a Empathy update in bodhi that fixes a ca-cert import bug, that should fix the ssl cert error for googletalk.

To install it run:
yum --enablerepo=updates-testing update empathy

And if you could leave karma afterwards it would be appreciated.

Comment 14 Damien Grassart 2010-11-10 16:27:36 UTC
Hi Brian, I updated empathy from updates-testing per your suggestion but Empathy still seems to crash if I enable "Ignore SSL certificate errors", hit apply, and then reconnect the account.

Comment 15 Brian Pepple 2010-11-10 16:33:28 UTC
(In reply to comment #14)
> Hi Brian, I updated empathy from updates-testing per your suggestion but
> Empathy still seems to crash if I enable "Ignore SSL certificate errors", hit
> apply, and then reconnect the account.

Is your account connected when you are enabling "Ignore SSL certificate errors" option? If not, please attach a backtrace. Thanks!

Comment 16 Brian Pepple 2010-11-10 16:49:51 UTC

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


Note You need to log in before you can comment on or make changes to this bug.