So, Proteus stopped working on Mac OSx

[Corpo Sloppants]

Am I doing something wrong here? I installed the most recent update for both my mac, and steam. Then I went to launch it keeps failing to launch.

[LUBA]

same Problem :/

[Monomyth]

B-Man님이 먼저 게시:

Stupid Apple releasing "groundbreaking" updates that make giant handfuls of applications unusable

That's how tech works. If backwards compatability is all you care about, you get the same Windows OS for twenty years.

Apple can't be held responsible for every single OS X app ever written.

[Sewas Knight]

Mismo problema:

Process: Proteus [1111]
Path: /Users/seb/Library/Application Support/Steam/SteamApps/common/Proteus/Proteus.app/Contents/Resources/bin/Proteus.app/Contents/MacOS/Proteus
Identifier: com.yourcompany.proteus
Version: 1.0 (1)
Code Type: X86 (Native)
Parent Process: ??? [1]

Date/Time: 2014-01-07 12:56:52.406 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Interval Since Last Report: 3734199 sec
Crashes Since Last Report: 14
Per-App Interval Since Last Report: 1 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: C2A3F8E01932

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x97059c5a __kill + 10
1 libSystem.B.dylib 0x97059c4c kill$UNIX2003 + 32
2 libSystem.B.dylib 0x970ec5a5 raise + 26
3 libSystem.B.dylib 0x971026e4 abort + 93
4 com.yourcompany.proteus 0x000b9510 mono_handle_native_sigsegv + 592
5 com.yourcompany.proteus 0x00057765 mono_arch_handle_altstack_exception + 149
6 com.yourcompany.proteus 0x000e58c1 mono_sigsegv_signal_handler + 369
7 libSystem.B.dylib 0x9705f05b _sigtramp + 43
8 ??? 0xffffffff 0 + 4294967295
9 ??? 0x017a5100 0 + 24793344
10 ??? 0x013f5d16 0 + 20929814
11 ??? 0x013f5958 0 + 20928856
12 ??? 0x013f56dc 0 + 20928220
13 com.yourcompany.proteus 0x000ef48e mono_jit_runtime_invoke + 798
14 com.yourcompany.proteus 0x0019b44e mono_runtime_invoke + 126
15 com.yourcompany.proteus 0x0019b5bc mono_runtime_delegate_invoke + 140
16 com.yourcompany.proteus 0x001a1331 call_unhandled_exception_delegate + 481
17 com.yourcompany.proteus 0x001a154b mono_unhandled_exception + 203
18 com.yourcompany.proteus 0x000b9f90 mono_handle_exception_internal + 1744
19 com.yourcompany.proteus 0x000baa69 mono_handle_exception + 41
20 com.yourcompany.proteus 0x0005877d mono_x86_throw_exception + 285
21 ??? 0x004d9f67 0 + 5087079
22 com.yourcompany.proteus 0x000c881c common_call_trampoline + 1052
23 com.yourcompany.proteus 0x000c597b mono_magic_trampoline + 59
24 ??? 0x004d903e 0 + 5083198
25 ??? 0x013f2a4c 0 + 20916812
26 ??? 0x00747b18 0 + 7633688
27 ??? 0x0073898c 0 + 7571852
28 ??? 0x00738abb 0 + 7572155
29 com.yourcompany.proteus 0x000ef48e mono_jit_runtime_invoke + 798
30 com.yourcompany.proteus 0x0019b44e mono_runtime_invoke + 126
31 com.yourcompany.proteus 0x0019fa04 mono_runtime_exec_main + 420
32 com.yourcompany.proteus 0x0019fd75 mono_runtime_run_main + 725
33 com.yourcompany.proteus 0x00050485 mono_jit_exec + 149
34 com.yourcompany.proteus 0x000031e1 main + 1665
35 com.yourcompany.proteus 0x00002395 start + 53

Thread 1:
0 libSystem.B.dylib 0x96ff8b36 semaphore_wait_trap + 10
1 com.yourcompany.proteus 0x0024b9de mono_sem_wait + 30
2 com.yourcompany.proteus 0x0013753a finalizer_thread + 74
3 com.yourcompany.proteus 0x0020b3d4 start_wrapper + 468
4 com.yourcompany.proteus 0x0023f97a thread_start_routine + 154
5 com.yourcompany.proteus 0x0024c071 inner_start_thread + 65
6 libSystem.B.dylib 0x97026259 _pthread_start + 345
7 libSystem.B.dylib 0x970260de thread_start + 34

Thread 2: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9701f382 kevent + 10
1 libSystem.B.dylib 0x9701fa9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x9701ef59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x9701ecfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x9701e781 _pthread_wqthread + 390
5 libSystem.B.dylib 0x9701e5c6 start_wqthread + 30

Thread 3:
0 libSystem.B.dylib 0x9701e412 __workq_kernreturn + 10
1 libSystem.B.dylib 0x9701e9a8 _pthread_wqthread + 941
2 libSystem.B.dylib 0x9701e5c6 start_wqthread + 30

Thread 4:
0 libSystem.B.dylib 0x9701e412 __workq_kernreturn + 10
1 libSystem.B.dylib 0x9701e9a8 _pthread_wqthread + 941
2 libSystem.B.dylib 0x9701e5c6 start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x97102693 ecx: 0x007e370c edx: 0x97059c5a
edi: 0x00000459 esi: 0x000b92d1 ebp: 0x007e3728 esp: 0x007e370c
ss: 0x0000001f efl: 0x00000202 eip: 0x97059c5a cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xa08fb020



Solución porfavor

[Sir John Douglas Cockcroft]

i need to wait for about 2minutes till it starts..

[LUBA]

at least you can start it..!

[Steveds]

dosent work at all

[atlasdrugged]

Bump

Not working for me either. I just bought it and it's just black/dark gray screen at start up.

[LUBA]

I don't even see a screen! It tells me right from the beginning, that it crashed! :D

[Corpo Sloppants]

OP here.
For some reason, Proteus suddenly works for me. without an update. So, I guess that's good.

[OwlBoy]

Puppy Shy님이 먼저 게시:

OP here.
For some reason, Proteus suddenly works for me. without an update. So, I guess that's good.

Did you update OS X?

[joetorsney]

Im on 10.7 and got the same problem. Wasted £5.
Anyone found a fix yet?

[Corpo Sloppants]

OwlBoy님이 먼저 게시:

Puppy Shy님이 먼저 게시:

OP here.
For some reason, Proteus suddenly works for me. without an update. So, I guess that's good.

Did you update OS X?

I haven't updated my OS since the problem arose, no. That's why it seems peculiar.

[noodlesat9]

I know it's been a while since this thread was active, but was there a solution to this problem?

[LUBA]

Negative^^

[Sewas Knight]

Actualizando el OS se soluciona el problema! :D