Skip to content

--no-qt-privacy-ask does not persist between invocations in 4.0.x

I was trying some installation automation we have with a 4.0.x build (20210920 win64; specifically this). We typically install the 3.x series and then run it with --no-qt-privacy-ask --quiet vlc://quit once to ensure that the notifications and privacy dialog does not come up afterwards. If it does, it foils automation that runs tests using VLC.

We found that the flags seem to be accepted but they don't persist between runs now. We have to specify --no-qt-privacy-ask each time if we want to avoid it.

Workaround: For the sake of automation with the beta builds, I just dump a pre-created vlcrc into the application data path that has already clicked through and set up everything. This workaround is sufficient and also helps standardize theme and UI so I might stick with it. Nonetheless, I wanted to report this as a regression that somebody might find interesting.

This was found in the Windows 64 builds of the 4.0.x build, namely 20210920. It was found on various Windows 10 images of different build numbers. I can provide specifics for any of them if it seems to matter.

Edited by rockobonaparte
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information