Bug 906384

Summary: [abrt] evolution-3.6.3-2.fc18: _gdk_device_xi2_reset_scroll_valuators: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ludek Finstrle <luf>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5497866ffe955ba8c43abb32b38cd8034b5a48bb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-01 08:06:40 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: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ludek Finstrle 2013-01-31 14:48:44 UTC
Description of problem:
I tried to remove the calendar entry using MAPI calendar on exchange.
The failure froze whole gnome-shell which I had to kill.

I'm using kerberos authentication againist AD.

Version-Release number of selected component:
evolution-3.6.3-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/evolution
crash_function: _gdk_device_xi2_reset_scroll_valuators
executable:     /usr/bin/evolution
kernel:         3.7.4-204.fc18.x86_64
remote_result:  804743
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _gdk_device_xi2_reset_scroll_valuators at gdkdevice-xi2.c:853
 #1 gdk_x11_device_manager_xi2_translate_event at gdkdevicemanager-xi2.c:1551
 #3 _gdk_x11_event_translator_translate at gdkeventtranslator.c:51
 #4 gdk_event_source_translate_event at gdkeventsource.c:227
 #5 _gdk_x11_display_queue_events at gdkeventsource.c:332
 #6 gdk_display_get_event at gdkdisplay.c:310
 #12 gtk_dialog_run at gtkdialog.c:1110
 #13 e_alert_run_dialog at e-alert-dialog.c:343
 #14 e_alert_run_dialog_for_args at e-alert-dialog.c:364
 #15 delete_component_dialog at delete-comp.c:158

Comment 1 Ludek Finstrle 2013-01-31 14:48:47 UTC
Created attachment 690967 [details]
File: backtrace

Comment 2 Ludek Finstrle 2013-01-31 14:48:52 UTC
Created attachment 690968 [details]
File: build_ids

Comment 3 Ludek Finstrle 2013-01-31 14:48:54 UTC
Created attachment 690969 [details]
File: cgroup

Comment 4 Ludek Finstrle 2013-01-31 14:48:57 UTC
Created attachment 690970 [details]
File: core_backtrace

Comment 5 Ludek Finstrle 2013-01-31 14:48:59 UTC
Created attachment 690971 [details]
File: dso_list

Comment 6 Ludek Finstrle 2013-01-31 14:49:01 UTC
Created attachment 690972 [details]
File: environ

Comment 7 Ludek Finstrle 2013-01-31 14:49:05 UTC
Created attachment 690973 [details]
File: limits

Comment 8 Ludek Finstrle 2013-01-31 14:49:07 UTC
Created attachment 690974 [details]
File: maps

Comment 9 Ludek Finstrle 2013-01-31 14:49:09 UTC
Created attachment 690975 [details]
File: open_fds

Comment 10 Ludek Finstrle 2013-01-31 14:49:11 UTC
Created attachment 690976 [details]
File: proc_pid_status

Comment 11 Ludek Finstrle 2013-01-31 14:49:13 UTC
Created attachment 690977 [details]
File: var_log_messages

Comment 12 Ludek Finstrle 2013-01-31 14:53:05 UTC
I forgot to mention I tried remove one occurance from reoccurance meeting.

Comment 13 Milan Crha 2013-02-01 08:06:40 UTC
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=673822

Comment 14 Ludek Finstrle 2013-02-02 08:45:29 UTC
I don't understand the Fedora policy but I don't want to create account in every bugzilla ;) And I don't want to compile several packages without knowledge if the patches will go into next update.

I read the upstream bug and there is suggestion for patch from debian. Can anybody from Fedora team (I understand that the bug isn't in evolution) use the patch and compile new package? I have no problem to use updates-testing repository to test it.

Comment 15 Milan Crha 2013-02-04 08:17:20 UTC
Right, I understand it and agree with you, that's why I wrote 'If possible'.

I cannot speak for gtk3 developers/maintainers, I can only create a scratch build with the the upstream patches included, but whether they'll use it or when I do not know.