[SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

Eraph · 2016-05-28 02:49:15

I'm trying to simplify my system and I was hoping to get rid of the XFCE4 AppFinder. As nice as it is, I want to get the hang of the more pure Bunsen experience - using the desktop menu and dmenu, and so on. The problem I have is this: I have installed Unity3D, the game development studio using the .deb file downloaded from their forums. The application opens up perfectly through AppFinder, presumably using the Desktop Configuration file I put into /user/share/applications:

[Desktop Entry]
Version=5.3.4f1
Name=Unity
Exec=/opt/Unity/Editor/Unity %F
Exec=/opt/Unity/Editor/Unity %U
Icon=unity-editor-icon
Terminal=false
Type=Application
StartupNotify=true
Categories=Utility;Application;
MimeType=x-scheme-handler/com.unity3d.kharma;

Now, It wouldn't open in Terminal or dmenu because of its odd path, which I've since added to the end of ~/.xsessionrc (as I quickly found out that ~/.profile was not the correct place for it):

PATH="$PATH:/opt/Unity/Editor"

After adding this I logged out and logged back in again, and I can see Unity appear in the suggestions of dmenu, and I no longer get an error when I attempt to open it from Terminal. However, it doesn't open. There is no indication that the task is running in the foreground or background, no messages given, nothing. Any idea how I can diagnose this?

Last edited by Eraph (2016-05-28 22:22:47)

damo · 2016-05-28 06:17:38

Exec=/opt/Unity/Editor/Unity %F

Seems that the command is expecting a parameter to be passed to it. Is it a config file of some kind?

Eraph · 2016-05-28 07:57:46

Well I tried altering the .desktop file, removing the parameters (and the second, almost identical Exec line) and it still runs from AppFinder so I don't think the parameters have anything to do with it.

Head_on_a_Stick · 2016-05-28 09:34:38

What happens if you run the command from a terminal:

/opt/Unity/Editor/Unity

Are there any error messages or other output?

Disclaimer: I've never tried Unity.

I use script wrappers with dmenu, eg:

# /usr/local/bin/unity
#!/bin/sh
exec /opt/Unity/Editor/Unity

/usr/local/bin/unity needs to be executable, I do this with Steam games taking the "Exec=" line from the supplied .desktop file.

xaos52 · 2016-05-28 10:29:46

I installed unity out of curiosity.
Apparently you need to run it by specifying the full path:
/opt/Unity/Editor/Unity

If you launch it from the terminal as
Unity
It finished immediately and logsa message to $HOME/.config/unity3d/editor.log containing:

mono profile = '/home/me/Data/Mono/lib/mono/2.0'
Unable to load mono library from /home/me/Data/MonoEmbedRuntime (x86_64)
Failed to load mono, aborting

I have no inclination to dig into the documentation of unity to find a cure for that.

Conclusion:
It is a Unity idiosyncrasy.

Eraph · 2016-05-28 12:36:34

Head_on_a_Stick wrote:

What happens if you run the command from a terminal:
/opt/Unity/Editor/Unity

Interesting! That does work. So I've reconfigured OpenBox to use that and it works. Terminal I'm not so fussed about, but any clues as to how I could get it to work from dmenu, without entering the full path?

damo · 2016-05-28 16:20:07

Eraph wrote:

Head_on_a_Stick wrote:
What happens if you run the command from a terminal:
/opt/Unity/Editor/Unity
Interesting! That does work. So I've reconfigured OpenBox to use that and it works. Terminal I'm not so fussed about, but any clues as to how I could get it to work from dmenu, without entering the full path?

Maybe try putting a symlink called 'Unity' in /usr/bin, pointing to '/opt/Unity/Editor/Unity'.

Head_on_a_Stick · 2016-05-28 16:27:32

Eraph wrote:

any clues as to how I could get it to work from dmenu, without entering the full path?

Yes, as I said:

I wrote:

I use script wrappers with dmenu, eg:
# /usr/local/bin/unity
#!/bin/sh
exec /opt/Unity/Editor/Unity
/usr/local/bin/unity needs to be executable, I do this with Steam games taking the "Exec=" line from the supplied .desktop file.

So just create a file at ~/bin/unity with the content I posted and then run:

chmod +x ~/bin/unity

Then "unity" should show up in dmenu and launch correctly (remove the added PATH first, ~/bin is sourced first in BL by default).

Eraph · 2016-05-28 22:22:27

Head_on_a_Stick wrote:

Eraph wrote:
any clues as to how I could get it to work from dmenu, without entering the full path?
Yes, as I said:
I wrote:
I use script wrappers with dmenu, eg:
# /usr/local/bin/unity
#!/bin/sh
exec /opt/Unity/Editor/Unity
/usr/local/bin/unity needs to be executable, I do this with Steam games taking the "Exec=" line from the supplied .desktop file.
So just create a file at ~/bin/unity with the content I posted and then run:
chmod +x ~/bin/unity
Then "unity" should show up in dmenu and launch correctly (remove the added PATH first, ~/bin is sourced first in BL by default).

Oops, I total fluffed over that bit

It works a treat! Thanks for your help, everyone!

#1 2016-05-28 02:49:15

[SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#2 2016-05-28 06:17:38

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#3 2016-05-28 07:57:46

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#4 2016-05-28 09:34:38

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#5 2016-05-28 10:29:46

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#6 2016-05-28 12:36:34

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#7 2016-05-28 16:20:07

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#8 2016-05-28 16:27:32

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

#9 2016-05-28 22:22:27

Re: [SOLVED] Unity3D won't open from OpenBox menu, Terminal or dmenu

Board footer