# Slicer 4.10 not starting after fresh build

**URL:** https://discourse.slicer.org/t/slicer-4-10-not-starting-after-fresh-build/4558
**Category:** Development
**Created:** [October 27, 2018, 8:32pm UTC](https://discourse.slicer.org/t/slicer-4-10-not-starting-after-fresh-build/4558 "2018-10-27T20:32:10Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [October 28, 2018, 4:24pm UTC](https://discourse.slicer.org/t/slicer-4-10-not-starting-after-fresh-build/4558/3 "2018-10-28T16:24:44Z")

</div>

> [@christian](#):
>
> Py\_Initialize: Unable to get the locale encoding

This error reported to occur when Slicer’s embeded Python environment is mixed with some other Python environments. See this post for details: [python-real different from python interpreter - #2 by jcfr](https://discourse.slicer.org/t/python-real-different-from-python-interpreter/2496/2). @pieper’s suggestion above should fix the gdb launching issue and then hopefully you can find the root cause of the crash.

---

_[View the full topic](https://discourse.slicer.org/t/slicer-4-10-not-starting-after-fresh-build/4558)._