Bug 214340

Summary: devel/qt5: could not find or load the Qt platform plugin "xcb"
Product: Ports & Packages Reporter: Petr Fischer <petr.fischer>
Component: Individual Port(s)Assignee: freebsd-kde (Team) <kde>
Status: Closed FIXED    
Severity: Affects Some People CC: rff1917, w.schwarzenfeld
Priority: --- Flags: rakuco: maintainer-feedback+
Version: Latest   
Hardware: amd64   
OS: Any   

Description Petr Fischer 2016-11-09 00:08:24 UTC
In some apps (like virtualbox or vlc) this erro roccurs when starting app:

Qt FATAL: This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: minimal, offscreen, xcb.

Reinstalling the application may fix this problem.
Abort trap

Manually running "pkg upgrade -f qt5-gui" helps, but it is IMHO a problem/bug.

Look at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214339
Comment 1 Petr Fischer 2016-11-09 00:09:07 UTC
*** Bug 214339 has been marked as a duplicate of this bug. ***
Comment 2 Walter Schwarzenfeld freebsd_triage 2016-11-12 23:49:44 UTC
Same problem and solution with ports-mgmt/portrac.
I think there is something missing in the Makefile USE_QT5= gui does not help. Maybe any LIB_BEPENDS?
Comment 3 Tobias C. Berner freebsd_committer 2016-11-13 20:26:28 UTC
*** Bug 214474 has been marked as a duplicate of this bug. ***
Comment 4 rff1917 2016-11-13 20:59:38 UTC
This solution *kind of* worked.

"pkg upgrade" alone was not finding any upgrades since last time and the latest version I always got was "qt5-gui-5.6.2", which causes the problem.

So I had to manually download the "qt5-gui-5.6.2_1.txz" file from the servers and then "pkg add" it.

Even now, running "pkg upgrade -f qt5-gui" wants to downgrade the working 5.6.2_1 version and install version 5.6.2.
Comment 5 Raphael Kubo da Costa freebsd_committer 2016-11-22 10:28:29 UTC
I manually bumped PORTREVISION in qt5-gui in ports r425987 to trigger a rebuild (it's still unclear to me how the xcb part of qt5-gui depends on perl). The repository problems mentioned in comment #4 look unrelated to this specific issue.