The initial bug report contains this message output by ssh:
Running ssh:
env LD_PRELOAD=/usr/lib/ssvnc/./lim_accept.so ssh -x -x -f -t -C -L
5930:localhost:5900 "192.168.2.2" "sleep 15"
Pseudo-terminal will not be allocated because stdin is not a terminal.
builder@192.168.2
I filed a bug against Xorg for XTestFakeMotionEvent:
https://bugs.freedesktop.org/show_bug.cgi?id=43101
Best,
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
This is a bug in the Xorg server, evidently introduced in 7.4, where
XTestFakeMotionEvent() no longer respects the 'screen_number' argument
passed to it.
I think a bug should be filed against Xorg for XTestFakeMotionEvent.
This bug 620620 should be closed somehow too...
Also, in the upstream x11v
Hi,
I finally tracked this down to a bug in the Xorg server. Sometime around
2009 the XTestFakeMotionEvent() interface was broken and it ignores the
'screen' input parameter.
A workaround is to use the this cmdline option:
x11vnc -xwarppointer
to have x11vnc use XWarpPointer() instead
> But is it necessary to create wrapper scripts on the fly (in a manner that
> I'm
> not entirely sure is secure) and execute those?
I guess to remove the xterm dependency there would be a debian patch that
modifies the wrapper(s) to set SSVNC_XTERM_REPLACEMENT=x-terminal-emulator
if it wasn't a
How is x11vnc being started? Do you know the x11vnc command line
being used?
If you can capture the printout from x11vnc for this failure please attach
it to this bug.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Also, as a workaround you probably can use the -skip_keycodes x11vnc
option to indicate which keycodes to not inject. It is a comma separated
list of the ones you want skipped.
(See the -help output or
http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes for
more info.)
So one coul
What version of x11vnc is this?
Try the "-xkb" option. That option should be activated automatically
for you using x11vnc 0.9.10 and later (but the activation depends on
the current keyboard mapping.)
If you are using x11vnc 0.9.10 or later (or if -xkb doesn't work),
run x11vnc with the options
Could you run x11vnc with the options "-v -o log.txt -dk -dk" (yes two
-dk's) and then reproduce the problem and then attach the entire log.txt
file to this bug.
Thanks,
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
As an aside (i.e. independent of a distro's dependencies), the environment
variable SSVNC_XTERM_REPLACEMENT can be set to a different terminal
emulator (one can also set this variable in ~/.ssvncrc) See Help -> Tip 15
for more info.
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@li
> KVM/QEMU, mostly during BIOS phase/early boot. Your question is spot
> on because I think that it might not be ssvnc's fault at all. I will
> further investigate.
Thank you, please do.
For reference, ssvnc's popup action ctrl-alt-del does not do anything
special (this is just the original unix
What is the remote system and mechanism by which it responds to ctrl-alt-del?
Also, what is the remote system vncserver?
Thanks,
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello,
Please rerun the failure and collect the full x11vnc output and attach
it to this thread so I can have a look at it. Add "-v -dp -dk" to the
command line for extra debugging info. Please also use x11vnc version
0.9.12 and indicate the complete command line typed.
I do not see this proble
Is this the same problem as 559088?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559088
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello,
You can achieve this customization of the ssh command by putting something
like this in your ~/.ssvncrc file:
env=SSH=ssh -Snone
or by exporting SSH='ssh -Snone' in your environment before starting ssvnc.
The SSH option is now documented in the upstream ssvnc 1.0.29 development
version a
| It's just this patch, right?
|
| --- ssvnc-1.0.27/vnc_unixsrc/vncviewer/rfbproto.c 2010-04-18
04:34:38.0 +0200
| +++ ssvnc-1.0.28/vnc_unixsrc/vncviewer/rfbproto.c 2010-06-04
03:20:39.0 +0200
| @@ -854,7 +854,9 @@
| switch (secType) {
| case r
Hello,
The recently released upstream version 1.0.28 of SSVNC should fix this bug:
http://sourceforge.net/projects/ssvnc/files/ssvnc/1.0.28/release-notes-1.0.28.txt/view
Please report back here whether it works for your case or not.
Thanks,
Karl
--
To UNSUBSCRIBE, email to debian-bugs-
Package: x11vnc-data
Version: 0.9.10-1
This is (IMHO) a bug, but this report is mainly a head-ups and
announcement that it is fixed in the x11vnc 0.9.11 upstream tarball.
The debian x11vnc-data jar files were not built to enable compatibility
back to earlier JVM's on the (arbitrary) client-side
Not sure, but it might be this involving xpg echo:
http://www.karlrunge.com/x11vnc/miscbuild.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Well, it looks like you've closed the bug already, but for reference
'request_code 53' (in the original bug report) is X_CreatePixmap:
% grep -w 53 /usr/include/X11/Xproto.h
#define X_CreatePixmap 53
and from the XCreatePixmap man page:
Pixmap XCreatePixmap(Display
> I would opt for option 2 or maybe 3.
>
> About option 2, I could split x11vnc into x11vnc and x11vnc-data packages.
> x11vnc-data package will contain all jars (/usr/share/x11vnc/classes) and
> will
> be platform-independent (architecture all).
So when a user installs the x11vnc package then
> Sun's java/jarsigner isn't available on the hppa architecture.
Oh, I see now.
Looking around I found these implementation files:
http://docjar.org/html/api/gnu/javax/crypto/jce/keyring/GnuKeyring.java.html
http://docjar.org/html/api/gnu/java/security/Registry.java.html
The former appe
Hi,
> # ls -la /dev/null
> crw-rw-rw- 1 root root 1, 3 2009-12-12 12:30 /dev/null
> # x11vnc -quiet -storepasswd foo /dev/null
> stored passwd in file /dev/null
> # ls -la /dev/null
> crw--- 1 root root 1, 3 2009-12-12 12:30 /dev/null
>
> x11vnc also claims to write to block devices with retu
Hi,
> Even though I'm using the -quiet option I still get output "stored
> passwd in file"
In the upstream x11vnc 0.9.9 dev tarball I have clarified the scope of
the -quiet option:
| -q, -quiet Be quiet by printing less informational output to
|stderr. (use -n
Does it still fail when using Sun's java/jarsigner?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Great! Could you please fix sshvnc and tsvnc in the same manner? :-)
Whoops, you're right. I just uploaded a fix in the 1.0.25 dev tarball.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Recommended packages *are* installed by default nowadays. Debian policy says
> that Recommends lists packages that should be installed in "all but unusual"
> cases.
Ah, that's good to hear. I'm glad that change has taken place (apologies
that I don't follow these basic things more closely.)
Package: ssvnc
Version: 1.0.23-1
Severity: normal
The debian ssvnc package puts 'stunnel4' on its recommends list instead
of its depends list.
This leads to a situation that confuses nearly all users that start up
the SSVNC encryption gui (i.e. the main 'ssvnc' command), namely that
SSVNC's defau
This bug is fixed in the recent upstream SSVNC 1.0.24 release.
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Sorry, of course ssvnc accepts a number of options. Those should be
> printed by ssvnc -h.
This situation has been improved in the upstream 1.0.24 tarball. Check
it out when you get the chance.
Karl
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "u
> Hi Karl,
>
> please find attached a patch for X11vnc manpage related to Debian bug #496294:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496294
>
> cheers,
>
> Fathi
Thanks Fathi. I have incorporated something like the patch into the
x11vnc 0.9.9 development tarball and uploaded it jus
Hi Fathi,
> > The debian openssl package is not on x11vnc's dependency list.
>
> It is.
> At least on Debian package 0.9.3.dfsg.1-1.
> I didn't checked previous versions.
> And that's a bug.
I believe you have missed the point of this bug.
It is about the debian package named 'openssl' not the
In the shell where 'x11vnc -forever -id pick ...' is typed, what is the
value of the $DISPLAY environment variable? Is it the local display
(e.g. :0.0) or is it a remote SSH redir (e.g. localhost:10)?
Please collect the entire x11vnc output and post it to this thread.
Does the '-noshm' option wo
> xtightvncviewer 1.3.9 cannot connect to x11vnc from
> http://www.karlrunge.com/x11vnc/
What command line are you using to run the x11vnc from that site?
(and what version of x11vnc are you using?)
I am guessing you are supplying the '-tightfilexfer' option to x11vnc, no?
If you were I think t
The upstream x11vnc source tarball now includes and installs a
'x11vnc.desktop' file.
For this launcher to work properly, x11vnc's dependency on the tk
package needs to be recorded. See #505213.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubsc
Correction: This bug should refer to the 'tk' package not 'tk8.4'.
I didn't realize there was a meta package 'tk' that points to the
default tk version's package. So x11vnc's dependency is on 'tk'.
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
| hallo,
|
| I for sure do not want to have tk8.4 installed only for a x11vnc feature
| I am not going to use ever.
I'm not sure I understand your argument. Are you saying most Debian
users feel the same way?
In any event, the main thing driving this request that Debian record
and install x11
Package: x11vnc
Version: 0.9.3.dfsg.1-1
The x11vnc program's "-gui" option depends on the tk8.4 package (via
/usr/bin/wish). Linux distros like debian seem to not ship this utility
by default as they once did.
The x11vnc gui mode is optional and doesn't look terribly nice, but by
having tk/wish
Package: x11vnc
Version: 0.9.3.dfsg.1-1
The x11vnc program depends on the openssl package for certificate
creation, see the following links for details:
http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl
http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCert
Package: x11vnc
Version: 0.9.3.dfsg.1-1
In the x11vnc VNC server package, debian does not include the x11vnc
java viewer applet jar files:
classes/VncViewer.jar
classes/ssl/VncViewer.jar
classes/ssl/SignedVncViewer.jar
classes/ssl/UltraViewerSSL.jar
classes
| Steps to reproduce:
| 1) Get openmoko freerunner and install xserver-xglamo package from
| pkg-fso repository http://pkg-fso.alioth.debian.org/debian/
| 2) run xrandr -o 3
| ...
I realized that 'xrandr -o 3' probably enables the 'inverted' state and
not a rotation 'left' or 'right' (I was confus
| Steps to reproduce:
| 1) Get openmoko freerunner and install xserver-xglamo package from
| pkg-fso repository http://pkg-fso.alioth.debian.org/debian/
| 2) run xrandr -o 3
| 3) start x11vnc
| 4) connect to the vncserver with xvnc4viewer
| 5) run xrandr -o 0
Could you please verify this problem s
Hi,
Your bug (actually looks more like a configuration problem on your part
to me) has nothing to do with the x11vnc and libvncserver packages.
Those packages have nothing to do with the "vnc.so" module that
the Xorg X server can load. I'm pretty sure the same applies to
/usr/lib/xrdb/libvnc.so.
After receiving the info and logfiles from Benedikt I was able to reproduce
the problem when going over a slow link.
The problem occurs in the "network speed" estimation for new VNC clients.
If the VNC client disconnects during this measurement it could lead to
an invalid client pointer that is s
| 1) start on 10.0.0.1: x11vnc -forever
| 2) connect and disconnect a couple of times (just close the vncviewer window):
| #! /bin/sh
|
| while true;
| do
| vncviewer -passwd VNCpasswdfile 10.0.0.1
| done
I tried this on a lenny install and could not reproduce the problem,
even "X-ing out" the vn
> It's not a good idea, on the other hand, to strongly recommend using
> ncache, as the current version does.
Sure it is! How else to get people to try it out and give feedback.
I appreciate yours (I wish more people did).
It works quite well, especially with an ncache-aware VNC viewer
(i.e. ssv
> 19/11/2007 10:20:52 *** unrecognized option(s) ***
> 19/11/2007 10:20:52 [1] -noxinerama
> 19/11/2007 10:20:52 For a list of options run: x11vnc -opts
> 19/11/2007 10:20:52 or for the full help: x11vnc -help
This has been fixed today in the upstream x11vnc dev. tarball and will
be released
| just an update:
|
| recompiling the x11vnc testing sources (in the package
| libvncserver-0.8.2) produces a working x11vnc.
|
| (debuild binary didn't seem to work though, I had to do a simple make in
| the x11vnc sources directory)
Hmmm, not sure what would cause this... Maybe you don't have
| Since I upgraded my testing distribution to the last libc&xorg yesterday,
| x11vnc from testing does not seem to work anymore. When I run it, I
| can connect to the remote desktop but the on the local viewing machine
| the desktop itself does not get screen updates anymore. I am obviously
| usi
> It would be great if you could supply a -geometry specification to
> x11vnc so that it only grabs the specified part of the frame buffer.
I believe the -clip option should do what you want:
-clip WxH+X+Y Only show the sub-region of the full display that
correspon
Update: I believe I fixed this bug in the x11vnc-0.8.4 release I made
last week. If you could double check it fixes it that would be useful.
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
| Running with -quiet I get this output:
| ==
| OK: x11vnc -forever -nofilexfer -usepw -quiet
| -permitfiletransferpermit file transfer support
| The VNC desktop is: hal:0
| PORT=5900
| ==
I believe I have this fixed in the libvncserver CVS.
(libvncserver/cargs.c rev 1.9).
However the cu
Please check whether the problem does or does not occur with the debian
package x11vnc-0.8.2-1 or, even better, the most recent build:
http://www.karlrunge.com/x11vnc/x11vnc-0.8.4.tar.gz
There is probably no need to install either one on your test system;
you can just run them in place.
Update:
Looking around in the Libvncserver rfb/rfbproto.h I see a new encoding:
#define rfbEncodingServerIdentity 0xFF25
that I believe conflicts with the old rfbEncodingBackground tightvnc
encoding (evidently no longer used). I have contacted the Libvncserver
author who added this to
I found some more info on this bug, and a workaround of sorts.
| Looking into the krdc output i think the bug is in krdc:
|
| Zero size rect - ignoring
| Rect too large: 28535x28192 at (30062, 27502)
|
| And shows the error dialog: "The connection to the host has been interrupted".
|
Hi,
I downloaded:
krdc_3.5.5-2_i386.deb
x11vnc_0.8.2-1_i386.deb
and extracted the program binaries. I ran the x11vnc binary on one
machine and krdc on another machine and had no problem connecting to
the X session at all.
Admittedly, I ran the x11vnc on a older debian system an
Hi,
We have what I hope is good news for this problem. I spoke with the
Libvncserver maintainer and we will be releasing these two packages
simultaneously next week sometime:
LibVNCServer-0.8
x11vnc-0.8
They will be from the same CVS tree, so hopefully Debian can pick up
the Lib
Hello Ludovic,
I looked at your log and I do not think you are building correctly.
You need to build from the x11vnc-0.7.2.tar.gz tarball. It looks
like you downloaded libvncserver-0.7.1.tar.gz and dropped in
the x11vnc.c file. Or something like that.
This no longer works. It may build but i
> There's nothing interseting in the x11vnc debug (bellow):
There is one (admittedly hard to notice in all the output):
> ...
> 14/10/2005 11:02:15 No XTEST or DEC-XTRAP protection from XGrabServer.
> 14/10/2005 11:02:15 Deadlock if your window manager calls XGrabServer!!
> 14/10/2005 11:02:15 --
KnuX wrote:
> Package: x11vnc
> Version: 0.7.1-2
> Severity: normal
>
>
> Hi,
>
> I'm using x11vnc after some weeks of x0vncviewer, performances are
better ;)
> But it crashs when I use Firefox (from the vnc4viewer).
If the crash is easy to reproduce (I hope it is) try running
one of these:
Package: tcsh
Version: 6.13.07-2
I believe I have traced this bug to tcsh 6.13.07 (it took me a while to
realize it might be something besides xterm). I apologize in advance
if this issue is not in tcsh, or is just something strange in my own
environment...
Every 2-3 months I do a 'apt-get dist-
61 matches
Mail list logo
