Nvim "vim-plug" plugin randomly disappeared.

clime · 2023-01-22 05:49:00

Hi, I'm not exactly sure where to post this as it seems odd.
Within my "~/.local/share/nvim folder" the path and file "site/autoload/plug.vim" simply disappeared.
I ran fzf -q plug.vim in my home directory and looked through my trash to see if I'd idiotically moved or deleted it on accident, but no luck.
It's as if a ghost decided to make it vanish (something I obviously find alarming).

The only significant things I did today was update my system and install Windows 11 on a VM.
I don't think updating my system could've caused this as neovim hasn't been updated since 12/29, and my plugins are all installed with my init.vim file.
When installing Windows 11, I did make the directory ".local/share/libvirt/images," yet I fail to see how that could possibly be related in any way.

Fixing the issue was easy, I just simply reinstalled the plugin, but I'd like to know if anyone else has had something similar happen after updating today or in the past.

Otherwise I'm simply left feeling spooky.

Thanks for any replies.

Last edited by clime (2023-01-23 07:33:53)

seth · 2023-01-22 08:26:10

https://wiki.archlinux.org/title/Audit_ … ies_access

The least supernatural explanation is that nvim deleted the file, in particular because of

and my plugins are all installed with my init.vim

clime · 2023-01-23 07:40:32

Hey thanks, I wasn't aware of the audit framework before, I'm playing around with it now.
Any idea how I can get it to log the arguments of commands (or get ausearch or aureport) and/or output it when I point a rule at a file?
If I set a rule to explicitly track execve system calls, it seems to do it implicitly :
see:

 type=EXECVE msg=audit(1674453466.099:1674): argc=3 a0="ausearch" a1="-k" a2="Execve"

in:

virtual-machine@vm123:~/audit-test$ ausearch -k Execve
[ . . . ]
----
time->Sun Jan 22 23:57:46 2023
type=PROCTITLE msg=audit(1674453466.099:1674): proctitle=6175736561726368002D6B00457865637665
type=PATH msg=audit(1674453466.099:1674): item=1 name="/lib64/ld-linux-x86-64.so.2" inode=5249928 dev=fc:03 mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
type=PATH msg=audit(1674453466.099:1674): item=0 name="/usr/sbin/ausearch" inode=5244196 dev=fc:03 mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
type=CWD msg=audit(1674453466.099:1674): cwd="/home/virtual-machine/audit-testbed"
type=EXECVE msg=audit(1674453466.099:1674): argc=3 a0="ausearch" a1="-k" a2="Execve"
type=SYSCALL msg=audit(1674453466.099:1674): arch=c000003e syscall=59 success=yes exit=0 a0=562b261e3d20 a1=562b261c5060 a2=562b261dd2f0 a3=8 items=2 ppid=1882 pid=5399 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=pts0 ses=2 comm="ausearch" exe="/usr/sbin/ausearch" subj=unconfined key="Execve"

Yet if I want to track by key or by another syscall (e.g. chmod), it doesn't print that field:

virtual-machine@vm123:~/audit-test$ ausearch -k TestWatchedFile
[ . . . ]
----
time->Mon Jan 23 00:02:11 2023
type=PROCTITLE msg=audit(1674453731.918:1878): proctitle=6175736561726368002D696600756E772D6469722F77617463686564002D69
type=PATH msg=audit(1674453731.918:1878): item=0 name="unw-dir/watched" inode=405385 dev=fc:03 mode=0100775 ouid=1000 ogid=1000 rdev=00:00 nametype=NORMAL cap_fp=0 cap_fi=0 cap_fe=0 cap_fver=0 cap_frootid=0
type=CWD msg=audit(1674453731.918:1878): cwd="/home/virtual-machine/audit-testbed"
type=SYSCALL msg=audit(1674453731.918:1878): arch=c000003e syscall=257 success=yes exit=3 a0=ffffff9c a1=5646129893f0 a2=0 a3=0 items=1 ppid=5583 pid=5584 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts4 ses=2 comm="ausearch" exe="/usr/sbin/ausearch" subj=unconfined key="testWatchedFile"

If this is straying too far from the post topic I understand, thanks for the help either way.
___

Also: Sorry, I must've been tired when I made the post because the plugin name is "vim-plug," not "plugged," lol.
I updated my post to reflect this.
I doubt that nvim itself is responsible because It's a pretty popular plugin, and I didn't see anything on the github issues page.

seth · 2023-01-23 08:27:59

https://lore.kernel.org/lkml/1390931954 … resys.com/
The process arguments are part of the execve, for everything else you'd need to log /proc/??/cmdline next to /proc/??/comm

I'm not saying the plugin deleted stuff here, I'm more looking at "my plugins are all installed with my init.vim" …

Arch Linux

#1 2023-01-22 05:49:00

Nvim "vim-plug" plugin randomly disappeared.

#2 2023-01-22 08:26:10

Re: Nvim "vim-plug" plugin randomly disappeared.

#3 2023-01-23 07:40:32

Re: Nvim "vim-plug" plugin randomly disappeared.

#4 2023-01-23 08:27:59

Re: Nvim "vim-plug" plugin randomly disappeared.

Board footer