Bug 904296

Summary: [abrt] evolution-3.6.2-3.fc18: _XAllocID: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: drbean
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bugzilla, icucjamie, lucilanga, mbarnes, mcrha, tcfxfzoi
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c3d2dfb9f866364abe93c4145420160df25dee08
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 18:30:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description drbean 2013-01-26 01:35:41 UTC
Description of problem:
I backed up my home directories on an FTP server,   │         
                | before installing Fedora 18 (up from 15) and now    │         
                | evolution ignored them, configuring email anew.

I may have fixed that problem copying them by hand to .local/share/evolution/local/cur

The problem may actually have been caused by changing locale for the user concerned to Japanese.

Version-Release number of selected component:
evolution-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        evolution
core_backtrace: 
crash_function: _XAllocID
executable:     /usr/bin/evolution
kernel:         3.7.2-204.fc18.i686.PAE
remote_result:  829631
uid:            1001
var_log_messages: Jan 26 10:16:32 localhost abrt[3449]: Saved core dump of pid 3368 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2013-01-26-10:16:31-3368 (128757760 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 _XAllocID at xcb_io.c:528
 #6 XCreatePixmap at CrPixmap.c:56
 #7 _cairo_xlib_surface_create_similar at cairo-xlib-surface.c:311
 #8 _cairo_surface_create_similar_scratch at cairo-surface.c:470
 #9 _cairo_surface_create_similar_solid at cairo-surface.c:865
 #10 _cairo_default_context_push_group at cairo-default-context.c:164
 #11 INT_cairo_push_group_with_content at cairo.c:515
 #12 gdk_window_update_icon at gdkwindow-x11.c:3285
 #13 gdk_x11_window_set_icon_list at gdkwindow-x11.c:3415
 #15 gdk_window_set_icon_list at gdkwindow.c:10519

Potential duplicate: bug 746437

Comment 1 drbean 2013-01-26 01:35:45 UTC
Created attachment 687780 [details]
File: backtrace

Comment 2 drbean 2013-01-26 01:35:47 UTC
Created attachment 687781 [details]
File: cgroup

Comment 3 drbean 2013-01-26 01:35:49 UTC
Created attachment 687782 [details]
File: dso_list

Comment 4 drbean 2013-01-26 01:35:51 UTC
Created attachment 687783 [details]
File: environ

Comment 5 drbean 2013-01-26 01:35:53 UTC
Created attachment 687784 [details]
File: limits

Comment 6 drbean 2013-01-26 01:35:57 UTC
Created attachment 687785 [details]
File: maps

Comment 7 drbean 2013-01-26 01:35:59 UTC
Created attachment 687786 [details]
File: open_fds

Comment 8 drbean 2013-01-26 01:36:01 UTC
Created attachment 687787 [details]
File: proc_pid_status

Comment 9 Milan Crha 2013-01-28 09:37:26 UTC
Thanks for a bug report. The backtrace shows a crash during UI drawing, nothing much directly related to evolution itself. There was filled a similar bug report quite long time ago, with no resolution upstream. Based on the backtrace, I doubt it is anyhow related to update issue, which doesn't mean it can be related, like some kind of memory corruption. I guess we can deal with this within bug #896725, which is about restore/update, or do you see constant crashes when using the Japanese locale?

Comment 10 jamie c 2013-02-03 09:48:38 UTC
opening evolution, at bottom of screen it showed "saving user state" many times, but just froze.

backtrace_rating: 4
Package: evolution-3.6.3-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 11 impvan 2013-04-15 19:18:59 UTC
One of the accounts which Evolution checks, was unavailable.  Clicking 'Cancel' brought up the cancelling dialog, but program hanged, was still cancelling an hour later. Unable to kill with the window with the Close button, had to use terminal to find and kill the process.

backtrace_rating: 4
cmdline:        evolution
core_backtrace: 
crash_function: _XAllocID
executable:     /usr/bin/evolution
kernel:         3.8.6-203.fc18.i686
package:        evolution-3.6.4-3.fc18
reason:         Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
uid:            1000
ureports_counter: 1
xsession_errors: (evolution-alarm-notify:1695): e-data-server-ui-WARNING **: Keyring key is unusable: no user or host name

Comment 12 Fedora End Of Life 2013-12-21 10:50:14 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 13 Fedora End Of Life 2014-02-05 18:30:30 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.

Comment 14 drbean 2014-10-20 13:06:39 UTC
OK.