OK, thanks.

First, let me note I use Smart for my software management, and not YaST/zypper, so you will have the assessment of someone who knows very little about this, but rather someone who is just looking at what he see's, and asking: "does that make sense?".

I was hoping one of our experienced YaST users would chime in, but thus far that has not happened.

Anyway, my observations are:
a. Item-6 (nvidia) looks strange to me. I don't think it is an "rpm-md" format, and I recommend you remove this repos for the moment. You can always add it later.
b. Item-15 (debug repos) of type NONE. That looks strange to me. Should not the type be identified? I recommend you remove this repos for the moment. You can always add it later if I am wrong.
c. Item-2 (updates) and Item-14 (Non-OSS) are clearly essential. I confess I am not familiar with type "yast-2". Did you insert these manually yourself, or was this handled by the YaST software GUI ? If you did this syntax yourself, I would be suspicious, but if done by YaST, then it should be ok.
d. Item-10 (packman). The format of the Packman Unixheads URL struck me as somewhat strange. Again, did you insert this manually yourself, or was this handled by the YaST software GUI ? If you did this syntax yourself, I would be suspicious, but if done by YaST, then it should be ok.

And finally, I noted you have both VideoLAN and Packman active at the same time. That will not cause a segmentation fault, but it will cause circular dependency problems for installation attempts of some applications. I recommend you disable VideoLAN, and leave it that way, and only enable IF and WHEN there is a VideoLAN app that you want, that you can not get from Packman.

And finally, to repeat myself, I am NOT a YaST user. I am a Smart user. These are only my observations.

If this doesn't do the trick, I can provide the commands for an rpm database rebuild, but I think it more likely this is a bad URL entry in the repository table of YaST.