I have attempted to run the 4.0.0.4 and 4.0.1.0 builds of x2goclient on my MacBook Pro (OS version 10.7.3). Both of them crash immediately on launch. When attempting to run from the command line I get illegal instruction 4. Unfortunately, I have not used a Mac long enough to know how to troubleshoot this (though I do have an extensive UNIX/BSD/Linux background) beyond the basics outlined below.
For the 4.0.1.0 build, I have verified the md5 sum matches. I have the .dmg files for the 4.0.1.0 and 3.99.2.1 builds mounted. One thing I notice is that 4.0.x is significantly smaller than 3.99:
/dev/disk1s2 50272 50272 0 100% /Volumes/x2goclient /dev/disk3s2 223104 188328 34776 85% /Volumes/x2goclient 3.99.2.1
Are the newer builds expected to be this much smaller? Unpacked, the entire dmg for 4.0.x is about 70MB smaller than the actual space used by 3.99.x, even with the dmg for 3.99 being somewhat bigger than the amount of space required.
Hi,
I am not subscribed to the list, so please Cc me on all repsonses.
I have attempted to run the 4.0.0.4 and 4.0.1.0 builds of x2goclient on my MacBook Pro (OS version 10.7.3). Both of them crash immediately on launch. When attempting to run from the command line I get illegal instruction 4. Unfortunately, I have not used a Mac long enough to know how to troubleshoot this (though I do have an extensive UNIX/BSD/Linux background) beyond the basics outlined below.
Can you paste the complete command you're running and its output? I have not tested my build on a 10.7 system, because I only have a Mountain Lion box – packages are built against the 10.7 SDK though, so they should in theory run (however, since I'm using libraries from MacPorts and those haven't been built for 10.7 there's a chance that this causes problems).
Illegal instruction sounds like a 32bit vs. 64bit issue, but afaik the only 32bit-only CPUs Apple shipped with any recent OS X version were some rather old Mac Minis, so that probably doesn't apply in your case.
The easiest and quickest fix for you, if you already have MacPorts installed, would be to install the x2goclient port.
For the 4.0.1.0 build, I have verified the md5 sum matches. I have the .dmg files for the 4.0.1.0 and 3.99.2.1 builds mounted. One thing I notice is that 4.0.x is significantly smaller than 3.99:
/dev/disk1s2 50272 50272 0 100% /Volumes/x2goclient /dev/disk3s2 223104 188328 34776 85% /Volumes/x2goclient 3.99.2.1
Are the newer builds expected to be this much smaller? Unpacked, the entire dmg for 4.0.x is about 70MB smaller than the actual space used by 3.99.x, even with the dmg for 3.99 being somewhat bigger than the amount of space required.
I do not know how the 3.x series DMGs were built, but I assume since those were afaik were universal binaries, that at least the binaries had double the size. You should not compare the DMG sizes, though, because the 4.x series uses compression and the 3.x ones might not.
-- Clemens
On 4/3/13 6:02 PM, Clemens Lang wrote:
Hi,
I am not subscribed to the list, so please Cc me on all repsonses.
I have attempted to run the 4.0.0.4 and 4.0.1.0 builds of x2goclient on my MacBook Pro (OS version 10.7.3). Both of them crash immediately on launch. When attempting to run from the command line I get illegal instruction 4. Unfortunately, I have not used a Mac long enough to know how to troubleshoot this (though I do have an extensive UNIX/BSD/Linux background) beyond the basics outlined below.
Can you paste the complete command you're running and its output? I have not tested my build on a 10.7 system, because I only have a Mountain Lion box – packages are built against the 10.7 SDK though, so they should in theory run (however, since I'm using libraries from MacPorts and those haven't been built for 10.7 there's a chance that this causes problems).
dcom8009196:MacOS jefosburgh$ pwd /Applications/x2goclient.app/Contents/MacOS dcom8009196:MacOS jefosburgh$ ./x2goclient Illegal instruction: 4
Illegal instruction sounds like a 32bit vs. 64bit issue, but afaik the only 32bit-only CPUs Apple shipped with any recent OS X version were some rather old Mac Minis, so that probably doesn't apply in your case.
dcom8009196:MacOS jefosburgh$ uname -a Darwin dcom8009196 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
The easiest and quickest fix for you, if you already have MacPorts installed, would be to install the x2goclient port.
I had finally gotten around to getting fink installed, which doesn't seem to have an x2goclient package. I'll look into Macports.
For the 4.0.1.0 build, I have verified the md5 sum matches. I have the .dmg files for the 4.0.1.0 and 3.99.2.1 builds mounted. One thing I notice is that 4.0.x is significantly smaller than 3.99:
/dev/disk1s2 50272 50272 0 100% /Volumes/x2goclient /dev/disk3s2 223104 188328 34776 85% /Volumes/x2goclient 3.99.2.1
Are the newer builds expected to be this much smaller? Unpacked, the entire dmg for 4.0.x is about 70MB smaller than the actual space used by 3.99.x, even with the dmg for 3.99 being somewhat bigger than the amount of space required.
I do not know how the 3.x series DMGs were built, but I assume since those were afaik were universal binaries, that at least the binaries had double the size. You should not compare the DMG sizes, though, because the 4.x series uses compression and the 3.x ones might not.
I wasn't sure if the size difference was to be expected, and I wasn't aware those were universal binaries, so in that case the size difference does make sense.
On 4/4/13 8:00 AM, Jonathan Fosburgh wrote:
The easiest and quickest fix for you, if you already have MacPorts installed, would be to install the x2goclient port.
I had finally gotten around to getting fink installed, which doesn't seem to have an x2goclient package. I'll look into Macports.
Improvement. At least I can get to the login screen on x2goclient from Macports. However, it will not let me accept the ssh key, if I select yes it continuously re-prompts me to accept.
On Thu, Apr 04, 2013 at 08:00:14AM -0500, Jonathan Fosburgh wrote:
dcom8009196:MacOS jefosburgh$ pwd /Applications/x2goclient.app/Contents/MacOS dcom8009196:MacOS jefosburgh$ ./x2goclient Illegal instruction: 4
OK, that's doesn't tell me much. Can you enable crash reporting using $> defaults write com.apple.CrashReporter DialogType developer and re-run it? This should give you a possiblility to save a crash report. Please send this report to me. When you're done, you can disable the crash reporting again using $> defaults write com.apple.CrashReporter DialogType basic
dcom8009196:MacOS jefosburgh$ uname -a Darwin dcom8009196 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
So it's not a 32bit issue. It might be related to the libraries not being built against the 10.7 SDK and without MACOSX_DEPLOYMENT_TARGET set.
-- Clemens
On 4/5/13 6:19 PM, Clemens Lang wrote:
On Thu, Apr 04, 2013 at 08:00:14AM -0500, Jonathan Fosburgh wrote:
dcom8009196:MacOS jefosburgh$ pwd /Applications/x2goclient.app/Contents/MacOS dcom8009196:MacOS jefosburgh$ ./x2goclient Illegal instruction: 4
OK, that's doesn't tell me much. Can you enable crash reporting using $> defaults write com.apple.CrashReporter DialogType developer and re-run it? This should give you a possiblility to save a crash report. Please send this report to me. When you're done, you can disable the crash reporting again using $> defaults write com.apple.CrashReporter DialogType basic
Process: sh [2584] Path: /bin/sh Identifier: sh Version: ??? (???) Code Type: X86-64 (Native) Parent Process: sh [1402]
Date/Time: 2013-04-08 08:00:33.834 -0500 OS Version: Mac OS X 10.7.3 (11D2001) Report Version: 9 Sleep/Wake UUID: 88C7A54D-B8A1-469B-9FA1-D634235BFB2E
Interval Since Last Report: 2125850 sec Crashes Since Last Report: 112 Per-App Crashes Since Last Report: 5 Anonymous UUID: FD016301-555B-491A-83DD-F9BF0B51AFF9
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGILL) Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit): rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000 r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028 Logical CPU: 6
Binary images description not available
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 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: 35610 thread_create: 2 thread_set_state: 0
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 4 GB, SMC 1.69f3 Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533643465238432D48392020 Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533643465238432D48392020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.100.98.75.19) Bluetooth: Version 4.0.3f12, 2 service, 18 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: ST9500325ASG, 500.11 GB Serial ATA Device: HL-DT-ST DVDRW GS31N USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3 USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2 USB Device: RIM Composite Device, 0x0fca, 0x8004, 0xfa130000 / 6 USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 5 USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7 USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2 USB Device: Nexus S 4G, 0x18d1 (Google Inc.), 0x4e22, 0xfd120000 / 4 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
-
Clemens Lang -
Jonathan Fosburgh