Bug#534468: x11vnc: -id not working
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 work around this problem? Can you reproduce this problem with the upstream version 0.9.8 of x11vnc? http://www.karlrunge.com/x11vnc/#downloading http://x11vnc.sourceforge.net/dev/x11vnc-0.9.8.tar.gz Thanks, Karl -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#501020: x11vnc depends on the openssl package
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 debian package named 'libssl0.9.8'. There can be no GPL issue about executing /usr/bin/openssl. Karl -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#495543: 495543
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. You will have to look for the package with vnc.so elsewhere, or if it is no longer included in debian, report that as a bug for the correct package (vnc4server I guess). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500627: x11vnc: segfault with xrandr -o 0 on arm
| 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 still occurs upstream in x11vnc versions 0.9.4 (released) and/or 0.9.5 (current dev)? What happens when you run x11vnc with its '-xrandr' option? What happens when (after a fresh X restart) AFTER x11vnc is started and a viewer connected you then do the 'xrandr -o 3' followed by 'xrandr -o 0' ? Is your device capable of 'xrand -s #number' size changes? If so, what happens if you use -s changes instead of -o's? Please post 'xrandr' output (i.e. query output) for before and after you do 'xrandr -o 3' and also for after the 'xrandr -o 0'. No need to run x11vnc to get these outputs. I don't have an X device capable fo xrandr rotation; only size changes. Could you post your xorg.conf so I might get an idea how to create a xrandr -o testing display? Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500627: x11vnc: segfault with xrandr -o 0 on arm
| 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 confused why in your log the width was 640 before and after...) So what happens when a left or right rotation (e.g. 'xrandr -o 2') is performed instead? The same question, but with '-xrandr' supplied to x11vnc. BTW, I found a debian workstation with nv video card that supported rotations, i.e. 'xrandr -o left' and 'xrandr -o right', (but not inversion 'xrandr -o inverted'.) I saw no crashes of x11vnc when using xrandr to rotate back and forth and doing -s size changes as well. One more question, you mention getting and using the xserver-xglamo X server. I now see there are other X server options (e.g. Xfbdev) for this device. Do they not have the problem? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500970: x11vnc package should include java VNC viewer applet jar files.
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/ssl/SignedUltraViewerSSL.jar evidently because (the explanation given for the 'dfsg' tag) the x11vnc-x.y.z.tar.gz tarball does not include the Java source files to create these jar files. These applet jars are served by the running x11vnc server to Java-enabled web browsers (or other java web starting mechanisms) that, in turn, re-connect to x11vnc as a VNC viewer. Note that starting with x11vnc 0.9.4: http://sourceforge.net/project/showfiles.php?group_id=32584&package_id=119006&release_id=626955 all of the java applet source files are included in the x11vnc tarball. So debian can now build and include the VNC viewer applet jar files in the x11vnc package. For x11vnc running on debian, to enable encrypted SSL VNC connections to any Java-enabled web browser on the Internet is a compelling reason to include these jar files in the x11vnc package. Also, to enable UltraVNC filetransfer with x11vnc to any Java-enabled web browser on the Internet is another compelling reason. For reference, here is a recipe a package creator could use to build the java applet VNC viewer jar files from source and package them: # change directory to the x11vnc tree: cd .../x11vnc-0.9.4 # remove all the prebuilt jar files: find . -name '*.jar' | xargs rm -f # build all the jar files from their java source: cd classes/ssl/src make update_jars make clean cd ../../.. # build and install x11vnc as normal, for example: ./configure --prefix=... args... make make install See classes/ssl/src/README for more information. This will be a very useful addition to the x11vnc package. If you decide to package these jars in a separate package outside of x11vnc, please make x11vnc *depend* on that package so that many users can readily take advantage of them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#501020: x11vnc depends on the openssl package
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 http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sslGenCA The debian openssl package is not on x11vnc's dependency list. It is not clear that openssl is a core debian package that is installed on every debian system, is it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505213: x11vnc depends on the tk8.4 package
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 installed it would work by default and would enable a some useful things. One thing it would enable is creating a desktop menu item that would launch a gui for x11vnc. E.g. 'x11vnc -gui tray=setpass -rfbport 5900' intended for naive users. This would enable addressing bug #475113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475113 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505213: x11vnc depends on the tk8.4 package
| 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 x11vnc's dependency on tk is that for this RFE (menu item): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475113 the way the fix for it has been implemented upstream (x11vnc 0.9.6) enables access to x11vnc for a larger class of users, i.e. naive desktop users. x11vnc's gui is used to interact with these users. Even for less-than-naive users it's not clear to me how x11vnc could startup in the background without some sort of interaction with the user. Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505213: x11vnc depends on the tk8.4 package
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? Contact [EMAIL PROTECTED]
Bug#475113: x11vnc should create a menu item
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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
debian-qa-packages@lists.debian.org
| 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 | using a VNC client (I tested several of them) on the viewing machine. | Also, typing on the keyboard does not seem to have any effect, but keys | do appear on the X11 console, and so do mouse clicks, etc. | | It seems to be just a screen update problem. This is probably the problem with the opengl based beryl window manager and the XDAMAGE extension described here: http://www.karlrunge.com/x11vnc/#faq-beryl Could you verify that this is the problem you are seeing? This seems to be a bug in Xorg that XDAMAGE doesn't work probably with OpenGL (i.e. XDAMAGE reports there are no screen changes, even though there are actually plenty) | I downloaded the latest x11vnc source 0.9.1 (and 0.9.2) from its project | site and they both work as expected after I compiled them. I have a workaround in those versions, it applies a heuristic to periodically check if the XDAMAGE extension is inaccurate, and if so abandon using it. I believe there will be output from x11vnc when it decides to abandon XDAMAGE. Could you send me the full x11vnc output when you use 0.9.1? I don't have beryl or opengl on any machines and so I can't test directly. The Xorg bug with OpenGL and XDAMAGE should really be fixed. When XDAMAGE is working properly it makes x11vnc more responsive and at the same time use fewer resources (i.e. less screen polling). Could you perhaps file a bug on that? (I'm not sure where it should be applied). Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-qa-packages@lists.debian.org
| 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 libxdamage -dev package installed and so the XDAMAGE support was disabled in the binary you built. Check this by runniung ldd on the x11vnc binary you built and look for the xdamage library dependency. Also, did you run "configure"? If so check the config.log output for libxdamage support message. BTW, I didn't mention it but a workaround for the debian binary would be to use "-noxdamage" option. See the FAQ for more info: http://www.karlrunge.com/x11vnc/#faq-beryl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452003: x11vnc: Option -noxinerama not recognized
> 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 in 0.9.4 (next 1-3 months I think). > 19/11/2007 10:30:06 Xinerama is present and active (e.g. multi-head). > 19/11/2007 10:30:06 Xinerama: enabling -xwarppointer mode to try to correct > 19/11/2007 10:30:06 Xinerama: mouse pointer motion. XTEST+XINERAMA bug. > 19/11/2007 10:30:06 Xinerama: Use -noxwarppointer to force XTEST. > 19/11/2007 10:30:06 fb read rate: 78 MB/sec > 19/11/2007 10:30:06 screen setup finished. > > I'm actually just tryint to turn off the multiple desktops that currently > get created -- seems to be a new feature in 0.9. In principle that's > great, but it should also be possible to turn it off, and -noxinerama > I thought might do it (or not). In private email with the bug submitter, we see that the "multiple desktop" observation was due to confusion about the -ncache mode. That effect has nothing to do with x11vnc's xinerama mode. The above Xinerama printout is unfortunate and confusing in that it seems to appears in a non-xinerama/multi-head setup. Evidently the X server is configured to activate Xinerama even when there is just 1 graphics card/output? I will try to improve this. I need to test on some newer distributions to see what is happening.. BTW, x11vnc's Xinerama mode is really esoteric: it only does something if the screen is not rectangular (e.g. 1280x1024 monitor next to 1024x768 monitor). Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452003: x11vnc: Option -noxinerama not recognized
> 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. ssvnc). It gives a nice speedup I used everyday. Best regards, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461382: x11vnc -forever segfault
| 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 vncviewer window as fast as it popped up for about 40-50 times. Is the "-passwd VNCpasswdfile" required for the failure? Which flavor and version of vncviewer are you using? Could you send the x11vnc output from the very beginning up until the SEGV? Could you also send a stack trace? Either use gdb manually, or use x11vnc's -dbg flag. Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461382: x11vnc -forever segfault
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 still being observed. A workaround is to apply the '-speeds dsl' (or "dsl" -> "lan" or "modem") to bypass the measurement and the problem. (BTW the speed estimate is really not that crucial to performance, it just gives some hints to x11vnc for the wireframing, etc) Please verify that this workaround actually works for you. I have uploaded to my site a new x11vnc-0.9.4.tar.gz tarball that puts in some guards against clients disconnecting during this period. It should be much improved. I would appreciate you trying it out and letting me know how it went. Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
