Bug 1389505 - could not find or load the Qt platform plugin "xcb" in ""
Summary: could not find or load the Qt platform plugin "xcb" in ""
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 18:27 UTC by Andreu Botella
Modified: 2019-10-23 02:33 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-18 12:22:48 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Andreu Botella 2016-10-27 18:27:22 UTC 
In Fedora 25 beta, on GNOME both on X11 and Wayland (at least as selected from gdm), all Qt applications fail to start. When run from the command line, they output this error message:


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

Available platform plugins are: custom-wayland, eglfs, linuxfb, minimal, minimalegl, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Reinstalling the application may fix this problem.
Aborted (core dumped)


This is on a two-days-old install of Fedora 25, using qt 4.8.7-18.fc25.

Steps to Reproduce:
1. Install any Qt application (I tried mscore, eric and RPMFusion's vlc).
2. On GNOME, run the application from the command line.
Comment 1 Than Ngo 2017-03-28 11:28:18 UTC 
i cannot reproduce this issue.
Comment 2 Than Ngo 2017-03-28 11:29:23 UTC 
does it work for you if you start it on KDE desktop?

thanks
Comment 3 Than Ngo 2017-07-18 12:22:48 UTC 
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.
Comment 4 Andreu Botella 2019-10-23 02:33:29 UTC 
.
Note You need to log in before you can comment on or make changes to this bug.