Alan Coopersmith wrote: > James Carlson wrote: >> Dumb off-topic non-architectural question, but this fast-track just >> reminded me: does this update also fix the core dumps that happen on >> v6-enabled machines? I have to type "vncviewer 127.1:1" instead of >> "localhost:1" or just ":1", because the v6 "::1" causes vncviewer to >> drop core. >> >> If so, then the update is a really welcome addition. ;-} > > I'm not seeing core dumps when trying that with either the old or new > versions of vncviewer, nor do I see any bug reports in bugster under > solaris/xserver/vnc matching that description. We can take that > discussion offline to see if we can figure out what's going on with > that bug.
It was such an obvious problem that I thought it must have been seen by someone else. I guess I should be more diligent about reporting problems. Anyway, I've reported it now: http://defect.opensolaris.org/bz/show_bug.cgi?id=12366 > This update does not fix the limitation that while vncviewer is > capable of connecting to a RFB server over IPv6, the Xvnc server only > listens for incoming connections on IPv4. That's a limitation that > needs to be fixed upstream. (The vncviewer IPv6 support was > originally a Fedora addition to RealVNC we picked up, and which the > Fedora maintainer has integrated into TigerVNC upstream now.) OK. Is there a project team working on those upstream issues? -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
