Bug 1466480 - [abrt] neovim: wstream_write(): nvim killed by signal 6
Summary: [abrt] neovim: wstream_write(): nvim killed by signal 6
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: neovim
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6b5375d4c725c43b9b326c37cc5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-29 18:25 UTC by Ed Marshall
Modified: 2018-05-29 11:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:25:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.68 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: cgroup (355 bytes, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: core_backtrace (5.13 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: cpuinfo (1.34 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: dso_list (1.37 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: environ (5.00 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: limits (1.29 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: maps (7.09 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: open_fds (1.20 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: proc_pid_status (1.28 KB, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details
File: var_log_messages (301 bytes, text/plain)
2017-06-29 18:25 UTC, Ed Marshall
no flags Details

Description Ed Marshall 2017-06-29 18:25:11 UTC
Description of problem:
Exited neovim.

Version-Release number of selected component:
neovim-0.2.0-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        nvim ImageMagick/ImageMagick.dll.config
crash_function: wstream_write
executable:     /usr/bin/nvim
journald_cursor: s=2ff631a66afd403d8e8fe0a534e20e41;i=43181;b=c5baa8d1ac064e1ea7163a1d30a79493;m=b2de9d1f3;t=5531d5d7bb984;x=5952fbec70f9c42
kernel:         4.11.6-301.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 wstream_write at /usr/src/debug/neovim-0.2.0/src/nvim/event/wstream.c:77
 #5 channel_write at /usr/src/debug/neovim-0.2.0/src/nvim/msgpack_rpc/channel.c:500
 #6 on_request_event at /usr/src/debug/neovim-0.2.0/src/nvim/msgpack_rpc/channel.c:472
 #7 multiqueue_process_events at /usr/src/debug/neovim-0.2.0/src/nvim/event/multiqueue.c:150
 #8 event_teardown at /usr/src/debug/neovim-0.2.0/src/nvim/main.c:162
 #10 getout at /usr/src/debug/neovim-0.2.0/src/nvim/main.c:647
 #11 ex_exit at /usr/src/debug/neovim-0.2.0/src/nvim/ex_docmd.c:6329
 #12 do_one_cmd at /usr/src/debug/neovim-0.2.0/src/nvim/ex_docmd.c:2240
 #13 do_cmdline at /usr/src/debug/neovim-0.2.0/src/nvim/ex_docmd.c:606
 #14 nv_colon at /usr/src/debug/neovim-0.2.0/src/nvim/normal.c:4498

Comment 1 Ed Marshall 2017-06-29 18:25:16 UTC
Created attachment 1292939 [details]
File: backtrace

Comment 2 Ed Marshall 2017-06-29 18:25:16 UTC
Created attachment 1292940 [details]
File: cgroup

Comment 3 Ed Marshall 2017-06-29 18:25:17 UTC
Created attachment 1292941 [details]
File: core_backtrace

Comment 4 Ed Marshall 2017-06-29 18:25:18 UTC
Created attachment 1292942 [details]
File: cpuinfo

Comment 5 Ed Marshall 2017-06-29 18:25:19 UTC
Created attachment 1292943 [details]
File: dso_list

Comment 6 Ed Marshall 2017-06-29 18:25:20 UTC
Created attachment 1292944 [details]
File: environ

Comment 7 Ed Marshall 2017-06-29 18:25:21 UTC
Created attachment 1292945 [details]
File: limits

Comment 8 Ed Marshall 2017-06-29 18:25:21 UTC
Created attachment 1292946 [details]
File: maps

Comment 9 Ed Marshall 2017-06-29 18:25:22 UTC
Created attachment 1292947 [details]
File: open_fds

Comment 10 Ed Marshall 2017-06-29 18:25:23 UTC
Created attachment 1292948 [details]
File: proc_pid_status

Comment 11 Ed Marshall 2017-06-29 18:25:24 UTC
Created attachment 1292949 [details]
File: var_log_messages

Comment 12 Andreas Schneider 2017-07-04 13:49:18 UTC
Please report it upstream. Thanks!

Comment 13 Fedora End Of Life 2018-05-03 08:06:49 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora  'version'
of '26'.

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 26 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 14 Fedora End Of Life 2018-05-29 11:25:44 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.