I am seeing this issue immediately after upgrading to Version 1.5.0.3501. This behavior is not seen in prior versions.
I believe this is a minor issue. After upgrading to the 1.5.0.3501 release in the official plexinc/pms-docker:plexpass docker image, The following is recorded in the container logs:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 40-plex-first-run: executing...
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 50-plex-update: executing...
Attempting to upgrade to: 1.5.0.3501-3b8374a5c
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 177 100 177 0 0 224 0 --:--:-- --:--:-- --:--:-- 224
100 100M 100 100M 0 0 561k 0 0:03:03 0:03:03 --:--:-- 769k
(Reading database ... 10923 files and directories currently installed.)
Preparing to unpack /tmp/plexmediaserver.deb ...
/var/lib/dpkg/info/plexmediaserver.prerm: 13: /var/lib/dpkg/info/plexmediaserver.prerm: stop: not found
Unpacking plexmediaserver (1.5.0.3501-3b8374a5c) over (1.4.4.3495-edef59192) ...
Setting up plexmediaserver (1.5.0.3501-3b8374a5c) ...
Processing triggers for systemd (229-4ubuntu13) ...
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting Plex Media Server.
**Critical: libusb_init failed**
It does not appear, so far, that this actually affects plex operation, however my monitoring tools caught this, so I figured reporting it would be a good thing. I will post an update if I find it actually causes problems.