# \[BUG\]Perspective Not Available on Linux Server?

**URL:** <https://forum.inductiveautomation.com/t/bug-perspective-not-available-on-linux-server/21780>\
**Category:** Ignition Early Access\
**Created:** [January 10, 2019, 2:20am UTC](https://forum.inductiveautomation.com/t/bug-perspective-not-available-on-linux-server/21780 "2019-01-10T02:20:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NorthPoint](https://avatars.discourse-cdn.com/v4/letter/n/a88e4f/32.png) [@NorthPoint](https://forum.inductiveautomation.com/u/NorthPoint)\
**Post date:** [January 10, 2019, 2:20am UTC](https://forum.inductiveautomation.com/t/bug-perspective-not-available-on-linux-server/21780/1 "2019-01-10T02:20:17Z")

</div>

I installed latest (1/9) on my Linux server, and Perspective does not appear in the tree at all, on existing or newly created projects. I rebooted the module, then the server, with no impact.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [January 10, 2019, 2:27am UTC](https://forum.inductiveautomation.com/t/bug-perspective-not-available-on-linux-server/21780/2 "2019-01-10T02:27:00Z")

</div>

Nothing to do with Linux, just a bug that'll be fixed this week.

> [@\[Bug-12013\] Perspective Missing in the Designer](http://forum.inductiveautomation.com/t/perspective-missing-in-the-designer/21743/4):
>
> This got fixed yesterday but I don’t know if the nightly build was successful.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [January 11, 2019, 7:33pm UTC](https://forum.inductiveautomation.com/t/bug-perspective-not-available-on-linux-server/21780/3 "2019-01-11T19:33:49Z")

</div>

This issue was fixed in the build that was uploaded today (1/11). Please let us know if you continue to see this behavior after upgrading.
