Bug#794983: vlc does weird things with the .lock file

[sacrificial-spam-address at horizon.com]

Package: vlc
Version: 2.2.1-2+b2
Architecture: i386
Severity: minor

Somehow (it may have been a transient error caused by C++ ABI upgrades),
I ended up with:

$ ls ~/.config/vlc/
vlc-qt-interface.conf
vlc-qt-interface.conf.lock
vlc-qt-interface.conf.lock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock
...
vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock

and ended up with vlc stuck looping retrying

open("/home/xxxxxxx/.config/vlc/vlc-qt-interface.conf.lock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock.rmlock", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE|O_CLOEXEC, 0644) = -1 ENAMETOOLONG (File name too long)

(Note that at no point did I have more than two copies of vlc running.)


Once I deleted all those files, things started working.  But shouldn't it be
able to figure out that ENAMETOOLONG won't be solved by retrying?