Hi, at least in my case the problem was that the SingleClick VNC
server reported the protocol version 3.16 and the client's top version
was the infamous 3.8 ; unfortunately, the client thinks that 3.8 is the
maximum version that would be available ever and behaves
(in)appropriately.
In my case
The attachment change server_minor = 8 to server_minor == 8 at
line 241 seems to be a patch. If it isn't, please remove the patch
flag from the attachment, remove the patch tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vnc4 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/123631
Title:
** Bug watch added: Debian Bug tracker #477664
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477664
** Also affects: tightvnc (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477664
Importance: Unknown
Status: Unknown
--
vncviewer -listen allows connections from
two bug reports upstream for this already.
http://sourceforge.net/tracker/?func=detailaid=1737746group_id=14067atid=114067
http://sourceforge.net/tracker/?func=detailaid=2959724group_id=14067atid=114067
** Bug watch added: SourceForge.net Tracker #1737746
I just wanted to buzz back. Use `ssvnc` it has the same syntax for
`-listen`, but works with RHB 3.8, and opens a Window.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification
Actually, svnc doesn't use 3.8
Proto: RFB 003.016
Setting RFB version to 3.3 for UltraVNC Single Click.
Connected to RFB server, using protocol version 3.3
Security-Type: 1 (rfbSecTypeNone) Latency: 4.53 ms
No authentication needed
--
vncviewer -listen allows connections from UltraVNC SC
** Changed in: tightvnc (Debian)
Status: Unknown = Confirmed
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Single-click using RealVNC 4.1
aamonster is right, that's how I've been doing it, but here's the
details:
1) Place the following files into the same directory:
* 7zr.exe (from the 7zip extras file @
http://sourceforge.net/projects/sevenzip/files/7-Zip/4.65/7z465_extra.7z/download)
*
Solved: instead of buggy sc created 7zip sfx installer archive with
contains winvnc.exe + batch file to run it. The same functionality, but
size ~600k.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You
Any more information about this?
My current workaround is having a laptop with Hardy running on it,
ideally I want to upgrade to Karmic or Fedora 12, something which I
can't do right now because only the Hardy version of tightvnc viewer
will work with SC.
--
vncviewer -listen allows connections
people report that ssvnc might help as workaround
http://ubuntuforums.org/showpost.php?p=8299617postcount=118
** Also affects: baltix
Importance: Undecided
Status: New
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
Same problem.
Karmic
2.6.31-15-generic
xtightvncviewer and xvnc4viewer
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of Ubuntu
Bugs, which is
any update on this fix ? I'm having the same problem, any work around
available ?
Thanks
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of
I'm on Karmic with the same issue. Commenting to subscribe and
hopefully gain some solution.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of
Yes, I can confirm that this bug is present in Karmic. Does anyone know
what's happening with this?
I'll try the workaround listed above
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug
From the UltraVNC forum:
sc is build with the old rfb protocol and use some non official rfb numbers.
( The whole thing was made before the rfb 3.4 was out)
If not using a ultravnc viewer, the viewer should tell he support 3.3 else
the server get confused and connection fails.
--
vncviewer
Still an issue in Karmic and also xvnc4viewer is affected.
** Also affects: vnc4 (Ubuntu)
Importance: Undecided
Status: New
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug
The temporary solution suggested by orgoj in comment #9 is working for me,
thanks!
It was quite easy to install (althought my first impression of the website was
different). I just downloaded this file:
http://downloads.sourceforge.net/ssvnc/ssvnc_unix_only-1.0.22.tar.gz
...extracted it to
@jptechnical: use the vncviewer mentioned here
https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/123631/comments/9 to
make it work in intrepid.
for scrolling in the other direction use the right mouse button...
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
Tried the binaries for enhanced xtightvncviewer, unfortunately the
scroll bars only work one way, but that was the case with the repo
version as well. When I tried Intrepid I found that xtightvncviewer
would not work listening either... which forced me back to hardy. So
far, the only vnc viewer
same problem here on latest intrepid amd64. was working before on hardy
without problems.
** Changed in: vnc4 (Ubuntu)
Status: New = Confirmed
** Changed in: tightvnc (Ubuntu)
Sourcepackagename: vnc4 = tightvnc
--
vncviewer -listen allows connections from UltraVNC SC clients, but
Temporary solution is use binnary from
http://www.karlrunge.com/x11vnc/ssvnc.html, working fine.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of
Same error in 8.10
xvnc4viewer -listen 53755
VNC Viewer Free Edition 4.1.1 for X - built Apr 16 2008 13:02:40
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Mon Nov 3 21:57:00 2008
main:Listening on port 53755
Mon Nov 3 21:57:06 2008
CConn:
same here and works for me too : )
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The above solution worked for me also.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Figured i'd share the comment from the duplicate bug:
https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/158798
If you do sudo apt-get remove xvnc4viewer (which also removes ubuntu-
desktop unfortunately), then all is well again as the command xvncviewer
will use the old version that
You'r right. I forgot the viewer... :-)
I tried it yeasterday again. When my brother connects with UltraVNC SC
everything works fine. But when a freind of mine trys to connect with (with the
same client) I also get an error.
Thats very strange.
--
vncviewer -listen allows connections from
albuntu: for the record, it's 'xtightvncviewer -listen' and that
totally does not work with UltraVNC's SC software in Gutsy.
In Feisty, yes. In Gutsy, nope. Thanks for trying though.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
I also have this problem.
You could use xtightvnc instead. This one works.
Open a terminal and type: xtightvnc -listen
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification
Hello.
I too have this problem.
--
vncviewer -listen allows connections from UltraVNC SC clients, but doesn't
display the window
https://bugs.launchpad.net/bugs/123631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
31 matches
Mail list logo
