On 2023/07/21 12:40, Alexis de BRUYN [Mailing Lists] wrote: > $ LD_DEBUG=1 flameshot > [...] > examining: '/usr/local/lib/qt5/libQt5XcbQpa.so.1.2' > loading: libz.so.5.0 required by /usr/local/lib/qt5/libQt5XcbQpa.so.1.2 > dlopen: failed to open libz.so.5.0 > > $ ll /usr/local/lib/qt5/libQt5XcbQpa.so* > -rw-r--r-- 1 root bin 3043000 May 21 19:56 > /usr/local/lib/qt5/libQt5XcbQpa.so.0.1 > -rw-r--r-- 1 root bin 3036224 Jul 17 17:30 > /usr/local/lib/qt5/libQt5XcbQpa.so.1.0 > -rw-r--r-- 1 root bin 1709088 Mar 7 2020 > /usr/local/lib/qt5/libQt5XcbQpa.so.1.2
Aha. There was a mistake in this update, : revision 1.36 : date: 2020/03/13 16:53:49; author: rsadowski; state: Exp; lines: +104 -66; commitid: 5XaCrjZTCfOR1LCV; : Update Qt to 5.13.2 and meta/qt5 The shared library version for libQt5XcbQpa went backwards. It should now be bumped to 2.0 so that it's handled automatically for anyone else in the situation. I'm a bit surprised that PLIST_DB allowed this to get into bulk builds. > $ doas rm -f /usr/local/lib/qt5/libQt5XcbQpa.so.1.2 > doas ([email protected]) password: You probably have some .libs packages lying around which could be pkg_delete'd. > All Qt-based programs are running fine now. > Thanks Stuart and Rafael for your help. Good :)
