Open Cobalt does not launch on Ubuntu 12.04

163 views
Skip to first unread message

Jake Nicholson

unread,
Jul 18, 2012, 5:47:31 PM7/18/12
to openc...@googlegroups.com
Hello, all. I am completely new to OC. I'm running Ubuntu 12.04 and after extracting the .zip file containing 1.0 alpha 20 and running the cobalt.sh file, nothing happens. I've read in the "Launching" section of the User Guide that upon doing this, Open Cobalt should either open the 3D environment directly, or should open a window with a blue ball in the corner. Neither of these scenarios happen. There aren't even any error messages that pop up that I could search for information on. I've also tried running the cobalt.sh file in the terminal, but all it seems to do is open a blank terminal window that closes very shortly afterwards (If there was an error, would the terminal stay open? [Are there any ways to get the terminal to stay open after the script has been run to look for errors or submit it to one of you who may be able to analyze it?]). All of my system specifications seem to be sufficient, according to the "System Requirements" section of the User Guide. The "log" folder (which I assume should contain valuable statistics) is completely empty. I've been browsing this group for about an hour now, searching for various combinations of different keywords, but no one else seems to have this same problem. I found into only one post regarding Ubuntu 12.04 in the Google Group (found here: https://groups.google.com/forum/?fromgroups#!searchin/opencobalt/12.04/opencobalt/9EdL3jEpv8g/qmwqP3-C7gUJ), but it seems to be addressing a problem with OpenAL, and not startus. In the Mantis Bug Database, I've located another post involving startup failure in Ubuntu (found here: http://croquet-src-01.oit.duke.edu/mantis/view.php?id=515), yet it looks like it supplies an error message, which I haven't received (as far as I know). I've also checked the "Troubleshooting" section of the User Guide, and it doesn't list my problem, either.

Could anyone point me in a direction of how I could go about fixing this? Am I missing something obvious?

Carlos Crosetti

unread,
Jul 18, 2012, 6:51:45 PM7/18/12
to openc...@googlegroups.com
Hi, just to want to let you know this is a known issue and a workaround exist to get you started, I am asking my colleagues using Linux to give the resolution path soon for you, as I cannot remember which configuration file needs to touched so far, please stay tuned, thanks, Carlos
--
You received this message because you are subscribed to the "Open Cobalt" Google group.
To post to this group, send email to openc...@googlegroups.com
To unsubscribe from this group, send email to
opencobalt+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/opencobalt?hl=en

Eric Gillespie

unread,
Jul 20, 2012, 3:30:01 AM7/20/12
to openc...@googlegroups.com
Yup. We know about it, I posted a fix to Mantis issue 515. I'll go check that the shell script is still relevant to Ubuntu 12.04's case. The only other question I need to ask you is: are you running the 64-bit version of Ubuntu?

Thanks for your reply, 

Regards from The Viking (Dr Smokey)

Eric Gillespie

unread,
Jul 20, 2012, 3:45:43 AM7/20/12
to openc...@googlegroups.com


On 20 July 2012 19:30, Eric Gillespie <brick...@gmail.com> wrote:
Yup. We know about it, I posted a fix to Mantis issue 515. I'll go check that the shell script is still relevant to Ubuntu 12.04's case. The only other question I need to ask you is: are you running the 64-bit version of Ubuntu?

Thanks for your reply, 

Regards from The Viking (Dr Smokey)


I forgot to mention, the reason I'm asking about 64-bit is because I'm attempting to get the library search path correct, as it differs for some 64-bit systems from the 32-bit system I normally use. At the moment, I've got a copy of 64-bit Fedora installed so I can take a look at the issue further. About the only other thing I have to then address is how Ubuntu 12.04 differs from Fedora 17.

Again, cheers from The Viking (Dr Smokey)

Jake Nicholson

unread,
Jul 20, 2012, 1:17:00 PM7/20/12
to openc...@googlegroups.com
When I use "uname -a" in the terminal, it gives me the result:

Linux jacob-p6710f 3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 athlon i386 GNU/Linux

I was told that the i386 means that I'm running 32 bit.

Jake Nicholson

unread,
Jul 20, 2012, 1:25:35 PM7/20/12
to openc...@googlegroups.com
Your fix worked perfectly. Thank you so much!

Eric Gillespie

unread,
Jul 20, 2012, 6:38:17 PM7/20/12
to openc...@googlegroups.com
On 21 July 2012 05:25, Jake Nicholson <zax...@gmail.com> wrote:
Your fix worked perfectly. Thank you so much!


I'm glad to hear it. The fix will be in the alpha21 release, I believe.

Cheers, The Viking (Dr Smokey)

Reply all
Reply to author
Forward
0 new messages