# ParaView v5.9 lib issue - can't open GUI

**URL:** https://discourse.paraview.org/t/paraview-v5-9-lib-issue-cant-open-gui/6509
**Category:** ParaView Support
**Created:** [February 19, 2021, 9:00pm UTC](https://discourse.paraview.org/t/paraview-v5-9-lib-issue-cant-open-gui/6509 "2021-02-19T21:00:21Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![n0xn4me](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/n/b487fb/32.png) [@n0xn4me](https://discourse.paraview.org/u/n0xn4me)
#### Post date: [February 19, 2021, 9:00pm UTC](https://discourse.paraview.org/t/paraview-v5-9-lib-issue-cant-open-gui/6509/1 "2021-02-19T21:00:21Z")

</div>

This happens when I try to open ParaView (happens if I use **bin/paraview** and **bin/paraview-real** ):

host% /app/paraview/v5.9/ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit/bin/paraview  
/app/paraview/v5.9/ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit/bin/paraview-real: /usr/lib64/libz.so.1: version `ZLIB\_1.2.9’ not found (required by /app/paraview/v5.9/ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit/bin/…/lib/libpng16.so.16)

If I run ParaView using the **–mesa &** option I get:

host% qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.  
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

error: exception occurred: Child aborted

[1] Exit 1 /app/paraview/v5.9/ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit/bin/paraview --mesa

I’ve seen a few other similar posts that are a few years old, but no resolutions. Any ideas?

Thank you.

---

<div class="post-metadata">

### Author: ![proxy](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/e19b73/32.png) [@proxy](https://discourse.paraview.org/u/proxy)
#### Post date: [October 17, 2021, 11:37am UTC](https://discourse.paraview.org/t/paraview-v5-9-lib-issue-cant-open-gui/6509/2 "2021-10-17T11:37:08Z")

</div>

Hello,  
I am also facing the same issue. Were you been able to resolve this issue?
