Bug 918785 - [abrt] evolution-3.4.4-2.fc17: gtk_style_context_get_border: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-3.4.4-2.fc17: gtk_style_context_get_border: Process /usr/bin...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:14e776995a073b5fb79a383b9e1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-06 20:58 UTC by J. William Cupp
Modified: 2013-03-07 08:30 UTC (History)
3 users (show)

Fixed In Version: evolution-3.7.92
Clone Of:
Environment:
Last Closed: 2013-03-07 08:30:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: environ (1.78 KB, text/plain)
2013-03-06 20:58 UTC, J. William Cupp 		no flags Details
File: limits (1.29 KB, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: backtrace (75.90 KB, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: cgroup (135 bytes, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: smolt_data (3.41 KB, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: executable (18 bytes, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: maps (85.17 KB, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: build_ids (6.93 KB, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: proc_pid_status (921 bytes, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
File: open_fds (296 bytes, text/plain)
2013-03-06 20:59 UTC, J. William Cupp 		no flags Details
View All

Description J. William Cupp 2013-03-06 20:58:54 UTC 
Version-Release number of selected component:
evolution-3.4.4-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        evolution --component=calendar
crash_function: gtk_style_context_get_border
kernel:         3.7.6-102.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 gtk_style_context_get_border at gtkstylecontext.c:3625
: #1 gtk_button_get_props at gtkbutton.c:1592
: #2 gtk_button_get_size at gtkbutton.c:2120
: #3 compute_size_for_orientation at gtksizerequest.c:382
: #4 gtk_widget_get_preferred_size at gtksizerequest.c:702
: #5 gtk_button_box_child_requisition at gtkbbox.c:492
: #6 gtk_button_box_size_request at gtkbbox.c:591
: #7 gtk_button_box_get_preferred_height at gtkbbox.c:671
: #8 compute_size_for_orientation at gtksizerequest.c:382
: #9 gtk_widget_get_preferred_height_for_width at gtksizerequest.c:647
Comment 1 J. William Cupp 2013-03-06 20:58:58 UTC 
Created attachment 706251 [details]
File: environ
Comment 2 J. William Cupp 2013-03-06 20:59:00 UTC 
Created attachment 706252 [details]
File: limits
Comment 3 J. William Cupp 2013-03-06 20:59:02 UTC 
Created attachment 706253 [details]
File: backtrace
Comment 4 J. William Cupp 2013-03-06 20:59:04 UTC 
Created attachment 706254 [details]
File: cgroup
Comment 5 J. William Cupp 2013-03-06 20:59:07 UTC 
Created attachment 706255 [details]
File: smolt_data
Comment 6 J. William Cupp 2013-03-06 20:59:09 UTC 
Created attachment 706256 [details]
File: executable
Comment 7 J. William Cupp 2013-03-06 20:59:11 UTC 
Created attachment 706257 [details]
File: maps
Comment 8 J. William Cupp 2013-03-06 20:59:13 UTC 
Created attachment 706258 [details]
File: build_ids
Comment 9 J. William Cupp 2013-03-06 20:59:15 UTC 
Created attachment 706259 [details]
File: proc_pid_status
Comment 10 J. William Cupp 2013-03-06 20:59:17 UTC 
Created attachment 706260 [details]
File: open_fds
Comment 11 Milan Crha 2013-03-07 08:30:39 UTC 
Thanks for a bug report. Even this crashed in the main thread, I see the Thread 2 calls gtk functions below e_client_emit_backend_died(), which it should not do. The current development version, to be 3.8.x and part of Fedore 19, has this done differently, thus I guess it may not happen there.
Note You need to log in before you can comment on or make changes to this bug.