Description of problem: Crash Neovim when I switch git branch. I used vim-fugitive plugin Version-Release number of selected component: neovim-0.8.2-2.fc38 Additional info: reporter: libreport-2.17.6 executable: /usr/bin/nvim uid: 1000 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-kitty-19278.scope type: CCpp crash_function: snprintf runlevel: N 5 reason: nvim killed by SIGABRT package: neovim-0.8.2-2.fc38 cmdline: nvim kernel: 6.2.0-0.rc5.20230126git7c46948a6e9c.41.fc38.x86_64 backtrace_rating: 4 journald_cursor: s=5466554a1b744edfb0ff535ea9bd8566;i=d2a7a;b=cc19103144984513880d0e974743db4f;m=1c8fe333c;t=5f37535f32c75;x=355482c9876d6da1 comment: Crash Neovim when I switch git branch. I used vim-fugitive plugin rootdir: / Truncated backtrace: Thread no. 1 (24 frames) #8 snprintf at /usr/include/bits/stdio2.h:54 #9 set_cmdarg at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/eval.c:7044 #10 apply_autocmds_group at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/autocmd.c:1843 #11 apply_autocmds_exarg at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/autocmd.c:1549 #12 readfile at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/fileio.c:617 #13 buf_reload at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/fileio.c:5038 #14 buf_check_timestamp at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/fileio.c:4952 #15 check_timestamps at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/fileio.c:4678 #16 ex_checktime at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_cmds2.c:765 #17 execute_cmd0 at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:1620 #18 do_one_cmd at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:2275 #19 do_cmdline at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:584 #20 ex_execute at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/eval.c:7727 #21 execute_cmd0 at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:1620 #22 do_one_cmd at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:2275 #23 do_cmdline at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:584 #24 do_ucmd at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/usercmd.c:1661 #25 execute_cmd0 at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:1612 #26 do_one_cmd at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:2275 #27 do_cmdline at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/ex_docmd.c:584 #28 nv_colon at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/normal.c:4058 #29 normal_execute at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/normal.c:1172 #30 state_enter at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/state.c:88 #31 normal_enter at /usr/src/debug/neovim-0.8.2-2.fc38.x86_64/src/nvim/normal.c:471
Created attachment 1941222 [details] File: dso_list
Created attachment 1941223 [details] File: core_backtrace
Created attachment 1941224 [details] File: limits
Created attachment 1941225 [details] File: proc_pid_status
Created attachment 1941226 [details] File: environ
Created attachment 1941227 [details] File: backtrace
Created attachment 1941228 [details] File: mountinfo
Created attachment 1941229 [details] File: cpuinfo
Created attachment 1941230 [details] File: open_fds
Created attachment 1941231 [details] File: os_info
Created attachment 1941232 [details] File: maps
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
Can you still reproduce this with neovim 0.8.3?
I was editing a file using suda (https://github.com/lambdalisue/suda.vim) to provide root access. When launching new foot instance, first one coredumped either neovim or shell itself. Now the shell instance is writing nonsense to terminal when interacting with mouse. reporter: libreport-2.17.8 type: CCpp reason: nvim killed by SIGABRT journald_cursor: s=62794396469f46beaaf17c6f082d7eed;i=12226;b=6575f03d29fc4b8d91c786987b752a00;m=a3969573;t=5f74f9b0cb312;x=120ece8379480ce7 executable: /usr/bin/nvim cmdline: nvim tekniset/chale_ja_trikkipower.md cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-foot.slice/app-foot-1893.scope rootdir: / uid: 1000 kernel: 6.2.7-300.fc38.x86_64 package: neovim-0.8.3-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: snprintf
Created attachment 1951919 [details] File: backtrace
Created attachment 1951921 [details] File: backtrace
Created attachment 1951922 [details] File: backtrace
Created attachment 1951923 [details] File: backtrace
In order to debug this we would need a reproducer with an minimal config file. Please document the steps clearly how to reproduce. Here is a minimal config file you can modify. Save as repro.lua and run with `nvim -u repro.lua`. Once you have a reproducer create a tarball of the ~/.repro directory: -- DO NOT change the paths and don't remove the colorscheme local root = vim.fn.fnamemodify("./.repro", ":p") -- set stdpaths to use .repro for _, name in ipairs({ "config", "data", "state", "cache" }) do vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name end -- bootstrap lazy local lazypath = root .. "/plugins/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, }) end vim.opt.runtimepath:prepend(lazypath) -- install plugins local plugins = { "folke/tokyonight.nvim", -- add any other plugins here } require("lazy").setup(plugins, { root = root .. "/plugins", }) vim.cmd.colorscheme("tokyonight") -- add anything else here
FEDORA-2023-7416df909b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7416df909b
FEDORA-2023-7416df909b has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-d8042dffac has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8042dffac
FEDORA-2023-127fdc9d84 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-127fdc9d84
FEDORA-2023-127fdc9d84 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-127fdc9d84` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-127fdc9d84 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-d8042dffac has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8042dffac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5e6280ef5d has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5e6280ef5d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5e6280ef5d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-b9ec085715 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b9ec085715 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-b9ec085715 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-5e6280ef5d has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days