But I could imagine other programs not being as robust to that sort of thing (running GUI apps with sudo was always a big no-no for a similar reason - fairly important files in your home directory would end up owned by root) and causing breakage like what you've seen.Īs you said, not enough info to clearly pinpoint the specifics of what went wrong, but I'm with you on this sort of thing being a potential issue! Online RPCS3 Forums > Support & Issues > Support > could not find or load the Qt platform plugin. Reinstalling the application may fix this problem.
This application failed to start because no Qt platform plugin could be initialized. pyc files, python just ignores them if it can't read them. Qt platform plug-in could not be initialized when trying to run the, RPCS3 is an open-source Sony PlayStation 3 emulator and debugger which currently supports Windows, Linux and BSD systems. (base) duxonpenguin: flatpak run qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin 'xcb' in '' even though it was found.
To Fix No Qt Platform Plugin Could Be Initialized Error or This Application. The app might not be clever enough to figure this out, and crash when subsequently run as a regular user. plugin: Could not load the Qt platform plugin xcb in even though it was. You can check if this is your problem too by running the following command in your Python script: import os print(os.environQTQPAPLATFORMPLUGINPATH) If those commands do not give you a file path you most likely have the same problem. This had no ill effects other than the files being untracked by pacman, but I can imagine a situation where if you run an app as root, additional files not originally in the package will be created, and since they are owned by root, won't be readable by regular users. I fixed it by explicitly setting the QTQPAPLATFORMPLUGINPATH environment variable. plugin: Could not load the Qt platform plugin windows. pyc files owned by root would be generated. failed to start because no Qt platform plugin could be initialized. There was a problem with the pyqt packages a while ago where if you ran a pyqt application as root.