I’m always getting this error with osxnvc, no matter what client or compression I use. After getting this error once (and the server crashing), it works again (I can restart the server and then connect). Is this a bug?
I should mention that I start osxvnc-server in /Contents/MacOS/ directly via the console. Is this not the intended way? Anyway, I use Mac OS X 10.2.8.
(If it’s not the intended way: how DO I start osxvnc via the console?)
[EDIT] the small letter “oh” (“o”) doesn’t work, either. [/EDIT]
It’s ok to launch the server in console mode, you might try launching using the link that is provided directly inside the app wrapper, this prevents a Dock item from trying to show up in the dock (which may be the cause of the crash):
OSXvnc.app/osxvnc-server
Outside of that we don’t have anything to suggest. We aren’t seeing this bug here at Redstone although we have heard reports of it in the field anything more you can tell us about the bug will help us to track it down.
What system are you connecting from? Are you using US keyboard settings on both ends?
Both the Aqua app and the startup item work great for most people (thousands of them, actually) – we get compliments on the package every day. When you say it “doesn’t work”, are you referring to the same problem as above?
We have worked dilligently to try to recreate this problem but we can not get it to happen on 10.2.8 or 10.3.7.
Since you are the only person reporting this behavior and you are seeing it in the GUI app and the command line app it’s likely that something on your system is interfering with OSXvnc’s ability to function.
First question, are you running any tools using APE from Unsanity.org? Second are you running any other third party utilites that would effect the system or other applications across the board?
If you have either an OSXvnc.app.log or an OSXvnc-server.log in your ~/Library/Logs/CrashReporter directory please send those to us.
If you have access to another MacOS X system it would be helpful for you to try OSXvnc there also.
Unfortunately, files cannot be attached in this forum, so I’ll just mail them to you (support@redstonesoftware.com). Anyways, I’m very grateful to you that you took your time to look into this. Probably it’s because of the Windows client I use (standalone version of TightVNC):
frome the readme file:
TightVNC 1.2.9 Binary Distribution for Windows platforms
This distribution is based on the standard VNC source with
modifications introduced in TridiaVNC 1.4.0, and includes new
TightVNC-specific features and fixes, such as additional low-bandwidth
optimizations (“Tight” encoding with optional JPEG compression, “local
cursor” feature), improved WinVNC advanced settings, and much more.
TightVNC is available under the terms of the GNU General Public
License (GPL), inclided in the file LICENCE.txt. You can freely use
the software for any legal purpose, but we’re asking for a donation to
the TightVNC project from commercial users, as well as from motivated
individuals, who like the software. You can donate any amount of your
choice starting at 10 U.S. dollars. See the details here:
We’ve looked at your crash logs and it really appears that something is wrong with your system installation. This will no doubt sound like we are trying to pass the buck, but OSXvnc isn’t doing anything at the time of the crash except running the event loop – all of the activity is from Apple’s system calls and they have nothing to do with OSXvnc. This is not an issue that is being reported by other users, which further points to a problem on your machine. Unfortunately, the best suggestion that we can offer based on the available information is to reinstall Mac OS X.
You might also try rebooting your machine while holding down the shift key; this is the “Safe Boot mode” and will disable startup items and nonessential kernel extensions. Hold the shift key down during login to disable any login items. If the VNC server then works, then there is some conflict with something else that is normally being loaded.
Yes, that is possible, I was expecting such an answer a bit actually after I had read your posts. Maybe I’ll install Panther onto it, but that’ll have to wait, I don’t have the time for that right now.
I have what seem sto be a similar error. I run the OSXvnc server, connect a client which causes a crash of the server app, then when I restart the server the client connects. The error is either a segmentation fault or a bus error.
I’m using OSX 10.2.8 on a TiBook for the server, and my client is WinXP on a Thinkpad. I’m usually connecting via an SSH tunnel.
I run /Applications/OSXvnc/OSXvnc-server to start it, as recommended above.
I checked for APE yesterday, and it is installed on my system. I added OSXvnc to the exclude list, although I didn’t actually reinstall OSXvnc. I’m thinking that maybe there are OSXvnc prefs that should be removed?
I use two different clients to connect: the realvnc windows VNC viewer, and TightVNC viewer.
–Jason
edit: My workaround for this is to wrap the VNC server startup in a shell script which executes the startup twice in a row. Thus, when the first OSXvnc process crashes, the second one starts right away, and then my client can connect.
