When performing an emerge update, net-misc/vnc-4.1.2-r4 pulls in xorg-server-1.3.0.0, and hence tries to downgrade xorg-server from 1.4-r1. net-misc/vnc-4.1.2-r4 works fine with xorg-server-1.4-r1, so can we get the ebuild updated please? Cheers, jcat Reproducible: Always
Does the vnc module work fine with xorg-server-1.4?
Ah. Do you mean the actual vnc module for "real" xorg vt diplay?
Yeah. vnc fails to build with xorg-1.4 sources, so that's why there's no ebuild yet. Use a modified ebuild in your local overlay removing the xorg dep :)
Oops. I emerge vnc after xorg-server using a package for speed :p So, confirmed here, vnc dosen't actually build with xorg-server-1.4-r1 :) Shall I change th bug status to resolved or leave it pending a new version of vnc that works with xorg-server-1.4?
I tried patching to enable for xorg 1.4, but I get a failed patch: * Failed Patch: 17_all_vnc-server-modular-xorg.patch ! * (/var/tmp/portage/net-misc/vnc-4.1.2-r5/work/patch/17_all_vnc-server-modular-xorg.patch)
*** Bug 193198 has been marked as a duplicate of this bug. ***
http://forums.gentoo.org/viewtopic-t-585806.html Check out this link. It resolves the issue. and ues VNC works with the newer version of Xorg with no problem. Running it now. Sorry about the duplicate bug report.
*** Bug 193199 has been marked as a duplicate of this bug. ***
How did you get the r4 patch set to correctly patch the xorg-server part? The xorg-server code has changed enough that the patches (specifically 17, 21, and 29) fail. I am working on fixing them now. But I do not see how anyone could get it to work without fixing these.
Joe, If you look at the posted at http://forums.gentoo.org/viewtopic-t-585806.html You will see how I did the work around for the ebuild but you have to edit the ebuild for VNC every time you do a sync. This worked for me with no problem as the ebuild for vnc was looking for xorg 1.3.0.0 to be installed, if it was not installed then it would want to merge this package. I edited the ebuild and changed the 1.3.0.0 to 1.4 and resolved the issue.
Hi David, I did the same (1.3.0.0 -> 1.4), but then it crashed during patching. Do you have the "server" USE flag set? If not, this could explain why it is working for you, since the problem only occurs during the server patches.
(In reply to comment #11) > Hi David, > > I did the same (1.3.0.0 -> 1.4), but then it crashed during patching. Do you > have the "server" USE flag set? If not, this could explain why it is working > for you, since the problem only occurs during the server patches. > Because what he fixed is the need of downgrading, but not the patch failure. If you remove the depend line of xorg-server, you'll get the same fix.
well I did the following and it seemed to work for me. USE=server emerge vnc That worked for me with no problem. This is a fresh build though with the 2007.0 cd. I have not had any issues on the 2006.x cd as that box is running with no problems, It preforms a sync and an emerge -uDv world every night. Both boxes do this.
just so you know. I also had xorg 1.4 installed when I merge VNC with the use=server flag set.
Hmm, curious. Also, do you have pixman installed? If so, where is pixman.h? Mine is in /usr/include/pixman-1/pixman.h. I had to make a new patch to correct the #includes in xorg-x11-server-sources (the 1.4 version). Testing now. I really don't see how you got past the patching issue (and also the pixman.h thing). And Raúl, why would it be "OK" to remove the dependency on xorg-server?
(In reply to comment #15) > > And Raúl, why would it be "OK" to remove the dependency on xorg-server? > It wouldn't be okay. I'm just saying that if someone isn't using the xorg module, and wants to use vnc and not having any dep issue, he can copy the ebuild into his local overlay and remove the depend line.
looks like it is installed. Here is the list and locations. hope it helps you out. /usr/share/doc/pixman-0.9.5 /usr/lib/libpixman-1.so.0 /usr/lib/libpixman-1.la /usr/lib/libpixman-1.a /usr/lib/libpixman-1.so /usr/lib/libpixman-1.so.0.9.5 /usr/lib/pkgconfig/pixman-1.pc /usr/include/pixman-1 /usr/include/pixman-1/pixman.h
David, still not sure how you were able to build with USE=server. Did the vncserver work OK? In any case, after spending too many hours trying to patch the patches to work with xorg 1.4, I got into some knarly compile issues that indicate to me that this is too much of a hackish path to follow. Raul, is a newer patch set available?
I honestly think it does. I used xrdp which requires the vnc server. I used windows remote desktop to connect to my xorg gui, so i am guessing it works with no problem.
do you all think you can at least patch the ebuild for vnc to reference xorg 1.4?
David, before just changing it to 1.4, I really think we need to get to the bottom of why you can build the server, but Raul and I cannot. I can build without the server USE flag, and it does indeed work, so it would be worthwhile getting it working on xorg-1.4 for that, but even better would be to get the patch set updated so the whole things works. Raul, what is your opinion? I personally found it to be incredibly non-trivial to get the old patches re-worked. I got them so the patches succeeded, but then I started down a path of various compile problems that required even more patching, to the extent that I started to feel uncomfortable. For example, some of the calls in the 1.3 server code are now gone (like miRegisterPointerDevice()), and I was starting to have to guess at how to use the calls in a new way... But David, I still really do not understand how you could have gotten server to compile. This is a really strange mystery.
What would you like from me that may give you some insight on how I got it to work with no problem. like I said this is from the latest cd build of 2007.0
Can you check you vnc log and look for this: "Underlying X server release 70200000, The X.Org Foundation" - see what version you see... Also, verify that the only change you made to the ebuild is the XSERVER_VERSION="1.3.0.0" line, right? It should then pick up xorg-server-${XSERVER_VERSION}.tar.bz2, and this is the code that the vnc-4.1.2-r4-patches-0.1 file will try to patch. These two seem incompatible entirely... See if, while emerging, you see these exact files being unpacked, etc.
Vnc log information: Xvnc Free Edition 4.1.2 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 10300000, The X.Org Foundation As far as the modification to the ebuild yes that was the only change I made.
Created attachment 132122 [details] emerge log
Created attachment 132128 [details] the emerge information for vnc with the use=server Here is the info you requested for the emerge info.
(In reply to comment #26) > Created an attachment (id=132128) [edit] > the emerge information for vnc with the use=server > > Here is the info you requested for the emerge info. David, you are not building the server. If you look in your log, it's getting USE="-server", and there is a message telling you to change your USE flags if you need the server. Try: USE="server" emerge -1av vnc
okay.. for the first time I get the following now. However when I first did it I had to do the USE="server emerge vnc in order to get my xrdp package to install because xrdp requires vnc with the use=server option. So not sure what gives now. WILCNF40310Q1 ~ # USE="server" emerge -Dv vnc These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-misc/vnc-4.1.2-r4 USE="server*" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) net-misc/vnc-4.1.2-r4 to / * vnc-4.1.2-r4-patches-0.1.tar.bz2 MD5 ;-) ... [ ok ] * vnc-4.1.2-r4-patches-0.1.tar.bz2 RMD160 ;-) ... [ ok ] * vnc-4.1.2-r4-patches-0.1.tar.bz2 SHA1 ;-) ... [ ok ] * vnc-4.1.2-r4-patches-0.1.tar.bz2 SHA256 ;-) ... [ ok ] * vnc-4.1.2-r4-patches-0.1.tar.bz2 size ;-) ... [ ok ] * xorg-server-1.4.tar.bz2 MD5 ;-) ... [ ok ] * xorg-server-1.4.tar.bz2 RMD160 ;-) ... [ ok ] * xorg-server-1.4.tar.bz2 SHA1 ;-) ... [ ok ] * xorg-server-1.4.tar.bz2 SHA256 ;-) ... [ ok ] * xorg-server-1.4.tar.bz2 size ;-) ... [ ok ] * vnc-4_1_2-unixsrc.tar.gz MD5 ;-) ... [ ok ] * vnc-4_1_2-unixsrc.tar.gz RMD160 ;-) ... [ ok ] * vnc-4_1_2-unixsrc.tar.gz SHA1 ;-) ... [ ok ] * vnc-4_1_2-unixsrc.tar.gz SHA256 ;-) ... [ ok ] * vnc-4_1_2-unixsrc.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking vnc-4_1_2-unixsrc.tar.gz ;-) ... [ ok ] * checking vnc-4.1.2-r4-patches-0.1.tar.bz2 ;-) ... [ ok ] * checking xorg-server-1.4.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking vnc-4_1_2-unixsrc.tar.gz to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work >>> Unpacking vnc-4.1.2-r4-patches-0.1.tar.bz2 to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work >>> Unpacking xorg-server-1.4.tar.bz2 to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work * Applying various patches (bugfixes/updates) ... * 01_all_vnc-cookie.patch ... [ ok ] * 03_all_vnc-gcc4.patch ... [ ok ] * 05_all_vnc-use-fb.patch ... [ ok ] * 07_all_vnc-xclients.patch ... [ ok ] * 09_all_vnc-idle.patch ... [ ok ] * 11_all_vnc-via.patch ... [ ok ] * 13_all_vnc-restart.patch ... [ ok ] * 15_all_vnc-vncpasswd.patch ... [ ok ] * 17_all_vnc-server-modular-xorg.patch ... * Failed Patch: 17_all_vnc-server-modular-xorg.patch ! * ( /var/tmp/portage/net-misc/vnc-4.1.2-r4/work/patch/17_all_vnc-server-modular-xorg.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/17_all_vnc-server-modular-xorg.patch-31547.out * * ERROR: net-misc/vnc-4.1.2-r4 failed. * Call stack: * ebuild.sh, line 1684: Called dyn_unpack * ebuild.sh, line 798: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * vnc-4.1.2-r4.ebuild, line 90: Called epatch '/var/tmp/portage/net-misc/vnc-4.1.2-r4/work/patch' * eutils.eclass, line 304: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * The die message: * Failed Patch: 17_all_vnc-server-modular-xorg.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/build.log'. * * Messages for package net-misc/vnc-4.1.2-r4: * Failed Patch: 17_all_vnc-server-modular-xorg.patch ! * ( /var/tmp/portage/net-misc/vnc-4.1.2-r4/work/patch/17_all_vnc-server-modular-xorg.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/17_all_vnc-server-modular-xorg.patch-31547.out * * ERROR: net-misc/vnc-4.1.2-r4 failed. * Call stack: * ebuild.sh, line 1684: Called dyn_unpack * ebuild.sh, line 798: Called qa_call 'src_unpack' * ebuild.sh, line 44: Called src_unpack * vnc-4.1.2-r4.ebuild, line 90: Called epatch '/var/tmp/portage/net-misc/vnc-4.1.2-r4/work/patch' * eutils.eclass, line 304: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!" * The die message: * Failed Patch: 17_all_vnc-server-modular-xorg.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/build.log'. * WILCNF40310Q1 ~ #
I think I figured out what happend... When doing the fresh install I think I did infact install vnc with xorg 1.3.0.0 after it was done I preformed the emerge -uDv world and got the errors about the Xorg server version. Modified the ebuild to reference xorg 1.4 and it went on is merry way.. if vnc is installed before the ugprade to 1.4 then it is all fine and dandy for the world updates but when trying to install vnc for the frist time or after is when it gives the errors.. I will keep working on it when I can and let you all know what I come up with.
just checked on realvnc.com and there is a newer version of vnc 4.3. can someone check and see if they can get this to work ?
VNC Free Edition is only at 4.1.2
I have done some work on updating the patchset for xorg-server-1.4, and got everything to work up to the point of applying patch 44_all_vnc-server-autotools.patch, where it is trying to patch unix/xorg-x11-server-source/hw/vnc/Makefile.am, which is missing. Did I miss something in one of the previous patches?
Well after running in to the problem now with the box I been trying to update. came up with this work around and it seems to work but it is really yucky fix in my book. first you have to mask the following packages and if they are installed uninstall them. # =x11-base/xorg-server-1.4-r1 # =x11-drivers/xf86-video-mga-1.4.7 # =x11-proto/renderproto-0.9.3 # =x11-libs/libXrender-0.9.4 Then do the emerge vnc with the use=server. once that is done then update world and it will want do its thing. remove the blocked packages. Then do update world again. That was the yucky part, then you need to edit the vnc ebuild and change it from 1.3.0.0 to 1.4 and emerge world again and it should go though. This is a yucky work around but it works for now. kinda sad that you have to downgrade to 1.3.0.0 then install vnc with the use=server option then do the updates then edit the ebuild, then do the updates some more. just a yucky work around.
no more updates on this issue? emerge continues tries to go up and down on xorg versions...
a month and a week later...
(In reply to comment #35) > a month and a week later... > Guys.. there is a lot of work they have to figure out. If you do the work around it should work with no problem after it is applied. I know it is an ugly work around but it has worked on all 3 of my systems.
What I have done to provide an acceptable workaround is to use TightVNC and X11vnc. Both of these applications work fine with the current version of xorg-server, and provide usable functionality until they can get the RealVNC application updated.
I'm trying to follow the work around in comment #33 but vnc is still refusing to build. >>> Emerging (1 of 1) net-misc/vnc-4.1.2-r4 to / * vnc-4_1_2-unixsrc.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * xorg-server-1.3.0.0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * vnc-4.1.2-r4-patches-0.3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking vnc-4_1_2-unixsrc.tar.gz ;-) ... [ ok ] * checking vnc-4.1.2-r4-patches-0.3.tar.bz2 ;-) ... [ ok ] * checking xorg-server-1.3.0.0.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking vnc-4_1_2-unixsrc.tar.gz to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work >>> Unpacking vnc-4.1.2-r4-patches-0.3.tar.bz2 to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work >>> Unpacking xorg-server-1.3.0.0.tar.bz2 to /var/tmp/portage/net-misc/vnc-4.1.2-r4/work * Applying various patches (bugfixes/updates) ... * 001_all_vnc-server-alpha-build-fix.patch ... [ ok ] * 003_all_vnc-gcc4.3.patch ... [ ok ] * 01_all_vnc-cookie.patch ... [ ok ] * 03_all_vnc-gcc4.patch ... [ ok ] * 05_all_vnc-use-fb.patch ... [ ok ] * 07_all_vnc-xclients.patch ... [ ok ] * 09_all_vnc-idle.patch ... [ ok ] * 11_all_vnc-via.patch ... [ ok ] * 13_all_vnc-restart.patch ... [ ok ] * 15_all_vnc-vncpasswd.patch ... [ ok ] * 17_all_vnc-server-modular-xorg.patch ... [ ok ] * 19_all_vnc-nohttpd.patch ... [ ok ] * 21_all_vnc-server-s390.patch ... [ ok ] * 23_all_vnc-viewer-reparent.patch ... [ ok ] * 25_all_vnc-64bit.patch ... [ ok ] * 27_all_vnc-select.patch ... [ ok ] * 29_all_vnc-server-ppc64.patch ... [ ok ] * 31_all_vnc-newfbsize.patch ... [ ok ] * 35_all_vnc-ipv6.patch ... [ ok ] * 37_all_vnc-password-stdin.patch ... [ ok ] * 39_all_vnc-config.patch ... [ ok ] * 41_all_vnc-render.patch ... [ ok ] * 43_all_vnc-autotools.patch ... [ ok ] * 44_all_vnc-server-autotools.patch ... [ ok ] * 45_all_vnc-autotools-compile.patch ... [ ok ] * 47_all_vnc-server-always-use-fb.patch ... [ ok ] * 49_all_vnc-vsnprintf.patch ... [ ok ] * 51_all_vnc-server-24bit.patch ... [ ok ] * Done with patching * Running eautoreconf in '/var/tmp/portage/net-misc/vnc-4.1.2-r4/work/vnc-4_1_2-unixsrc/common' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running elibtoolize in: vnc-4_1_2-unixsrc/unix/xorg-x11-server-source * Applying install-sh-1.5.4.patch ... * Applying portage-1.5.10.patch ... * Applying max_cmd_len-1.5.20.patch ... * Applying sed-1.5.6.patch ... * Running elibtoolize in: vnc-4_1_2-unixsrc/common * Applying sed-1.5.6.patch ... * Running eautoreconf in '/var/tmp/portage/net-misc/vnc-4.1.2-r4/work/vnc-4_1_2-unixsrc/unix' ... * Running aclocal ... [ ok ] * Running libtoolize --copy --force --install --automake ... [ ok ] * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ ok ] * Running elibtoolize in: vnc-4_1_2-unixsrc/unix * Applying sed-1.5.6.patch ... * Running eautoreconf in '/var/tmp/portage/net-misc/vnc-4.1.2-r4/work/vnc-4_1_2-unixsrc/unix/xorg-x11-server-source' ... * Running aclocal ... [ !! ] * Failed Running aclocal ! * * Include in your bugreport the contents of: * * /var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/aclocal-6281.out * * ERROR: net-misc/vnc-4.1.2-r4 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2591: Called eautoreconf * environment, line 846: Called eaclocal * environment, line 785: Called autotools_run_tool 'aclocal' * environment, line 340: Called die * The specific snippet of code: * die "Failed Running $1 !"; * The die message: * Failed Running aclocal ! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/vnc-4.1.2-r4/temp/environment'. * and ***** aclocal ***** ***** aclocal configure.ac:1677: error: AC_SUBST: `libdir exec_prefix prefix' is not a valid shell variable name configure.ac:1677: the top level autom4te-2.62: /usr/bin/m4 failed with exit status: 1 aclocal-1.10: autom4te failed with exit status: 1 I can not switch to tightvnc because of Bug: #230612
still no way?
-r5 now uses/needs 1.5.1
