Bug 667543 - [abrt] evolution-2.32.1-1.fc14: g_object_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: g_object_unref: Process /usr/bin/evolution wa...
Keywords:
Status: CLOSED DUPLICATE of bug 676837
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e0788261023405fd344a609cb67...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-05 22:30 UTC by Sergio Basto
Modified: 2011-02-28 08:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-28 08:04:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (37.37 KB, text/plain)
2011-01-05 22:30 UTC, Sergio Basto
no flags Details

Description Sergio Basto 2011-01-05 22:30:34 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/evolution
component: evolution
crash_function: g_object_unref
executable: /usr/bin/evolution
kernel: 2.6.35.10-74.sb.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1294265888
uid: 500

How to reproduce
-----
1. open evolution , with 2 imaps accounts 
2. close normally evolution, after a while, as you do usually .
3. everytime I got this pseudo crash. (yeah after closing evolution) 
4. I don't know if it is an abtr problem which find crash every where when we close things .

Comment 1 Sergio Basto 2011-01-05 22:30:37 UTC
Created attachment 471956 [details]
File: backtrace

Comment 2 Milan Crha 2011-01-06 12:34:35 UTC
Thanks for a bug report. The crash is pretty strange and to be honest I do not understand it much. Could you run evolution under valgrind (I know, it's very slow when doing so) and attach here its output, to see whether it'll spot anything, please? You can get a valgrind log when you'll run this command on a console:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.txt

If you are able to reproduce this also when in offline, then even better,
use --offline at the end of the above command.

Thread 1 (Thread 22826):
#0  0x0000003a56e0f190 in g_object_unref (_object=<value optimized out>) at gobject.c:2629
#1  0x0000003a52e379b1 in exit () from /lib64/libc.so.6
#2  0x0000003a52e1ee84 in __libc_start_main (main=0x4021a0 <main>, argc=1, ubp_av=0x7fffa40593d8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffa40593c8) at libc-start.c:258
#3  0x0000000000401e69 in _start ()

Comment 3 sandijs.aploks 2011-02-11 10:20:17 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I upgraded kernel, and after the reboot, I closed Evolution application, and then the core dumped.

Comment 4 Artem 2011-02-11 15:46:50 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.start programm
2.syncronization mail start
3.after sync read new message
4.closed application

Comment 5 Frank Hahn 2011-02-11 16:53:26 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Everything worked OK then saw the bug report.
2.
3.

Comment 6 Derek Stanley 2011-02-13 16:00:18 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Everytime I close Evolution (clicking on the "x" in the upper right corner of the window) the program crashes.


Comment
-----
I just read my mail, deleted the junk then closed by clicking the X.

Comment 7 admin 2011-02-15 06:41:52 UTC
Package: evolution-2.32.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.open evolution
2. click e-mail address in to browser
3.

Comment 8 Sergio Basto 2011-02-26 09:03:40 UTC
Hi, latest update of qtcurve-gtk2 mention on bug
https://bugzilla.redhat.com/show_bug.cgi?id=676837

solves this bug either

Comment 9 Milan Crha 2011-02-28 08:04:13 UTC
Great, thanks, thus I'm marking this as a duplicate of it.

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


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