SUMMARY STEPS TO REPRODUCE 1. Go to `.local/share/applications/Vim.desktop 2. Have `Exec=konsole -e "vim"` and Terminal=0 3. Open a file in vim Here is a video showing the problem. https://youtu.be/jiXCqLI9uec OBSERVED RESULT Craziness. EXPECTED RESULT ... uhm... nothing to happen. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Copying the vim.desktop file from `/usr/share/applications' to `.local/share/applications fixes the problem... though a new file appeared there called Vim.desktop which has `konsole -e "vim"` as exec. And yes it appeared there by itself. Also my desktop wallpaper keep changing to default one (for this 5.14 release) and after that I noticed vim acting up again. Might be related.
Just in time for https://andrewcrouthamel.wordpress.com/2018/10/17/kde-bugsquad-konsole-bug-day-on-october-20th-2018/ Hmmmmm.
And before somebody asks, no, is not my vimrc file. If it was then why a vim.desktop changes make it go away. Also Gvim and urxvt are fine too.
Can you attach your Vim.desktop file?
Created attachment 115796 [details] vim.desktop By default it has `konsole -e "vim"` not sure why. Also I replaced it with `vim %F` with run in terminal. Not sure if that is the issue or not. Seems that for the most part having vim start in terminal instead makes the issue go away most often than not but not every time. This is why I switched to gvim for now. The vim.desktop in `/usr/share/applications` is this actually: https://github.com/vim/vim/blob/master/runtime/vim.desktop Not sure why vim is changed there. This is my vimrc https://gitlab.com/RaitaroH/Random-Code/blob/master/dot/vimrc
Does the issue reproduce if you temporarily move aside your vimrc file?
(In reply to Nate Graham from comment #5) > Does the issue reproduce if you temporarily move aside your vimrc file? Well the problem doesn't seem to appear but I noticed that after looking in my vimrc for what may cause it, relativenumber was pretty much it from what I could tell. Even still the problem appeared with that not being there but it was less severe. The most effective resolve was to have the desktop file changed instead. Not to mention that the problem appeared basically only when starting from a double click in dolphin rather than starting vim from a terminal. Not sure if that helps. Yet again... my vimrc doesn't seem to impact gvim or urxvt at all, or konsole if vim is started as a command from the terminal...
Created attachment 115823 [details] qdbus org.kde.KWin /KWin supportInformation
Damn... I have been trying to reproduce this today but, I can't. My new vimrc, the old vimrc, no vimrc, konsole -e or not. Well it is in line with my experience so far. I had a reinstall of KDE Neon (a failed Antergos installed) and I hoped the problem would go away. A few days it was, it came back, it went away, it came back, today it seems it went away again. Is this even possible...
Hmm, well I'm afraid if it's not consistent than it's going to be a challenge to debug. Any chance you could try to find a reproducible test case?
(In reply to Nate Graham from comment #9) > Hmm, well I'm afraid if it's not consistent than it's going to be a > challenge to debug. Any chance you could try to find a reproducible test > case? Could it be Nvidia or Kwin at fault instead?
Well I have been using gvim for now. I also see that sometimes gvim doesn't display a line or 2 even if they are there, but is not the same as the bug I showed in the video, or if it is then it is veeery low intensity. I suppose 'worksforme'