[vlc-devel] Re: Skins2 Error

[Olivier Teulière]

Hello,

On Thu, Nov 10, 2005, Mateus Krepsky Ludwich wrote:
> [00000240] main dialogs provider error: no dialogs provider module
> matched "any"
> [00000239] skins2 interface error: No suitable dialogs provider found
> (hint: compile thewxWidgets plugin, and make sure it is loaded
> properly)

There are 2 things to check:

1) Make sure that you really compiled the wxwidgets plugin. There should
   be a 'libwxwidgets_plugin.so' file in ./modules/gui/wxwidgets/
   If not, look more carefully the output of configure

2) Make sure the plugin is working: 'vlc -l' should list it. If it
   doesn't appear, it's probably because of an unresolved symbol in the
   plugin, it should be visible if you run 'vlc -vv -l'.

> Couldn't gzopen /home/mateus/.vlc/skins2/default.vlt
> [00000239] main interface error: no suitable access module for 
> `/home/mateus/.vlc/skins2/default.vlt'
> [00000239] skins2 interface error: Failed to open 
> /home/mateus/.vlc/skins2/default.vlt for reading
> [00000239] skins2 interface error: Failed to parse 
> /home/mateus/.vlc/skins2/default.vlt
> Couldn't gzopen share/skins2/default.vlt
> [00000239] main interface error: no suitable access module for 
> `share/skins2/default.vlt'
> [00000239] skins2 interface error: Failed to open 
> share/skins2/default.vlt for reading
> [00000239] skins2 interface error: Failed to parse share/skins2/default.vlt
> [00000239] skins2 interface: skin: VLC OSX Interface author: BigBen
> Segmentation fault

This is a different problem.

Was /home/mateus/.vlc/skins2/default.vlt present when you got these
logs? If so, do you have reading rights on the file (at least)?

I would be very interested in a backtrace, for the segfault.
(run 'ulimit -c unlimited', run vlc to get a core dump, then run
'gdb path/to/vlc/executable path/to/core', and finally type 'bt' inside
gdb).

-- 
Ipkiss

-- 
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html