The gentoo ebuild has some kind of weird interaction with QT libraries, which fail to load. I could now figure how to fix, hence I reported a bug upstream (see link). Reproducible: Always
...and what exactly is that supposed weird interaction in the ebuild?
Please see the screenshots in the upstraem bug.
How is that related to the ebuild?
(In reply to Andreas Sturmlechner from comment #3) > How is that related to the ebuild? Because the upstream AppImage works, so it implies it may be a packaging issue.
Please share the full terminal output.
I don't have any issues with other QT5 programs on this system. The software when compiled from source does not have the issue. Downgrading to 3.12 resolved the issue. It's specifically an issue with that ebuild version. Full output of the terminal is: QPainter::begin: Paint device returned engine == 0, type:2 QPainter::begin: Paint device returned engine == 0, type:2 QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::drawRects: Painter not active QPainter::setPen: Painter not active ... endless repeats of these messages...
(In reply to Sam James from comment #4) > Because the upstream AppImage works, so it implies it may be a packaging > issue. The wording implied the bug reporter had knowledge of a specific weird interaction in our ebuild. The Appimage may just use a different version of Qt.
(In reply to OzTiram from comment #6) > The software when compiled from source does not have the issue The ebuild for 3.13.0 and 3.13.1 is basically the same functionally, though it drops the `>=dev-qt/qtconcurrent-5.15.9:5` dep (which looks wrong, see bug 945694). The ebuild passes: -DFORCE_INTERNAL_QSCINTILLA=OFF -DFORCE_INTERNAL_QCUSTOMPLOT=OFF -DFORCE_INTERNAL_QHEXEDIT=OFF If you change those to ON, does it work?
I've recently filed my own issue with them on trying to port to Qt6: https://github.com/sqlitebrowser/sqlitebrowser/issues/3829 This is fatal in Qt6 but may also lead to unexpected issues in Qt5.
fwiw, I cannot reproduce that problem. All listed (un-)bundled deps only exist with a single version in ::gentoo right now, so should be the same on your system. app-editors/qhexedit2-0.8.9_p20210525-r3 dev-libs/qcustomplot-2.1.1 x11-libs/qscintilla-2.14.1-r1
Changing : -DFORCE_INTERNAL_QSCINTILLA=ON -DFORCE_INTERNAL_QCUSTOMPLOT=ON -DFORCE_INTERNAL_QHEXEDIT=ON Leads to: $ sqlitebrowser sqlitebrowser: error while loading shared libraries: libqscintilla2.so: cannot open shared object file: No such file or directory
Andreas, thanks for looking at it. Maybe it's a an issue specific to mate\gtk and QT. What desktop env. are you using?
Plasma 6. Maybe it is time you show us your emerge --info, should have been there from the beginning.
(In reply to OzTiram from comment #11) > $ sqlitebrowser > sqlitebrowser: error while loading shared libraries: libqscintilla2.so: > cannot open shared object file: No such file or directory I'm not sure how it's possible for you to get this, given it depends on those.
Created attachment 915666 [details] emerge --info
> I'm not sure how it's possible for you to get this, given it depends on those. Isn't it what I just told the ebuild with: -DFORCE_INTERNAL_QSCINTILLA=ON -DFORCE_INTERNAL_QCUSTOMPLOT=ON -DFORCE_INTERNAL_QHEXEDIT=ON I guess they are supposed to be bundled somehow, but they are not...
I did some more digging, and I was able to narrow the issue down to "it's only happening on mate desktop with nvidia". I have multiple gentoo machines running intel and they don't have this issue. On the desktop with nvidia card, this happens only on mate-desktop. Running xfce4 or plan X (with twm) the issue does not happen.
So... after a very long research an multiple gentoo installation it turns out it's really an issue with mate+nvidia, which is fixed by setting the correct font DPI. I commented on the upstream issue for those interested.
Thank you for following up.
