[GH-ISSUE #398] Cannot start barrier.exe, no Qt platform plugin #314

Closed
opened 2026-05-05 06:01:20 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @MichaelMcDonnell on GitHub (Aug 16, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/398

Operating Systems

Server: Windows 10 Version 1803 (OS build 17134.950)

Client: Windows 10 Version 1803 (OS build 17134.950)

Barrier Version

2.3.1-snapshot

Latest commit 58d8f02

Steps to reproduce bug

  1. Build on Windows with clean_build.bat
  2. Install Inno Setup from http://files.jrsoftware.org/is/5/innosetup-5.5.9.exe
  3. Build installer with build_installer.bat
  4. Double click on barrier\build\installer-inno\bin\BarrierSetup-2.3.1-snapshot.exe to install it
  5. Double click on the Barrier desktop icon
  6. Notice the error message:
    This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix the problem.

Other info

  • When did the problem start to occur? After I installed my own compiled version.
  • Is there a way to work around it? Probably if I manually copy the missing Qt files into the install loction.
  • Does this bug prevent you from using Barrier entirely? Yes
Originally created by @MichaelMcDonnell on GitHub (Aug 16, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/398 ### Operating Systems ### Server: Windows 10 Version 1803 (OS build 17134.950) Client: Windows 10 Version 1803 (OS build 17134.950) ### Barrier Version ### 2.3.1-snapshot Latest commit 58d8f02 ### Steps to reproduce bug ### 1. Build on Windows with clean_build.bat 2. Install Inno Setup from http://files.jrsoftware.org/is/5/innosetup-5.5.9.exe 2. Build installer with build_installer.bat 3. Double click on barrier\build\installer-inno\bin\BarrierSetup-2.3.1-snapshot.exe to install it 4. Double click on the Barrier desktop icon 5. Notice the error message: `This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix the problem.` ### Other info ### * When did the problem start to occur? After I installed my own compiled version. * Is there a way to work around it? Probably if I manually copy the missing Qt files into the install loction. * Does this bug prevent you from using Barrier entirely? Yes
gitea-mirror 2026-05-05 06:01:20 -06:00
Author
Owner

@AdrianKoshka commented on GitHub (Aug 16, 2019):

Can I ask why you're on 1803, just for science.

<!-- gh-comment-id:522125525 --> @AdrianKoshka commented on GitHub (Aug 16, 2019): Can I ask why you're on 1803, just for science.
Author
Owner

@noisyshape commented on GitHub (Aug 16, 2019):

Is the QT_PLUGIN_PATH environmental variable defined on your system? If so it's not supposed to be defined system-wide and that's likely the problem. If not, list the files that were installed to the program directory.

<!-- gh-comment-id:522131743 --> @noisyshape commented on GitHub (Aug 16, 2019): Is the QT_PLUGIN_PATH environmental variable defined on your system? If so it's not supposed to be defined system-wide and that's likely the problem. If not, list the files that were installed to the program directory.
Author
Owner

@AdrianKoshka commented on GitHub (Aug 16, 2019):

Fwiw, I installed barrier from the release tab in a windows sandbox and it just worked. I would've built it in the sandbox, but VS2019 can't be installed inside the sandbox and I don't feel like installing it on my host system, and I don't have a VM set up.

Update:

I compiled barrier from source on a windows 10 VM (1903), with visual studio community 2019, and QT 5.13.0, the installer was built with InnoSetup 6. The launch of barrier worked.

<!-- gh-comment-id:522156184 --> @AdrianKoshka commented on GitHub (Aug 16, 2019): Fwiw, I installed barrier from the release tab in a windows sandbox and it just worked. I would've built it in the sandbox, but VS2019 can't be installed inside the sandbox and I don't feel like installing it on my host system, and I don't have a VM set up. Update: I compiled barrier from source on a windows 10 VM (1903), with visual studio community 2019, and QT 5.13.0, the installer was built with InnoSetup 6. The launch of barrier worked.
Author
Owner

@MichaelMcDonnell commented on GitHub (Aug 17, 2019):

I'm away from that computer right now but I'll check soon. I just tried building on my other computer and it worked fine. The other computer with Visual Studio 2019, Qt 5.12.4 and InnoSetup 5.5.9 worked fine.

<!-- gh-comment-id:522259350 --> @MichaelMcDonnell commented on GitHub (Aug 17, 2019): I'm away from that computer right now but I'll check soon. I just tried building on my other computer and it worked fine. The other computer with Visual Studio 2019, Qt 5.12.4 and InnoSetup 5.5.9 worked fine.
Author
Owner

@MichaelMcDonnell commented on GitHub (Aug 19, 2019):

I figured out the problem. I had forgotten to change B_QT_VER to the version of Qt I had installed. That's why none of the Qt DLLs got installed.

I think it would be a good idea to fail the build if Qt cannot be found. I might look into that at some point.

<!-- gh-comment-id:522619587 --> @MichaelMcDonnell commented on GitHub (Aug 19, 2019): I figured out the problem. I had forgotten to change B_QT_VER to the version of Qt I had installed. That's why none of the Qt DLLs got installed. I think it would be a good idea to fail the build if Qt cannot be found. I might look into that at some point.
Author
Owner

@shymega commented on GitHub (Aug 19, 2019):

@MichaelMcDonnell You don't need to do that, I've added checks to CMakeLists.txt...see #404.

<!-- gh-comment-id:522645671 --> @shymega commented on GitHub (Aug 19, 2019): @MichaelMcDonnell You don't need to do that, I've added checks to CMakeLists.txt...see #404.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

I figured out the problem. I had forgotten to change B_QT_VER to the version of Qt I had installed. That's why none of the Qt DLLs got installed.

I assume this means we can close the issue. Please let me know if I misunderstood the problem, thanks.

<!-- gh-comment-id:757516869 --> @p12tic commented on GitHub (Jan 10, 2021): > I figured out the problem. I had forgotten to change B_QT_VER to the version of Qt I had installed. That's why none of the Qt DLLs got installed. I assume this means we can close the issue. Please let me know if I misunderstood the problem, thanks.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#314
No description provided.