# Projucer 5.4.1 won't start on Ubuntu **URL:** \ **Category:** The Projucer\ **Created:** [January 11, 2019, 12:54pm UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228 "2019-01-11T12:54:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Jnv](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jnv/32/11862_2.png) [@Jnv](https://forum.juce.com/u/Jnv)\ **Post date:** [January 11, 2019, 12:54pm UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/1 "2019-01-11T12:54:36Z")
Upgrading from the latest JUCE 4 (which worked very fine) to the latest v5.4.1, I can’t make Projucer work on Ubuntu (16.04). Compiling is flawless, but when launching the executable, I get this: JUCE v5.4.1 JUCE Assertion failure in juce\_Displays.cpp:344 Segmentation fault (core dumped) I have no problem with Windows. I tested on master and develop, the result is the same. Thanks! ---
**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\ **Post date:** [January 11, 2019, 2:05pm UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/2 "2019-01-11T14:05:18Z")
That’s odd, I’m not seeing this on Ubuntu 18.04.1 and I don’t think it was present on my older installation of 16.04 either. Have you changed the display settings in Ubuntu at all? Can you post what the `node.display->totalArea` is for each of the `node`s in the `displayNodes` array? ---
**Author:** ![Jnv](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jnv/32/11862_2.png) [@Jnv](https://forum.juce.com/u/Jnv)\ **Post date:** [January 11, 2019, 2:34pm UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/3 "2019-01-11T14:34:13Z")
Thanks for the reply. I didn’t change anything in Ubuntu. And I can not tell you the totalArea because I use Clion and I have no Build for it… (I feel stupid, sorry). However, I downloaded JUCE, and the already compiled Projucer throws an error right from the start: version `CURL\_OPENSSL\_4’ not found (required by ./Projucer) Maybe the segfault comes from that? Anyway, that’s strange, because I have already installed the right library (libcurl4-openssl-dev). But the problem seems to come from my Linux set-up… Don’t bother too much. I’ll upgrade to 18.04 and it will probably correct the problem. ---
**Author:** ![Jnv](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jnv/32/11862_2.png) [@Jnv](https://forum.juce.com/u/Jnv)\ **Post date:** [January 11, 2019, 2:44pm UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/4 "2019-01-11T14:44:49Z")
Oh, it seems this is linked to this [problem](https://forum.juce.com/t/where-does-libcurl3-dependancy-come-from/27679/2). I’ll try to do something about it. ---
**Author:** ![Jnv](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jnv/32/11862_2.png) [@Jnv](https://forum.juce.com/u/Jnv)\ **Post date:** [January 12, 2019, 11:01am UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/5 "2019-01-12T11:01:19Z")
Ok, I’ve found a bug it seems. I’ve updated to Ubuntu 18.04 LTS, and the segfault is still here. I managed to investigate like you asked me to: In juce\_Displays.cpp, l332: I have 2 nodes, which have these data: node 1: 1920x1200, position 1280, 0 node 2: 1280x1024, position 0, 105 So none of these nodes satisfies the “getTopLeft() == Point\<\>()” condition. As a test, I removed the test, the first node is selected no matter what and the Projucer works! So maybe you should add a fallback if no node is found by the end of the loop? ---
**Author:** ![ed95](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/ed95/32/7635_2.png) [@ed95](https://forum.juce.com/u/ed95)\ **Post date:** [January 14, 2019, 9:25am UTC](https://forum.juce.com/t/projucer-5-4-1-wont-start-on-ubuntu/31228/6 "2019-01-14T09:25:36Z")
Interesting, I’ll put in a fallback for this. Thanks for reporting.