Bug 864796 - [abrt] evince-3.6.0-1.fc18: _gdk_x11_display_error_event: Process /usr/bin/evince was killed by signal 5 (SIGTRAP)
Summary: [abrt] evince-3.6.0-1.fc18: _gdk_x11_display_error_event: Process /usr/bin/ev...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e95dd634213abac57b76224375a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-10 07:17 UTC by Juanjo Marin
Modified: 2012-10-19 01:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-19 01:51:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: core_backtrace (10.99 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: environ (1.75 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: limits (1.29 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: backtrace (70.83 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: cgroup (130 bytes, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: maps (59.15 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: dso_list (12.84 KB, text/plain)
2012-10-10 07:17 UTC, Juanjo Marin 		no flags Details
File: proc_pid_status (919 bytes, text/plain)
2012-10-10 07:18 UTC, Juanjo Marin 		no flags Details
File: var_log_messages (264 bytes, text/plain)
2012-10-10 07:18 UTC, Juanjo Marin 		no flags Details
File: open_fds (1.13 KB, text/plain)
2012-10-10 07:18 UTC, Juanjo Marin 		no flags Details
View All

Description Juanjo Marin 2012-10-10 07:17:36 UTC 
Version-Release number of selected component:
evince-3.6.0-1.fc18

Additional info:
libreport version: 2.0.15
abrt_version:   2.0.14
backtrace_rating: 4
cmdline:        evince '/home/jjmarin/Escritorio/PRESUPUESTO DE MANTENIMIENTO 2012.pdf'
crash_function: _gdk_x11_display_error_event
kernel:         3.6.0-3.fc18.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2417
: #6 handle_error at xcb_io.c:212
: #7 handle_response at xcb_io.c:324
: #9 XInternAtom at IntAtom.c:181
: #10 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:244
: #12 get_net_supporting_wm_check at gdkscreen-x11.c:1284
: #13 fetch_net_wm_check_window at gdkscreen-x11.c:1321
: #14 gdk_x11_screen_supports_net_wm_hint at gdkscreen-x11.c:1402
: #15 gdk_x11_window_set_user_time at gdkwindow-x11.c:3078
: #16 setup_toplevel_window at gdkwindow-x11.c:697
Comment 1 Juanjo Marin 2012-10-10 07:17:44 UTC 
Created attachment 624619 [details]
File: core_backtrace
Comment 2 Juanjo Marin 2012-10-10 07:17:46 UTC 
Created attachment 624620 [details]
File: environ
Comment 3 Juanjo Marin 2012-10-10 07:17:50 UTC 
Created attachment 624621 [details]
File: limits
Comment 4 Juanjo Marin 2012-10-10 07:17:52 UTC 
Created attachment 624622 [details]
File: backtrace
Comment 5 Juanjo Marin 2012-10-10 07:17:54 UTC 
Created attachment 624623 [details]
File: cgroup
Comment 6 Juanjo Marin 2012-10-10 07:17:57 UTC 
Created attachment 624624 [details]
File: maps
Comment 7 Juanjo Marin 2012-10-10 07:17:59 UTC 
Created attachment 624625 [details]
File: dso_list
Comment 8 Juanjo Marin 2012-10-10 07:18:01 UTC 
Created attachment 624626 [details]
File: proc_pid_status
Comment 9 Juanjo Marin 2012-10-10 07:18:03 UTC 
Created attachment 624627 [details]
File: var_log_messages
Comment 10 Juanjo Marin 2012-10-10 07:18:05 UTC 
Created attachment 624628 [details]
File: open_fds
Comment 11 Marek Kašík 2012-10-10 08:59:48 UTC 
This is probably a problem in gdk or gtk+. It is similar to the one from #856752. I'm reassigning this to gtk+ now.

Marek
Comment 12 Matthias Clasen 2012-10-19 01:51:58 UTC 
The crash is happening in _gtk_text_handle_create_window. We've had a problem in that function which was fixed in 3.6.1 - I assume this is probably the same
Note You need to log in before you can comment on or make changes to this bug.