# PyGPlates Installation error on Ubuntu 20.04

**URL:** https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483
**Category:** Bug Reports
**Created:** [23 February 2022 10:29 UTC](https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483 "2022-02-23T10:29:04Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![john.cannon](https://discourse.gplates.org/letter_avatar_proxy/v4/letter/j/3e96dc/32.png) [@john.cannon](https://discourse.gplates.org/u/john.cannon)
#### Post date: [7 March 2022 04:47 UTC](https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483/12 "2022-03-07T04:47:29Z")

</div>

Thanks for sending the `CMakeCache.txt` file.

As we discussed offline just now, your initial seg fault is now fixed (the problem mentioned in [this post above](https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483/5): `libgdal.so.29: undefined symbol: opj_encoder_set_extra_options`). By compiling `pygplates` in conda, both `pygplates` and `pygmt` use the same version of GDAL (thus avoiding the conflict).

The problem you’re now having (mentioned in [this post](https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483/10)) is a different issue that’s covered in [this post](https://discourse.gplates.org/t/python-shell-segmentation-fault-after-exiting-when-importing-pygplates/487/2): it’s an issue with `pygplates` seg faulting _on exit_ when using version 3.9 of Python that I’m currently looking into.

So now you’re compiling pygplates in a Python _3.8_ (not 3.9) conda environment as a workaround.

---

_[View the full topic](https://discourse.gplates.org/t/pygplates-installation-error-on-ubuntu-20-04/483)._