You seem to be mixing up several things.
./configure
--prefix=/usr
--disable-wxwindows
--disable-wxwidgets
--enable-aa
--disable-skins2
--disable-joystick
--disable-kde
--disable-qt
--enable-ncurses
--enable-release
--enable-dvdread
First of all, remove the "--disable-wxwindows" flag, it is deprecated and is replaced by the --disable-wxwidgets" one.
If you build with --disable-skins2_and --disable-wxwidgets, then yes, you won't have the skins interface nor the wxwidgets interface. You will have the dummy interface by default, but you can still use the rc one (vlc --intf rc), the http one (vlc --intf http), the ncurses one (vlc --intf ncurses), etc..., depending on which ones you enabled in configure.
If you build with --enable-skins2 and --disable-wxwidgets, then the skins interface will be the default one, but won't be very useful because no dialog box will be available. This will give you the "No suitable dialogs provider found" message.
If you build with --disable-skins2 and --enable-wxwidgets, then the wxWidgets interface will be the default one, and you will get no skins.
If you build with --enable-skins2 and --enable-wxwidgets, then the wxWidgets interface will be the default one. Skins will also be available (vlc --intf skins2, or "Switch interface" in the Settings menu) and will work completely, without any restriction due to the dialogs provider.
I'm not disagreeing with you, but I am saying that just disabling skins2 during the compile process made the normal wx interface work...
As explained above, this is not possible if you only changed --enable-skins2 into --disable-skins2 (unless you have found a very weird bug, but i really doubt it). But this is possible if you changed --disable-wxwidgets into --enable-wxwidgets at the same time.
[00000545] main video output warning: late picture skipped (1133195)
[00000545] main audio output warning: PTS is out of range (901527), dropping buffer
[00000499] avi private warning: unknown chunk (not unloaded)
This has nothing to do with the combination of interfaces you use (skins2/wxWidgets).
I think I'm just going to disable skins2 since I have no need for a skin anyway.
Do as you like. What i wanted to point out is that enabling or disabling the skins2 interface doesn't change anything to the fact that the wxWidgets interface is working or not, or to the fact that you get the above warnings in the logs.