gnuplot: Why does gnuplot_qt fail to start on some PCs?

install gnuplot ubuntu
gnuplot examples
gnuplot tutorial
gnuplot download
gnuplot chart types
gnuplot plot
gnuplot linux

I have a gnuplot script which works fine on Win7 and Win10 PCs.

set term wxt size 400,400

However, if I switch to qt terminal it works fine on some PCs, but on others I get error messages.

set term qt size 400,400

The error message suggests to reinstall the application? Which application? Which Qt platform plugin? I am working with gnuplot 5.2.6 and simply unpacked gnuplot from the file gp526-win64-mingw.7z from

What exactly do I have to reinstall to get it working everywhere?

Addition: Some more findings.

On those PCs where the qt-terminals didn't work, I was running gnuplot 5.2.6, however, the qt-terminals worked with gnuplot 5.2.0 on the same PCs. Going back to gnuplot 5.2.0 is not a solution because it doesn't have some features which I need. Some differences of the "working" and "non-working" PCs were the Microsoft Visual C++ Redistributables. Some PCs have the 2008,2010,2012,2013 and 2015 versions installed. On the newest Win10 PCs there is even a 2017 version but no 2015 version. So, my current suspicion is that gnuplot 5.2.6 requires the 2015 version, whereas gnuplot 5.2.0 probably runs with the 2013 version. If it is like this, it would have been nice if gnuplot_qt.exe told me that this or that specific version is missing.

Currently, I don't have access to those PCs. So, further tests will take some more time.

I have never used gnuplot, however, I have recently debugged issues with Qt plugins. From the popup it is clear that the platform plugin has been found (windows), but could not be initialized.

It might just be that the plugin DLL is somehow corrupt, or that multiple versions of Qt are available on the machine, and for some reason version A tries to load plugins from version B (and fails).

The part of Qt that loads plugins has some debug output built in. I suggest you try to enable debug output and get more information about the error:

  1. Get DebugView
  2. Enable plugins debug output. This can be done by setting an environment variable: SET QT_DEBUG_PLUGINS=1
  3. Start DebugView
  4. Start gnuplot from the command line where you set the variable
  5. Look for messages from gnuplot in DebugView. There might be some noise depending on what else is running in the system. DebugView collects output from all applications, but you can easily filter and search.

Debug messages should at least show exact paths to plugins that are being loaded. Most likely some additional information about the error will be shown too.

Gnuplot: INSTALL, configure --help 152 153 Some options relevant to gnuplot are listed below: 154 configure may fail to find lua support if the package configuration tool is 199 configure as shown below: 201 202 ln -s /usr/lib/pkgconfig/lua5.3.pc 502 line shell to be used for executing commands and starting sub-shells. brew uninstall gnuplot brew install gnuplot --with-x11 The first command uninstall a previous gnuplot installed with homebrew. The second command installs gnuplot by specifying the x11 terminal. This way, opening gnuplot sets the terminal automatically to x11, and the warning messages about "gnuplot_qt" and "slow font initialization" disappeared!

It's difficult to say without minimal code. But it looks like you didn't correctly deploy your application. 1) you should use windeployqt tool to create redistributable build. 2) you need to configure your app correctly with config: qt.conf. Ask if you need more help.

P.S. I got very difficult bug, when I got installed qt and redistributable qt on one PC. I found an answer here.

[PDF] Gnuplot 5.2, A short self-contained script demonstrating the problem is often helpful. To launch an interactive session after an initialization file "header" and followed by In earlier versions of gnuplot, some terminal types used the values from set size to The emxvga and emxvesa terminal drivers support PCs with SVGA, VESA. I use Ubuntu 16.04 LTS and gnuplot-qt. The following command does not exactly maximize the plot window but leaves it as large as possible. Use the following command for your terminal (in my case qt) specifying the maximum screen size (in my case 959, 650). The terminal type appears when the gnuplot is initialized. set terminal qt size 959, 650

I run in a similar problems few months ago with another software that was using Qt on Windows.

I do not have a final solution for your problem but those are some of the steps I followed to fix the problem.

1. Ensure you have a clean windows

In order to ensure that your configuration will run in all Windows version, try to setup a clean installation with no third-party dependency installed.

Sometimes, you will find that you have installed several packages in the past that makes your system compatible with the software you are running. In order to avoid that, try to install a clean version if you are planning to release an installation or setup that must run in different PCs.

Extract the folder an try to run it. If it does not run, try to install Qt and add it to the system path.

2. Find missing dependencies

I used DependencyWalker to find the missing dlls, if any in my system.

Create a new folder and extract the files you just downloaded. Open with DepencyWalker the binaries you are going to run.

This software will tell you if you need to install any third-party library that is missing in your system (download them for MinGw from this page).

Normally, you should add all those dlls into the 'bin/' folder.

Be aware that some of the dlls may be installed in one system and not in others because of the different Windows version they are using.

If DependencyWalker is not complaining anymore, zip the folder and try to run it in other systems.

3. Deploy for an installed Qt version

Qt provides a tool to copy all the dependencies from Qt that a binary need to run properly.

The Windows deployment tool windeployqt is designed to automate the process of creating a deployable folder containing the Qt-related dependencies (libraries, QML imports, plugins, and translations) required to run the application from that folder. It creates a sandbox for Windows Runtime or an installation tree for Windows desktop applications, which can be easily bundled into an installation package.

After installing Qt, try to run this tool in all the binaries to replace/updates the Qt dependencies in order to fix the problems with the Qt plugins.

Part I Gnuplot, although there are some subtle differences (see syntax (p. 101) for The new gnuplot user should begin by reading about plotting (if on-line, type help plotting). A small script demonstrating the problem may be useful. On the IBM PC, the use of a TSR program such as DOSEDIT or CED may be desired for line editing. In OS X Yosemite 10.10.2 and El Capitan 10.11.2, the Gnuplot does not package with XQuartz. Answer in bibstha's comment. Much more robust window manager is in qt and it works. brew uninstall gnuplot brew install gnuplot --with-qt Note that using --qt is deprecated now.

gnuplot / Bugs / #1554 multiplot freeze/crash with qt terminal, If you then type a plot command, it will open up a new plot window and Maybe it would be clearer to say "gnuplot_qt exiting on read failure". Gnuplot is a portable command-line driven graphing utility for linux, OS/2, MS Windows, OSX, VMS, and many other platforms. Use this tag for questions about programmatic use of Gnuplot; debugging interactive usage is off-topic.

Terminal set to "unknown" in gnuplot 5.2.6, Before this gnuplot version, there was gnuplot-5.2.2 in my PC and 'qt' is the default version of terminal. Can you please suggest me some terminal type using which I can do ploting install gnuplot-qt', but event after all these my gnuplot is After this restart my PC and since then this problem is comming. Some PDF files that have not been created using Adobe products may not be compatible with Acrobat or Reader. It is possible that these files do not meet Adobe specifications or standards. However, it is worth noting that older versions of Adobe Reader or Acrobat are not as strict as the recent versions when it comes to standards compliance.

Complete list of terminals, Plot windows remain open even when the gnuplot driver is changed to a different device. Note that some backend/terminal/font combinations might not support some (I do not know if that is a general problem with the tpic specials, or if it is The emxvga and emxvesa terminal drivers support PCs with SVGA, VESA� I encounter a very strange problem when using gnuplottex on my Win 7 32 bit system with MiKTeX 2.9 - gnuplot 4.6.3 & the latest gnuplottex release: \documentclass[dvips]{minimal} ewcommand{

  • I haven't had yet enough time to investigate the topic further. The issue is not yet solved. But now the StackOverflow automatic system is chyvvying me and tells me: "bounty expired - answer auto-selected". Well, you deserve it. DebugView looks like a useful tool.
  • Thank you for your answer. I will check your suggestion. This might take a while.
  • Thank you for your answer. I will check and try the options. This may take a while.
  • Imo, useless answer. 1) Can you explain, what "similar problem" did you solved with "clean windows"? Qt doesn't depend on anything, except correct CRT. Which is very easy to detect. So this step is useless. 2) If Qt application shows any message box then problem couldn't be solved with DependencyWalker, because DependencyWalker shows only compile-time linked libraries (both lib and dll). This step is useless too. 3) Application should be compiled with same major vesion of Qt. It doesn't depend on Qt installation at all, so replacement of dll won't fix this issue.
  • @DmitrySazonov: DependencyWalker can show also run-time issues, if you use "Profile"