Bug 1000663 - [abrt] cinnamon-1.9.1-19.fc19: _gdk_x11_display_error_event: Process /usr/bin/cinnamon was killed by signal 5 (SIGTRAP)
Summary: [abrt] cinnamon-1.9.1-19.fc19: _gdk_x11_display_error_event: Process /usr/bin...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cogl
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aab5da826e031c7449b0c228173...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-24 02:57 UTC by jcrosscope
Modified: 2015-02-17 16:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 16:53:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (60.98 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: cgroup (140 bytes, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: core_backtrace (13.72 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: dso_list (6.68 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: environ (1.38 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: limits (1.29 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: maps (95.26 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: open_fds (3.21 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: proc_pid_status (957 bytes, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details
File: var_log_messages (3.50 KB, text/plain)
2013-08-24 02:57 UTC, jcrosscope
no flags Details

Description jcrosscope 2013-08-24 02:57:03 UTC
Description of problem:
Debugging Tika project in Netbeans 7.3.  (And working in two virtual screens, couple of terminal tabs open but not running any apps at the time,  file browser, geany text editor, firefox browser.)  Was examining variables in the debugger (to wit, var type was tika.sax.BodyContentHandler, probably holding a sizeable chunk of data), when system froze, flashed a few times, then got a "Cinnamon crashed" popup.  Was working in Fedora 19 envt, on VMware player, on Windows 8, Dell XPS-8500 machine, then turtles all the way down.

Version-Release number of selected component:
cinnamon-1.9.1-19.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        cinnamon --replace
crash_function: _gdk_x11_display_error_event
executable:     /usr/bin/cinnamon
kernel:         3.10.5-201.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2556
 #5 handle_error at xcb_io.c:213
 #7 XShmGetImage at XShm.c:386
 #8 _cogl_texture_pixmap_x11_update_image_texture at winsys/cogl-texture-pixmap-x11.c:584
 #9 _cogl_texture_pixmap_x11_update at winsys/cogl-texture-pixmap-x11.c:667
 #10 _cogl_texture_pixmap_x11_pre_paint at winsys/cogl-texture-pixmap-x11.c:909
 #11 _cogl_pipeline_layer_pre_paint at ./cogl-pipeline-layer.c:858
 #12 _cogl_pipeline_pre_paint_for_layer at ./cogl-pipeline.c:2498
 #13 _cogl_rectangles_validate_layer_cb at ./cogl-primitives.c:535
 #14 cogl_pipeline_foreach_layer at ./cogl-pipeline.c:723

Potential duplicate: bug 991839

Comment 1 jcrosscope 2013-08-24 02:57:07 UTC
Created attachment 789761 [details]
File: backtrace

Comment 2 jcrosscope 2013-08-24 02:57:10 UTC
Created attachment 789762 [details]
File: cgroup

Comment 3 jcrosscope 2013-08-24 02:57:12 UTC
Created attachment 789763 [details]
File: core_backtrace

Comment 4 jcrosscope 2013-08-24 02:57:15 UTC
Created attachment 789764 [details]
File: dso_list

Comment 5 jcrosscope 2013-08-24 02:57:17 UTC
Created attachment 789765 [details]
File: environ

Comment 6 jcrosscope 2013-08-24 02:57:20 UTC
Created attachment 789766 [details]
File: limits

Comment 7 jcrosscope 2013-08-24 02:57:22 UTC
Created attachment 789767 [details]
File: maps

Comment 8 jcrosscope 2013-08-24 02:57:25 UTC
Created attachment 789768 [details]
File: open_fds

Comment 9 jcrosscope 2013-08-24 02:57:27 UTC
Created attachment 789769 [details]
File: proc_pid_status

Comment 10 jcrosscope 2013-08-24 02:57:30 UTC
Created attachment 789770 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-01-09 19:34:31 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 12 Fedora End Of Life 2015-02-17 16:53:58 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


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