# Skimage import error

**URL:** <https://discourse.slicer.org/t/skimage-import-error/19482>\
**Category:** Development\
**Created:** [September 2, 2021, 10:00am UTC](https://discourse.slicer.org/t/skimage-import-error/19482 "2021-09-02T10:00:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shatz](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@shatz](https://discourse.slicer.org/u/shatz)\
**Post date:** [September 2, 2021, 10:00am UTC](https://discourse.slicer.org/t/skimage-import-error/19482/1 "2021-09-02T10:00:24Z")

</div>

When importing the `io` module from skimage, I get this error: `ImportError: /projects/msieve_dev3/usr/shats/apps/Slicer-4.11.20210226-linux-amd64/lib/Python/lib/python3.6/site-packages/PIL/_imaging.cpython-36m-x86_64-linux-gnu.so: ELF load command address/offset not properly aligned`. The other modules ive used work fine.

Ive tried to pip\_uninstall and then reinstall scikit-image, to no avail. Seems like some people on the internet get this error in different situations when the “[strip](https://en.wikipedia.org/wiki/Strip_(Unix))” program, so I wonder if slicer is using that internally.

In any case, does anyone have a fix for this?

OS: Linux  
Slicer Version: 4.11.20210226

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 2, 2021, 11:57pm UTC](https://discourse.slicer.org/t/skimage-import-error/19482/2 "2021-09-02T23:57:21Z")

</div>

Information in this issue may help: [https://github.com/Slicer/Slicer/issues/5474](https://github.com/Slicer/Slicer/issues/5474)

---

<div class="post-metadata">

**Author:** ![shatz](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@shatz](https://discourse.slicer.org/u/shatz)\
**Post date:** [September 4, 2021, 7:40pm UTC](https://discourse.slicer.org/t/skimage-import-error/19482/3 "2021-09-04T19:40:19Z")

</div>

Thanks! apparently this was fixed on Mar 13 but the build I downloaded was only a few weeks before the fix was released!