Comment # 48 on bug 1174406 from Robin Klitscher

Yes; I���m using Packman and others, including openSUSE/Plasma/Qt update channels
from http://download.opensuse.org.  My current Leap 15.2 system is at:  

Operating System: openSUSE Leap 15.2
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0
Kernel Version: 5.3.18-lp152.33-default
OS Type: 64-bit
Processors: 8 �� Intel�� Core��� i7-4770 CPU @ 3.40GHz
Memory: 31.3 GiB of RAM
Graphics Processor: GeForce GTX 670/PCIe/SSE2

This is a multi-boot machine upon which, largely for historical reasons and
curiosity but also for prudence, I maintain separate Leap 15.2, Leap 15.1 and
Tumbleweed installations.  Each has its own /home ��� non-shared; and each is
always installed fresh, not as upgrades.

A couple of months or so ago (before Leap 15.2) I first ran into the USB
problem with VirtualBox and Win 10 in Leap 15.1, using the Oracle package, not
the openSUSE ones.  That Vbox setup had worked very well for several years,
consistently under a succession of previous editions of Leap/openSUSE.  

Initially in 15.2 it worked briefly, then quit.  This might indeed tend to
support an idea that something from the component update repos I���m using could
be the problem.

As an experiment, last evening I installed Vbox into my current Tumbleweed host
in the hope that Tumbleweed, being Tumbleweed, might not be prey to similar
update error.  But I got the same result ��� no USB in the Win 10 guest. 

For what it may be worth, I attach the output of zypper lr -e for each of these
three installations.  For simplicity the texts have been edited to remove
several repos not held in common (or equivalent) across the three systems.  If
the source of the problem is an inappropriate component update, it would have
to exist in all three systems.