Client not working on OS X Mavericks

3 posts / 0 new
Last post
Krater
Client not working on OS X Mavericks

Hi
I just installed the server on Ubuntu 12.04, tried it with an XP client and it works (great, by the way!).
But then I installed the client on OS X Mavericks (10.9) and it loads, but under "USB Hubs" it shows a red dot with a string (8B27CB00-FE8D-11D5-AFBD-F46D045FB58C) which appears an disappears.
If I click on properties I get:

NAME:
Version: 0.0.0
STATE: Connected (error)
Address: NAS.local.:7575
CONNECTED FOR: 5 sec
MAX DEVICES:
SERIAL NUMBER: 8B27CB00-FE8D-11D5-AFBD-F46D045FB58C

Once it crashed. This is what appeared in system.log:

Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: VirtualHere crashed, backtrace follows...
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 0 VirtualHere 0x000000010000165a _ZN11Application16OnFatalExceptionEv + 74
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 1 VirtualHere 0x000000010052747c wxFatalSignalHandler + 28
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 2 libsystem_platform.dylib 0x00007fff864c45aa _sigtramp + 26
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 3 CoreFoundation 0x00007fff83e89609 CFDictionarySetValue + 217
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 4 VirtualHere 0x000000010052f6cb _ZN12wxEvtHandler23SearchDynamicEventTableER7wxEvent + 203
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 5 VirtualHere 0x000000010052f43b _ZN12wxEvtHandler19ProcessEventLocallyER7wxEvent + 59
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 6 VirtualHere 0x000000010052f34c _ZN12wxEvtHandler12ProcessEventER7wxEvent + 188
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 7 VirtualHere 0x0000000100384664 _ZN12wxWindowBase8TryAfterER7wxEvent + 212
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 8 VirtualHere 0x000000010052f380 _ZN12wxEvtHandler12ProcessEventER7wxEvent + 240
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 9 VirtualHere 0x00000001003bbe23 _ZN24wxScrollHelperEvtHandler12ProcessEventER7wxEvent + 35
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 10 VirtualHere 0x000000010052f75f _ZN12wxEvtHandler18SafelyProcessEventER7wxEvent + 15
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 11 VirtualHere 0x000000010037d220 _ZNK12wxWindowBase17HandleWindowEventER7wxEvent + 16
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 12 VirtualHere 0x0000000100327d0a _ZN10wxMenuBase9SendEventEii + 218
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 13 VirtualHere 0x00000001001c64e2 _ZN6wxMenu20HandleCommandProcessEP10wxMenuItemP8wxWindow + 114
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 14 AppKit 0x00007fff89f903d0 -[NSApplication sendAction:to:from:] + 327
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: [bt]: 15 AppKit 0x00007fff89fab348 -[NSMenuItem _corePerformAction] + 394
Nov 3 22:45:37 MacBook-de-K.local VirtualHere[554]: VirtualHere backtrace complete
Nov 3 22:45:43 MacBook-de-K.local ReportCrash[563]: Failed to create CSSymbolicatorRef for VirtualHere[554]
Nov 3 22:45:43 MacBook-de-K.local ReportCrash[563]: Failed to create dSYM-less CSSymbolicatorRef for VirtualHere[554]
Nov 3 22:45:43 MacBook-de-K com.apple.launchd.peruser.501[230] (com.virtualhere.vhui.81344[554]): Job appears to have crashed: Abort trap: 6
Nov 3 22:45:43 MacBook-de-K.local ReportCrash[563]: Saved crash report for VirtualHere[554] version 1.7.9 (1.7.9) to /Users/k/Library/Logs/DiagnosticReports/VirtualHere_2013-11-03-224543_MacBook-de-K.crash

This is the content of the crash file:

Process: VirtualHere [554]
Path: /Applications/VirtualHere.app/Contents/MacOS/VirtualHere
Identifier: com.virtualhere.vhui
Version: 1.7.9 (1.7.9)
Code Type: X86-64 (Native)
Parent Process: launchd [230]
Responsible: VirtualHere [554]
User ID: 501

Date/Time: 2013-11-03 22:45:42.686 +0100
OS Version: Mac OS X 10.9 (13A603)
Report Version: 11
Anonymous UUID: 845C4A47-B028-477F-3D75-F37CED6D469C

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000070

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff72ed3310 rcx: 0x00007fff5fbfc948 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff5fbfc970 rsp: 0x00007fff5fbfc948
r8: 0x0000000000166ce0 r9: 0x00000000001270e0 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x000060800005dcd0 r13: 0x00007fff5fbfd3f0 r14: 0x0000000000000006 r15: 0x00007fff74203da8
rip: 0x00007fff8c85f866 rfl: 0x0000000000000206 cr2: 0x00007fff8b379478

Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133

Binary images description not available

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 2
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 515
thread_create: 1
thread_set_state: 0

If you need anything else, just tell me.
Regards,

Krater

Michael
Thanks for the info.

Thanks for the info.

Are you seeing http://askubuntu.com/questions/339702/network-service-discovery-disabled... when you start your ubuntu server?

If so that is disabling name resolution of NAS.local. which means your mac client cannot look it up.

To work around this issue, in the osx client hardcode the ip of the server by Right clicking USB Hubs -> Specify Hubs -> +

Krater
Hi

Hi
Hardcoding the server IP works, thanks!
I didn't see that error as the server is headless. I'll try to fix the name resolution when I have time.
Regards,

Krater

Log in or register to post comments