The VideoLAN Forums

This seems to be the bane of my life.
New update of OS (opensuse Leap15), and once again am having issues connecting to dlna resources that are easily connected to, for example, by Kodi running on opensuse, or Bubbleupnp running on Android.
Those apps connect and play without issues/delays etc, but when trying to use VLC (have tried both the opensuse package (3.0.2) and now trying the packman beta (4.0.0-dev), and they will not find my Fetch TV at all, will find one of my other nas sources almost straight away, and takes many minutes to find another couple of resources...
I don't understand. Would really like to be able to use vlc, but at this point, I cannot.

Was it caused by updating the OS or VLC? That makes all the difference...

Probably a bit of both...
Have changed hardware, and carried my original drives across, which resulted in me basically doing an 'in-place' upgrade, which replaced my VLC repo version of VLC (beta, probably), with one from the opensuse repos. As I said, have then connected back to the Packman and VLC repos...
So...
Apart from doing a full reinstall of the OS (which I don't REALLY think would be any more likely to fix things)....

OK, have done a FULL reinstall (Leap15 x64 + updates) ie formatted the system drive, brand new user, nothing carried over from the previous install, and if anything, I am now worse off, as I can see NO DLNA resources on the network. I have at least 3: a Gerbera Media server, a Fritzbox router (NAS), and a Fetch TV box.
These can be seen by various other DLNA clients that I have eg BubbleUPNP running on Android, Kodi Client, Windows 10 machine.
Why can I not see them in VLC? (3.0.2 Vetinari - 3.0.2-lp150.3.6-x86_64 from vendor http://packman.links2linux.de)
Thanks.

Hi, would you have verbose logs? It could come from a missing library like microdns or default firewall configuration for example, but if other clients can see them it's probably a missing library.
You can also give the result of VLC 3.0.2 is starting to be old too.

Hi, would you have verbose logs?
You can also give the result of

Code: Select all

vlc -l

Thanks for the response.
Have done the vlc -l (https://drive.google.com/open?id=1SVQAq ... gEjDGW_G5V) and just saved the log when logged in at the command line (https://drive.google.com/open?id=150X8e ... MzG_QOj0vd)
Not sure how useful this is...?
Thanks.