Hi Stefan
thanks - I've seen your message via the webfrontend earlier and thus decided to sign up. However, CCing me would have been a good idea, yes.
I am flattered, but unfortunately not skilled enough to help you. The fix I send originated from a hour-long debugging session with two other people (non-OS X developers) - I am pretty sure I would have never caught such a stack overflow by myself. (Actually, I tried debugging via gdb at first and noticed the this pointer changed when going into the newly called channelLoop function, causing the program to crash - but was more than startled because this should have never had happened. Turns out, the stack was full and the first parameter of the function, i.e., "this" could not be pushed onto it, thus reading some random memory.)
At the same time, I am happy to say that otherwise the x2go client (from git) is fully functioning on OS X with one little flaw - I have to test the same git version on Linux as well to confirm a OS X specific bug though.
Oh yeah, and building nxproxy on OS X is not trivial but easily manageable with a few build system modifications.
Best regards,
Mihai
Am 18.02.2012 04:57, schrieb Mihai Moldovan:
Raise the stack space to 2MB for secondary threads. It previously used the 512KB system default.
Signed-off-by: Mihai Moldovan<ionic@ionic.de>
<snip>
Mihai, since you committed an OS X-specific patch: Would you be interested in picking up development of the OS X X2Go-Client? Originally, Mike wanted to take a stab at it, but didn't get around to do it, and Alex won't touch the OS X port unless he gets paid for it.
If you have the necessary skills and the time to keep the OS X port current, I could provide you with a Mac mini for testing. See http://comments.gmane.org/gmane.linux.terminal-server.x2go.devel/2112 and http://comments.gmane.org/gmane.linux.terminal-server.x2go.devel/2347 for the specs& background info.
I bought this Mac specifically so someone skilled enough can work on the X2Go-Client, and it's kind of sad that no one wants to pick up development even though hardware is provided for free/in exchange for a deposit.
I don't have enough Mac users among my clients that paying Alex (or anyone else) to work on it would be economically viable...
-Stefan
Hi Mihai,
On Sa 18 Feb 2012 21:25:36 CET Mihai Moldovan wrote:
Hi Stefan
thanks - I've seen your message via the webfrontend earlier and thus decided to sign up. However, CCing me would have been a good idea, yes.
I am flattered, but unfortunately not skilled enough to help you. The fix I send originated from a hour-long debugging session with two other people (non-OS X developers) - I am pretty sure I would have never caught such a stack overflow by myself. (Actually, I tried debugging via gdb at first and noticed the this pointer changed when going into the newly called channelLoop function, causing the program to crash - but was more than startled because this should have never had happened. Turns out, the stack was full and the first parameter of the function, i.e., "this" could not be pushed onto it, thus reading some random memory.)
At the same time, I am happy to say that otherwise the x2go client (from git) is fully functioning on OS X with one little flaw - I have to test the same git version on Linux as well to confirm a OS X specific bug though.
Oh yeah, and building nxproxy on OS X is not trivial but easily manageable with a few build system modifications.
Best regards,
Mihai
We are desperately searching for someone taking over the building and
testing of the Mac version of x2goclient. Not necessarily the
development.
As far as I can tell, you could be the person we are looking for. Or
rather: the beginning of a team of people.
If you could provide a set of built installer packages for a Mac
version of x2goclient, nxproxy and libxcomp (nx-libs-lite derived from
nx-libs.git) that would be awesome!!!!! NX -> idealistically without
Rosetta, but native...
Any help needed will be given to you (if we can)!!!
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Ah, native multi-arch binaries? I'll give it a try, hang on...
Hi Mihai,
On Sa 18 Feb 2012 21:25:36 CET Mihai Moldovan wrote:
Hi Stefan
thanks - I've seen your message via the webfrontend earlier and thus decided to sign up. However, CCing me would have been a good idea, yes.
I am flattered, but unfortunately not skilled enough to help you. The fix I send originated from a hour-long debugging session with two other people (non-OS X developers) - I am pretty sure I would have never caught such a stack overflow by myself. (Actually, I tried debugging via gdb at first and noticed the this pointer changed when going into the newly called channelLoop function, causing the program to crash - but was more than startled because this should have never had happened. Turns out, the stack was full and the first parameter of the function, i.e., "this" could not be pushed onto it, thus reading some random memory.)
At the same time, I am happy to say that otherwise the x2go client (from git) is fully functioning on OS X with one little flaw - I have to test the same git version on Linux as well to confirm a OS X specific bug though.
Oh yeah, and building nxproxy on OS X is not trivial but easily manageable with a few build system modifications.
Best regards,
Mihai
We are desperately searching for someone taking over the building and testing of the Mac version of x2goclient. Not necessarily the development.
As far as I can tell, you could be the person we are looking for. Or rather: the beginning of a team of people.
If you could provide a set of built installer packages for a Mac version of x2goclient, nxproxy and libxcomp (nx-libs-lite derived from nx-libs.git) that would be awesome!!!!! NX -> idealistically without Rosetta, but native...
Any help needed will be given to you (if we can)!!!
Greets, Mike
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
On Sa 18 Feb 2012 21:46:40 CET Mihai Moldovan wrote:
Ah, native multi-arch binaries? I'll give it a try, hang on...
Yeah...
Cheers, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi all
Turns out, building a static, multi-arch (fat) version of x2goclient is not that easy. Not because of x2goclient, but I had to (successfully) hack openldap into building universal first. Also, my system Qt libs have no static version, so I'm currently rebuilding them.
Anyway, I should have a working version by tonight (i.e., in at most 24 hours) including a fat binary file for x86 and x86_64. ppc will take a me a little bit longer, as my ppc assembler went missing (don't ask me how exactly.) Do we even care about ppc? Snow Leopard (10.6) is not working on ppc and Lion (10.7) dropped all ppc support for good.
Btw: so far, I've been using the NX nomachine source (nxproxy, nxcomp) for building a native 2-arch version of nxproxy (with nxcomp statically linked in.) I merely had a quick glance at your nx-libs.git, but from what I could see it's just the vanilla nx source redistributed, so we should be golden.
I'll post my "installer" (really just a .dmg image with x2goclient.app in it, how all project redistribute on OS X) to the list when it's ready and I've had some sleep.
Best regards,
Mihai
On Sa 18 Feb 2012 21:46:40 CET Mihai Moldovan wrote:
Ah, native multi-arch binaries? I'll give it a try, hang on...
Yeah...
Cheers, Mike
Am 19.02.2012 06:59, schrieb Mihai Moldovan:
I'll post my "installer" (really just a .dmg image with x2goclient.app in it, how all project redistribute on OS X) to the list when it's ready and I've had some sleep.
Uh, I don't think posting it to the list is a good idea. I'd suggest you send it by eMail to Heinz and Alex so they can upload it somewhere on x2go.org, and if you want to, CC me, since I should have my Mac mini back from Mike in a few days and could act as a tester. (I'm not exactly experienced with Mac OS X and have a reputation for crashing Macs just by getting near to them ;-) so I should be the ideal tester - if I can get it to work, the average Joe should be able to do that, too.)
-Stefan
Hi Mihai,
On So 19 Feb 2012 11:43:44 CET "newsgroups.mail2@stefanbaur.de" wrote:
Am 19.02.2012 06:59, schrieb Mihai Moldovan:
I'll post my "installer" (really just a .dmg image with x2goclient.app in it, how all project redistribute on OS X) to the list when it's ready and I've had some sleep.
Uh, I don't think posting it to the list is a good idea. I'd suggest
you send it by eMail to Heinz and Alex so they can upload it
somewhere on x2go.org, and if you want to, CC me, since I should
have my Mac mini back from Mike in a few days and could act as a
tester. (I'm not exactly experienced with Mac OS X and have a reputation for
crashing Macs just by getting near to them ;-) so I should be the
ideal tester - if I can get it to work, the average Joe should be
able to do that, too.)
If you have web space somewhere where you upload the .dmg and I can
download it that will be easiest, I guess. I also have upload rights
on code.x2go.org, so I can take over placing the files there.
Thanks, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mike
Don't worry, I'll just give you a link to the file on my server when it's done. ;)
So far I'm still building Qt4...
Best regards,
Mihai
Hi Mihai,
On So 19 Feb 2012 11:43:44 CET "newsgroups.mail2@stefanbaur.de" wrote:
Am 19.02.2012 06:59, schrieb Mihai Moldovan:
I'll post my "installer" (really just a .dmg image with x2goclient.app in it, how all project redistribute on OS X) to the list when it's ready and I've had some sleep.
Uh, I don't think posting it to the list is a good idea. I'd suggest you send it by eMail to Heinz and Alex so they can upload it somewhere on x2go.org, and if you want to, CC me, since I should have my Mac mini back from Mike in a few days and could act as a tester. (I'm not exactly experienced with Mac OS X and have a reputation for crashing Macs just by getting near to them ;-) so I should be the ideal tester - if I can get it to work, the average Joe should be able to do that, too.)
If you have web space somewhere where you upload the .dmg and I can download it that will be easiest, I guess. I also have upload rights on code.x2go.org, so I can take over placing the files there.
Thanks, Mike
Hi Mihai,
On So 19 Feb 2012 16:45:50 CET Mihai Moldovan wrote:
Hi Mike
Don't worry, I'll just give you a link to the file on my server when it's done. ;)
So far I'm still building Qt4...
Best regards,
Mihai
Brilliant!!! I am getting more and more excited!!!
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Aaand this...
/usr/bin/g++-4.2 -headerpad_max_install_names
-Wl,-syslibroot,/Developer/SDKs/MacOSX10.6.sdk -o
x2goclient.app/Contents/MacOS/x2goclient sharewidget.o settingswidget.o
configwidget.o sessionwidget.o connectionwidget.o configdialog.o
editconnectiondialog.o exportdialog.o imgframe.o LDAPSession.o
onmainwindow.o onmainwindow_part2.o onmainwindow_part3.o
onmainwindow_part4.o sessionbutton.o sessionmanagedialog.o
sshmasterconnection.o sshprocess.o SVGFrame.o userbutton.o
x2gologdebug.o printprocess.o cupsprint.o cupsprintwidget.o
cupsprintersettingsdialog.o printwidget.o printercmddialog.o
printdialog.o wapi.o clicklineedit.o httpbrokerclient.o ongetpass.o
x2gosettings.o brokerpassdlg.o contest.o xsettingswidget.o x2goclient.o
moc_configdialog.o moc_editconnectiondialog.o moc_exportdialog.o
moc_imgframe.o moc_onmainwindow.o moc_sessionbutton.o
moc_sessionmanagedialog.o moc_sshmasterconnection.o moc_sshprocess.o
moc_SVGFrame.o moc_userbutton.o moc_printprocess.o moc_cupsprintwidget.o
moc_cupsprintersettingsdialog.o moc_printwidget.o moc_printercmddialog.o
moc_printdialog.o moc_sessionwidget.o moc_connectionwidget.o
moc_settingswidget.o moc_sharewidget.o moc_clicklineedit.o
moc_httpbrokerclient.o moc_brokerpassdlg.o moc_contest.o
moc_xsettingswidget.o qrc_resources.o
/opt/local/libexec/heimdal/lib/libhcrypto.a
/opt/local/libexec/heimdal/lib/libcom_err.a
/opt/local/libexec/heimdal/lib/libasn1.a
/opt/local/libexec/heimdal/lib/libhdb.a
/opt/local/libexec/heimdal/lib/libheimntlm.a
/opt/local/libexec/heimdal/lib/libheimsqlite.a
/opt/local/libexec/heimdal/lib/libhx509.a
/opt/local/libexec/heimdal/lib/libkadm5clnt.a
/opt/local/libexec/heimdal/lib/libkafs.a
/opt/local/libexec/heimdal/lib/libkdc.a
/opt/local/libexec/heimdal/lib/libotp.a
/opt/local/libexec/heimdal/lib/libroken.a
/opt/local/libexec/heimdal/lib/libsl.a
/opt/local/libexec/heimdal/lib/libwind.a
/opt/local/libexec/heimdal/lib/windc.a
/opt/local/libexec/heimdal/lib/libkrb5.a
/opt/local/libexec/heimdal/lib/libgssapi.a /opt/local/lib/libsasl2.a
/usr/src/x2goclient-git/dist/lib/libssh.a
/usr/src/x2goclient-git/dist/lib/libldap.a
/usr/src/x2goclient-git/dist/lib/liblber.a -lcups -L/opt/local/lib
-lQtSvg -framework ApplicationServices -framework Carbon -framework
AppKit -framework Security -lQtGui /opt/local/lib/libjpeg.a
/opt/local/lib/liblcms.a /opt/local/lib/libintl.a
/opt/local/lib/libiconv.a /usr/lib/libresolv.dylib
/opt/local/lib/libmng.a /opt/local/lib/libtiff.a /opt/local/lib/libpng.a
-lQtNetwork -framework SystemConfiguration -framework CoreFoundation
/usr/lib/libssl.dylib /usr/lib/libcrypto.dylib -lQtCore
/usr/lib/libz.dylib -lm
is transforming into this:
x2goclient.app/Contents/MacOS/x2goclient: /usr/lib/libcups.2.dylib (compatibility version 2.0.0, current version 2.8.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 152.0.0) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1038.32.0) /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 37594.0.0) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 41.0.0)
/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 293.5.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 550.29.0) /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0) /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 751.29.0)
Yay, no more external dependencies.
Now, let me build your nxcomp and test the application.
Hi Mihai,
On So 19 Feb 2012 16:45:50 CET Mihai Moldovan wrote:
Hi Mike
Don't worry, I'll just give you a link to the file on my server when it's done. ;)
So far I'm still building Qt4...
Best regards,
Mihai
Brilliant!!! I am getting more and more excited!!!
Mike
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi Mike
please fetch and try the file at http://www.ionic.de/x2goclient-3.99.1.0.dmg.
It's starting up and connecting fine for me, however, I can't test X11 stuff as some other bug is biting me again where it can't connect to the X11 server. I started debugging this a few days ago but couldn't get really into it as the problem just vanished from one run to another...
Anyway, I'd be delighted if you could give it a try, Mike!
Best regards,
Mihai
Hi Mihai,
On So 19 Feb 2012 11:43:44 CET "newsgroups.mail2@stefanbaur.de" wrote:
Am 19.02.2012 06:59, schrieb Mihai Moldovan:
I'll post my "installer" (really just a .dmg image with x2goclient.app in it, how all project redistribute on OS X) to the list when it's ready and I've had some sleep.
Uh, I don't think posting it to the list is a good idea. I'd suggest you send it by eMail to Heinz and Alex so they can upload it somewhere on x2go.org, and if you want to, CC me, since I should have my Mac mini back from Mike in a few days and could act as a tester. (I'm not exactly experienced with Mac OS X and have a reputation for crashing Macs just by getting near to them ;-) so I should be the ideal tester - if I can get it to work, the average Joe should be able to do that, too.)
If you have web space somewhere where you upload the .dmg and I can download it that will be easiest, I guess. I also have upload rights on code.x2go.org, so I can take over placing the files there.
Thanks, Mike
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi Mihai,
On So 19 Feb 2012 19:55:41 CET Mihai Moldovan wrote:
Hi Mike
please fetch and try the file at http://www.ionic.de/x2goclient-3.99.1.0.dmg.
It's starting up and connecting fine for me, however, I can't test X11 stuff as some other bug is biting me again where it can't connect to the X11 server. I started debugging this a few days ago but couldn't get really into it as the problem just vanished from one run to another...
Maybe an xauth problem? Does X2GoClient's Qt work through X11 on Mac
OS or does Qt4 connect to the graphical Mac desktop directly?
Anyway, I'd be delighted if you could give it a try, Mike!
Unfortunately, I do not have a Mac around (anymore). I am currently in
the process of sending a test machine provided by Stefan back to him.
Stefan will be able to test your build in a couple of days.
Anyone else on the list who has a Mac OS around, please give us
feedback on the .dmg file provided by Mihai.
Thanks thanks thanks!!! Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mihai,
On So 19 Feb 2012 19:55:41 CET Mihai Moldovan wrote:
Hi Mike
please fetch and try the file at http://www.ionic.de/x2goclient-3.99.1.0.dmg.
It's starting up and connecting fine for me, however, I can't test X11 stuff as some other bug is biting me again where it can't connect to the X11 server. I started debugging this a few days ago but couldn't get really into it as the problem just vanished from one run to another...
Maybe an xauth problem? Does X2GoClient's Qt work through X11 on Mac OS or does Qt4 connect to the graphical Mac desktop directly? Nah, Qt4 is using the native Cocoa interface on OS X. X2go then tries to start (if not already started) and to connect to the xserver on localhost:6000 (which seems weird/wrong to me, why not via the UNIX socket for instance? I guess I should try to change that.) and then it should basically work.
However, on my system the X server is listening on port 6004 instead of 6000 (thus using displayPort 5?) - for whatever reason. Due to the hardcoded connection settings in x2goclient, it won't be able to connect to the server... but again, as I was about to fix it, it started working again (probably the xserver restarted on displayport 0/port 6000), so I lost the interest and tried getting the universal build setup first.
Anyway, I'd be delighted if you could give it a try, Mike!
Unfortunately, I do not have a Mac around (anymore). I am currently in the process of sending a test machine provided by Stefan back to him. Stefan will be able to test your build in a couple of days.
Anyone else on the list who has a Mac OS around, please give us feedback on the .dmg file provided by Mihai.
Oh alright, I can wait. But please do me a big favor: fetch http://www.ionic.de/x2goclient-3.99.1.0-r2.dmg - I forgot to add i386 support in the x2goclient binary before, shame on me. r2 is now featuring both x86 and x86_64 support.
Best regards,
Mihai
Am 19.02.2012 20:45, schrieb Mihai Moldovan:
However, on my system the X server is listening on port 6004 instead of 6000 (thus using displayPort 5?) - for whatever reason.
Does "defaults read org.x.X11" say anything regarding the port number? If so, have you tried setting it to 6000 using the corresponding "defaults write" command (possibly requiring sudo)?
Oh alright, I can wait. But please do me a big favor: fetch http://www.ionic.de/x2goclient-3.99.1.0-r2.dmg - I forgot to add i386 support in the x2goclient binary before, shame on me. r2 is now featuring both x86 and x86_64 support.
I fetched both and will give them a try once my Mac is back. ;-) Note that my Mac is x86_64-based, so I will neither be able to confirm nor to deny the functionality of the x86 support.
-Stefan
Does "defaults read org.x.X11" say anything regarding the port number? If so, have you tried setting it to 6000 using the corresponding "defaults write" command (possibly requiring sudo)?
Nope, and note that I'm "special" yet again - I'm using the MacPorts X11-dev (that is, pretty much always the newest version.)
defaults read org.macports.X11 does give me a list with a lot of options, but only those which could be set via the GUI too (rootless, clipboard, etc.) - no displayPort or TCP port.
AFAIK the X server is autodetecting the displayPort and adding this to 6000 (i.e., port = 6000 + displayPort = 6000 if displayPort == 0).
At the same time, I really don't see any reason for connecting to the local machine via X11, I'll try to get a connection via the UNIX socket during next week. :)
I fetched both and will give them a try once my Mac is back. ;-) Note that my Mac is x86_64-based, so I will neither be able to confirm nor to deny the functionality of the x86 support. Well... personally, I don't care about x86-only machines either, as there was only one generation without x86_64 support, but since I "went the extra mile", I'd still like to know if it's working on these boxes too. Let's see if other people are reporting back. :)
Best regards,
Mihai
Hi,
<snip>
Well... personally, I don't care about x86-only machines either, as there was only one generation without x86_64 support, but since I "went the extra mile", I'd still like to know if it's working on these boxes too. Let's see if other people are reporting back. :) I might be able to get my hands on a Mac at work tomorrow, but I can't
Den 19. feb. 2012 21:46, skrev Mihai Moldovan: promise it, and I'm not sure if it's 32 or 64 bits. I'll report back soon as I have found the Mac and tested.
Regards, Terje
Hi,
Den 19. feb. 2012 22:50, skrev Terje Andersen:
Hi,
<snip>
Well... personally, I don't care about x86-only machines either, as there was only one generation without x86_64 support, but since I "went the extra mile", I'd still like to know if it's working on these boxes too. Let's see if other people are reporting back. :) I might be able to get my hands on a Mac at work tomorrow, but I can't
Den 19. feb. 2012 21:46, skrev Mihai Moldovan: promise it, and I'm not sure if it's 32 or 64 bits. I'll report back soon as I have found the Mac and tested.
I'm sorry to say that the Mac (the only one we had) isn't around at our office anymore. So I can't help with testing Mac packages :-(
//Terje
Hi Mihai,
On So 19 Feb 2012 21:46:11 CET Mihai Moldovan wrote:
AFAIK the X server is autodetecting the displayPort and adding this to 6000 (i.e., port = 6000 + displayPort = 6000 if displayPort == 0).
It might well be that localhost:0 is hardcoded in x2goclient for Mac.
Not sure, though.
Have you tried
DISPLAY=:0 x2goclient
or in your case
DISPLAY=:4 x2goclient
???
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mike
Sorry for responding so late, but I didn't get around it yesterday.
It might well be that localhost:0 is hardcoded in x2goclient for Mac. Not sure, though. Have you tried DISPLAY=:0 x2goclient [...]
Nope, that won't work on OS X. Let me elaborate.
OS X is not using X11 as all other UNIX(-like) systems do, but instead a proprietary drawing API called Cocoa (or the old, x86-only Carbon interface) based on the Quartz rendering/compositing engine.
On other UNIX(-like) systems, Cocoa/Carbon would be (for instance) Gtk/Qt and Quartz the X11 server.
In contrast to this, OS X does ship an X11 server, too, called "XQuartz", which is using the Quartz rendering engine.
Now that we covered Cocoa and Quartz, let's take a look at the Qt framework. Qt is essentially just another drawing API, providing widgets, manual drawing and whatnot. As you know, Qt can use the X11 system as rendering backend. What you may not know, is that on OS X, Qt can also use Cocoa is a backend, acting as a compatibility/portability wrapper using the Cocoa API. If using those kinds of libraries, for instance with x2goclient, your application will *not* use the X11 server at all but instead paint directly via Cocoa to Quartz.
Qt on OS X is most commonly used as this wrapper for Cocoa (because it works really well in that mode.) As such, x2goclient has also used this mode and I of course kept it this way.
This means, that whenever x2goclient is started, it's using the native Cocoa/Quartz rendering engine and we naturally can not assume that the X11 server on this machine is actually running.
Thus, the x2goclient code tries to start the X server first via a hardcoded path to startx (which sounds wrong to me, we should be using launchctl for that kind of stuff) and afterwards connecting to the hardcoded location TCP localhost:6000 (again, seems wrong, I'll try to get the current UNIX socket and connect to that instead or something like this.) Also, it should be noted that the environment variable DISPLAY it not used/handled in this code at all, so setting it is pointless (even more so for a Cocoa application. ;))
I hope I could shed some light on the internals and outline the work I have planned.
Best regards,
Mihai
OS X is not using X11 as all other UNIX(-like) systems do, but instead a proprietary drawing API called Cocoa (or the old, x86-only Carbon interface) based on the Quartz rendering/compositing engine.
On other UNIX(-like) systems, Cocoa/Carbon would be (for instance) Gtk/Qt and Quartz the X11 server.
In contrast to this, OS X does ship an X11 server, too, called "XQuartz", which is using the Quartz rendering engine.
Not sure how relevant this is, but X11 is removed from Mac OS X 10.8 (Mountain Lion) and has to be downloaded by the user: http://www.macrumors.com/2012/02/17/apple-removes-x11-in-os-x-mountain-lion-...
Cheers, Daniel
Hi Mihai,
On Mi 22 Feb 2012 01:43:31 CET Mihai Moldovan wrote:
Sorry for responding so late, but I didn't get around it yesterday.
No problem at all!
- On 19.02.2012 11:10 PM, Mike Gabriel wrote:
It might well be that localhost:0 is hardcoded in x2goclient for Mac. Not sure, though. Have you tried DISPLAY=:0 x2goclient [...]
Nope, that won't work on OS X. Let me elaborate.
[... Mac OS tutorial on screen output, Qt, Cocoa, X and X2GoClient ...]
This was a really neat tutorial on graphics rendering on Mac. Thanks a
lot for taking your time to write that down.
Do you think you can improve the sitatuaion with x2goclient and send
us patches?
That would really be awesome!!! Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hey Mike
Do you think you can improve the sitatuaion with x2goclient and send us patches?
That's my plan. :) But don't expect it too soon, as I have to learn for university, too...
Best regards,
Mihai
Hi, I just tried it and works
2012/2/19 newsgroups.mail2@stefanbaur.de <newsgroups.mail2@stefanbaur.de>
Am 19.02.2012 20:45, schrieb Mihai Moldovan:
However, on my system the X server is listening on port 6004 instead of
6000 (thus using displayPort 5?) - for whatever reason.
Does "defaults read org.x.X11" say anything regarding the port number? If so, have you tried setting it to 6000 using the corresponding "defaults write" command (possibly requiring sudo)?
Oh alright, I can wait. But please do me a big favor: fetch
http://www.ionic.de/**x2goclient-3.99.1.0-r2.dmg<http://www.ionic.de/x2goclient-3.99.1.0-r2.dmg>- I forgot to add i386 support in the x2goclient binary before, shame on me. r2 is now featuring both x86 and x86_64 support.
I fetched both and will give them a try once my Mac is back. ;-) Note that my Mac is x86_64-based, so I will neither be able to confirm nor to deny the functionality of the x86 support.
-Stefan
______________________________**_________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/**mailman/listinfo/x2go-dev<https://lists.berlios.de/mailman/listinfo/x2go-dev>
On So 19 Feb 2012 20:45:08 CET Mihai Moldovan wrote:
Oh alright, I can wait. But please do me a big favor: fetch http://www.ionic.de/x2goclient-3.99.1.0-r2.dmg - I forgot to add i386 support in the x2goclient binary before, shame on me. r2 is now featuring both x86 and x86_64 support.
copied and rename to code.x2go.org: http://code.x2go.org/releases/binary-macosx/x2goclient/x2goclient-3.99.1.0pr...
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Mihai,
On So 19 Feb 2012 06:59:47 CET Mihai Moldovan wrote:
Turns out, building a static, multi-arch (fat) version of x2goclient is not that easy. Not because of x2goclient, but I had to (successfully) hack openldap into building universal first. Also, my system Qt libs have no static version, so I'm currently rebuilding them.
Ok! Great!
Anyway, I should have a working version by tonight (i.e., in at most 24 hours) including a fat binary file for x86 and x86_64. ppc will take a me a little bit longer, as my ppc assembler went missing (don't ask me how exactly.) Do we even care about ppc? Snow Leopard (10.6) is not working on ppc and Lion (10.7) dropped all ppc support for good.
PPC is not so interesting to us, I guess. x86 and x86_64 should get
the main focus.
Btw: so far, I've been using the NX nomachine source (nxproxy, nxcomp) for building a native 2-arch version of nxproxy (with nxcomp statically linked in.)
That would be sufficient for our first test loops.
I merely had a quick glance at your nx-libs.git, but from what I could see it's just the vanilla nx source redistributed, so we should be golden.
The source tree is pretty much vanilla NX, but the patch list is long
and those patches only get applied on (a) building the packages for
Debian/Ubuntu or (b) when I roll the tarballs you find under this URL:
http://code.x2go.org/releases/source/nx-libs/
It's such a gift that you give your time to this!!!
Thanks, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...