[Bug]: Vim doesn't open (X11, XFCE) #22733
Comments
|
Could you post a Bash script installer that works to fully reproduce your exact crash non-interactively within a clean installed Termux installation? I used these commands, but after using them, Vim is not crashing for me, instead, every time I push an arrow key in Vim, I see this error: cd
wget https://raw.githubusercontent.com/DuilioPerez/Utilities/refs/heads/main/.vimrc
curl -fLo ~/.vim/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
mkdir -p ~/.vim/pack/themes/start
cd ~/.vim/pack/themes/start
git clone https://github.com/dracula/vim.git dracula
vim ~/.vimrcAfter using those commands, the |
|
To install, excecute this script: cd ~
wget https://raw.githubusercontent.com/DuilioPerez/Utilities/refs/heads/main/.vimrc
curl -fLo ~/.vim/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vimNow open vim, it'll give some errors because plugins aren't downloaded. Inside vim excecute |
|
Here it is a video with the steps: XRecorder_02012025_071509.mp4 |
|
Very interesting, and I wonder what the difference between your device, and others' devices, must be, that results in the crash, because, I tested what seems to me like the exact same steps you show in your video, multiple times, on both a 32-bit ARM device that has Android 7, and a 64-bit ARM device that has Android 10, and unfortunately I have still not been able to reproduce what you show happening. This is a video of what I recorded happening when I do the same steps on the 32-bit ARM device with a fairly clean, fully updated Termux installation, and I can't see anything out of the ordinary, other than that the large number of Vim plugins begins to slow down Vim a little bit on this device. vimcrashreproductionattempt.webmWould it be possible for you to recompile Vim with debug symbols enabled, and try getting what is called a "C language debugging backtrace" of your crash, which is a diagnostic report that contains additional information about the crash, that cannot be obtained on any environment where the crash cannot yet be reproduced? These are the commands to do that (requires an amd64 Docker system to build, after which the # amd64 system with docker installed
git clone https://github.com/termux/termux-packages.git
cd termux-packages
scripts/run-docker.sh ./build-package.sh -I -f -d vim
ls output# Termux
pkg reinstall ./vim*.deb
pkg install gdb
gdb vim
run
bt |
|
Unfortunatly, I can't recompile vim because I don't have access to an AMD environment. Maybe on device. The interesting thing is that it is happening since the last update. I've used vim on Termux for a long time and the plugins I've added have been tested by me. I've been using Vim on Termux for more than two years. |
|
I've found the issue. It seems the plugin vim-polyglot cause the crash. I added some month ago. Thank you and closing now. |
truboxl
added
not-bug
|
Weird, because while using your |
|
As note, in the previous version of vim it worked very well. There's a similar bug in Visual Studio Code in the TUR repo, which as far as I tested, because I don't use it much, since the new update, it close if you click in file menu. |
|
Take a look here to see the issue with polyglot XRecorder_02012025_193916.mp4 |
|
If you think this is an issue with Termux, then I'll reopen the issue report |
Since it works when vim-polyglot is not installed, and fails when it is installed my best guess would have to be that this is an issue with how vim-polyglot handles an empty filetype ( |
|
If I rememer, it worked just well before updating vim. And If I'm right, there was two updates of vim with less than two weeks of difference |
|
I'll try to replicate and troubleshoot the issue.
I assume these up here are the reproduction steps? |
|
I can't replicate the issue. |
|
Please share |
|
I guess is this: |
|
I don't see anything relating to Vim or any segfault in the log above. Just as a sanity check I also tested this against Neovim, with the same result. |
I posted a detailed workaround for that one in the discord, so I will show it to you too - since it was tracked upstream, I'd just assumed that after enough updates come to TUR for microsoft/vscode#230604 (comment) workaround that can avoid that crash when i tested: press Ctrl + Shift + P to open command palette -> keyboard shortcuts settings -> create: new file -> rebind it to any combination that does not contain the "Super" key
|
|
I've tested today and logcat doesn't register that signal. XRecorder_03012025_161226.mp4 |
|
|
|
I've fixed the issue in a very strange way. I installed strace to track signals, but it didn't show anything. After restarting Termux it now open vim without arguments loading vim-polyglot very well |
|
Wait a moment. It seems I've found the source of the issue. It seems to be related to xfce4: XRecorder_04012025_132333.mp4 |
|
That explains why I haven't been able to replicate it. |
|
I'm sure now. It seems for some reason it propagated to Termux terminal. In LXQt it works well |
|
This is what I could save to a |
truboxl
added
bug report
Problem description
I'm a regular Vim user. I haves used Vim in Termux since a lot of time ago. But now doesn't open since last update. It open just if I don't use my .vimrc, but in that mode, Vim is very basic. It reports the next error:
What steps will reproduce the bug?
You can see it here
What is the expected behavior?
To open normally
System information
The text was updated successfully, but these errors were encountered: