Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
3
Found in
2018.3.0a1
Issue ID
1047075
Regression
Yes
Linux executable doesn't launch and has incorrect icon.
Linux executable doesn't launch and has incorrect icon
Steps to Reproduce:
1. Create a new project
2. Change "Target Platform" as a Linux
3. Set architecture as "x86 + x86_64(Universal)"
4. Build project
5. Transfer executable file on Linux machine
Actual result:
Executable doesn't run and shows incorrect icon
Reproducible on:
2018.3.0a3, 2018.3.0a2, 2018.3.0a1
Working Fine on:
2018.2.0b7, 2018.2.0b9
Environment:
Build made on Windows (10) for Linux
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- RenderParam.renderPriority is ignored when rendering Mesh with Graphics.RenderMesh()
- Multipage Sprite Atlas renders incorrectly when Secondary Textures are used
- Changes to the Terrain Prefab are reflected on the unrelated Terrain GameObject in a Scene when sculpting it using Brushes
- Data is not serialized correctly on time when OnValidate is used to retrieve the data
- The mouse cursor is positioned in the center when Cursor.LockState is set to CursorLockMode.Confined and changing the mouse position
jwvanderbeck
Oct 25, 2018 17:03
Why not make PIE an option when building? Not every game is going to care about the extra security.
syscrusher
Oct 11, 2018 15:19
Question: Is this only applicable to the universal binaries, or would it also affect a specific 32-bit or 64-bit build? I ask because I do independent builds for 32 and 64 bit most of the time. Thanks.
FROS7
Sep 28, 2018 00:50
@pjayb Has the issue been raised with the Gnome community??
PJayB
Sep 25, 2018 15:47
Unfortunately, this is an issue caused by Nautilus' ("Files") lack of support for position-independent executables, i.e. double-click and icon support is not available for PIE binaries. Running from the command line still works. Unfortunately, fixing this is up to the GNOME community and is out of Unity's control. However, we are considering ways to make this less painful/confusing for our users.