IMDTouchKnowledge BaseShop main store

Troubleshooting

Fix the libQt5WebEngine.so.5 error when an HMI editor will not start

HMI and touchscreens Published 6 min read

Short answer

The message means the dynamic loader cannot resolve one shared library the editor binary needs, so startup fails before any editor code runs. Run a dependency report on the exact failing binary, install your distribution's Qt 5 WebEngine runtime package that provides libQt5WebEngine.so.5, and relaunch only when the report shows no unresolved libraries. Do not symlink or rename another library to match the name.

On this page
  1. What the loader message actually says
  2. Confirm which binary is failing
  3. Install the runtime package that provides the library
  4. Worked example: pvdevelop at /opt/pvb/pvdevelop/pvdevelop on x86-64 Linux
  5. When the library file exists but the error stays
  6. After the editor starts
  7. Questions asked

Your editor did not crash — it never started. The line /opt/pvb/pvdevelop/pvdevelop: error while loading shared libraries: libQt5WebEngine.so.5: cannot open shared object file: No such file or directory is the Linux dynamic loader reporting that it cannot open one Qt 5 shared library the binary needs, so the process exits before any editor code runs. The fix is a package fix, not a project fix: inspect the exact binary named in the message, install your distribution's Qt 5 WebEngine runtime package, and relaunch only when a dependency report on that binary shows zero unresolved libraries. Renaming or symlinking a different library to match the name fixes nothing, because a matching filename alone proves nothing.

What the loader message actually says #

The message carries three facts: the failing binary is the one at /opt/pvb/pvdevelop/pvdevelop, the library it asked for is libQt5WebEngine.so.5, and the loader found no usable file under that name. pvdevelop is the screen-development environment of the open-source pvbrowser project, and the failure reported in its 4.5.6 release thread is an installation fault, not a bug in your screens.

Before the first line of application code runs, the loader must open every shared library listed in the executable's dependency table. One of four conditions produces this exact message:

  • The Qt 5 WebEngine runtime package is not installed on this machine at all.
  • A file with that name exists but was built for a different architecture, so a 64-bit executable cannot load it.
  • The name resolves to a dangling symbolic link or a leftover file from a partial update.
  • The file exists but sits in a directory the loader does not search.

The message names only the first library that failed. Others can be missing behind it, which is why you inspect the whole dependency table rather than fixing one name per launch.

Confirm which binary is failing #

Work on the binary the loader named, not on a copy selected by a desktop shortcut or a search path.

  • Launch the editor from a terminal and keep the complete startup output.
  • Compare the path in the error with the path your launcher actually runs; an old shortcut can point at a different installation while the runtime files belong to a newer one.
  • Run the dependency report on the exact path: ldd /opt/pvb/pvdevelop/pvdevelop. The tool prints every library the binary needs, each with the full path it resolved to, or not found where it resolved to nothing.
  • Record every not found line, not only libQt5WebEngine.so.5.
  • If a file with the missing name exists on disk, ask the package manager which package owns it, and check whether it is a real file or a link whose target is gone.

The checkpoint is a dependency report tied to the exact failing binary, with every unresolved name listed. That gives the package repair a defined target.

Install the runtime package that provides the library #

Take pvbrowser and pvdevelop from the project's own release channel, and take operating-system libraries from your distribution's repositories — nothing else. On a machine that runs a plant, a library package from an unverified source is an intrusion path, not a shortcut.

  • Identify your distribution's Qt 5 WebEngine runtime package. On Arch Linux it is qt5-webengine; a documented build is 5.15.19-4.3 for x86_64. Package names differ on other distributions, so search your repository for the provider of libQt5WebEngine.so.5.
  • Install that package with the package manager so its declared dependencies arrive with it. WebEngine is not one file; it carries its own dependency chain.
  • Rerun the dependency report. The pass condition is zero not found lines.
  • If the report now names a different libQt5*.so.5, that library has its own runtime package — repeat once per name, then recount.

Do not rename an unrelated library to the missing name, do not point a link at a different Qt generation, and do not copy the file from another computer. None of those produces binary compatibility, and each hides the real owner of the file from the package manager.

Worked example: pvdevelop at /opt/pvb/pvdevelop/pvdevelop on x86-64 Linux #

Inputs. The failing binary path /opt/pvb/pvdevelop/pvdevelop and the missing soname libQt5WebEngine.so.5 both come from the reported startup message. The host class is x86-64 Linux. The documented provider is the distribution package qt5-webengine, build 5.15.19-4.3, architecture x86_64.

Rule. The loader opens every soname in the executable's dependency table before the program starts. The repair passes only when the dependency report on this exact binary prints no not found line, and the installed library matches the executable in Qt major version and in architecture.

Arithmetic.

  • Requested ABI: the digit after .so in libQt5WebEngine.so.5 is 5.
  • Provider Qt version: 5.15.19, so major version 5. Since 5 = 5, this package generation satisfies the soname.
  • Provider architecture: x86_64; executable class: x86-64. The pair matches.
  • Unresolved lines before repair: at least 1, because the loader printed a name. The pass threshold is 0, and 1 > 0, so the install step is required, not optional.
  • Required count after install: 0. When the recount reads 0, then 0 = 0 and the binary may launch.

Result. With the distribution's Qt 5 WebEngine runtime installed, the dependency report resolves libQt5WebEngine.so.5 to a real file in the package's library directory, and the not found count on the report is 0.

Decision. At 0 unresolved lines, relaunch pvdevelop from a terminal; a clean start with no loader message is the pass. Any count above 0 names the next library, and the same one-package-per-name repair applies. If your distribution release ships no Qt 5 WebEngine runtime at all, move the installation to a supported release rather than copying the file by hand.

When the library file exists but the error stays #

A valid runtime can still be invisible to the loader. Work through this list before concluding the package is wrong:

  • Resolve the symbolic link for libQt5WebEngine.so.5 and confirm the final target exists as a real, non-empty file.
  • Check that the account launching the editor can read the file and traverse every directory in its path.
  • Compare a terminal launch with the desktop launcher: the two can see different library search paths. If the packaged launcher sets its own search path, launch through it.
  • After adding libraries outside the standard tree, refresh the loader's cache with the command your distribution documents.
  • Retest under the account and the launcher developers will actually use, not only from an administrator shell.

After the editor starts #

A clean launch clears the installation fault and nothing else. If the project itself then fails to open, that is a project-level fault with its own recovery and backup steps for an HMI project, not another loader problem. And until the binary starts, leave the PLC, the tags and the communication settings alone: this process died before any communication was attempted, so no amount of comms troubleshooting changes the message.

Questions asked

Can I copy libQt5WebEngine.so.5 from another computer that has it?

No. A matching filename proves nothing: the copy can come from a different Qt build, a different architecture, or carry its own unresolved dependencies. It also leaves the file outside your package inventory, so a later system update can remove or break it silently. Install the runtime package from your distribution's repositories instead.

Why does the error name only one library when more could be missing?

The loader stops at the first library it cannot open and reports that one name; it does not continue to list the rest. A dependency report on the binary lists every unresolved library in a single pass, which is why the report drives the repair instead of repeated launches. Fix every name the report shows before relaunching.

Will installing a Qt development package fix the startup error?

No. Development packages supply headers and build tools for compiling software; the loader opens the runtime library that a runtime package installs. Installing development tools proves nothing about whether the editor will start. Install the runtime package first, then run the dependency report again and count the unresolved lines.

Can a symbolic link to a newer Qt WebEngine library work instead?

No. The 5 at the end of libQt5WebEngine.so.5 is the major ABI version the binary was linked against, and a library from another major version is not binary compatible with it. A renamed or relinked file either fails at load or breaks later at runtime. Only a matching Qt 5 WebEngine runtime satisfies the soname.

Keep reading

  • Troubleshooting

    Why a standalone HMI project will not open in your integrated editor

    A standalone Vijeo Designer .vdz archive usually fails in an integrated editor because the two editors sit at different version levels and accept different project operations, not because a license is missing. Open the copy through the destination editor's documented import or restore route, with the destination editor at the same version level or newer than the editor that saved the archive, then verify target and communication settings.

    HMI and touchscreens

  • Selection guide

    How to Select Lightweight HMI Software for Modbus I/O Control

    Select on three gates in order: a driver that speaks Modbus RTU (and Modbus TCP if the LAN path is required), a tag license at least 20 percent above your counted total, and a runtime that runs the exported project on a clean PC. A 56-device floor plan counts 154 tags, so a 150-tag edition already fails. Prove one floor plan, one popup, one live indicator and one write before you pay.

    HMI and touchscreens

  • Selection guide

    How to Choose HMI Software for a New Control System

    Count operator stations, controllers and connections first, keep sequencing and permissives in the PLC, and pick the smallest architecture that meets the full requirement. One station with no logging duties takes a dedicated panel; multiple stations needing simultaneous control or sustained history take a PC-based runtime.

    HMI and touchscreens

Why WinCC Unified simulation will not open in a browser