| Summary: | net-misc/tightvnc-1.3_alpha5 (Xvnc) segfaults on amd64 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jason McGuiness <gentoo-bugs> |
| Component: | New packages | Assignee: | Disenchanted (RETIRED) <morfic> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aliz, jstubbs, lorenzo, mathieu.malaterre, rich0 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch to make tightvnc-1.3_alpha7 compile/run on amd64 | ||
I am experiencing exactly the same problem. Is there any progress on resolving this bug? Same problem also on amd64 box. Segfault in vnc having followed steps outlined in the following howto: http://forums.gentoo.org/viewtopic-t-72893-highlight-tightvnc+howto.html Same here, using current xorg. It segfaults on start. Does this work for anybody? Otherwise I'd recommend removing the ~amd64 flag. Take a look at: http://runsafe.no/tightvnc-compile.patch The patch needs a little adjustment as it currently stands, but that does allow the build to go through. However, Xvnc seems to segfault. So, this is about as useful as the other Xvnc versions with the same problem. In any case, I figured I'd post this for the sake of its limited usefulness... I've just found a workaround at http://gentoo-wiki.com/HOWTO_Xvnc_terminal_server#Additional_notes_to_AMD64_users - doesn't really fix the bug, but if anybody needs Xvnc urgently he might want to try it this way: For now tightvnc seems to segfault when compiled for x86_64. If you really want to get it running on amd64, you might carefully try this: Set up a 32bit chroot environment as explained in http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml?part=1&chap=4#doc_chap3 and then compile tighvnc static for 32bit USE="static" emerge tightvnc quickpkg tightvnc copy the package to /usr/portage/packages/All and install it on the 64bit system. ACCEPT_KEYWORDS="~amd64" emerge tightvnc --usepkg -pv ACCEPT_KEYWORDS="~amd64" emerge tightvnc --usepkg Created attachment 78616 [details, diff]
Patch to make tightvnc-1.3_alpha7 compile/run on amd64
This patch fixes several problems when compiling and running tightvnc-1.3_alpha7 on amd64 under Gentoo. I've tested the Xvnc/vncserver and that seems to work. At least it's a very significant improvement. Please apply to ~amd64 asap.
I haven't exhaustively stress tested it. I haven't done any testing on any other platform and I haven't tested the viewer.
(In reply to comment #6) > This patch fixes several problems when compiling and running > tightvnc-1.3_alpha7 on amd64 under Gentoo. I've tested the Xvnc/vncserver and > that seems to work. At least it's a very significant improvement. Please apply > to ~amd64 asap. Works for me too (~amd64)! Thank you very much! Thanks Bradley, spamassassin ate the bugzilla email when you added the patch, i saw maxxer's comment, changed my spam filter since. Looks good on x86, ppc and amd64, applying. new ebuild should show inn ~ 2hours thank you all again |
In tightvnc-1.3_alpha5 I get a coredump in running vncserver: Reproducible: Always Steps to Reproduce: 1. Rebuilt tightvnc with CFLAGS="-march=opteron -O0 -g -pipe", FEATURES+="nostrip", USE+="debug". 2. run "Xvnc :2 -desktop 'X' -httpd /usr/share/tightvnc/classes -auth /home/jason/.Xauthority -geometry 1024x768 -depth 24 -rfbwait 120000 -rfbauth /home/jason/.vnc/passwd -rfbport 5902 -core" Actual Results: Examining the core file in GDB shows this: (gdb) where #0 0x0000002a95efb047 in strftime_l () from /lib/tls/libc.so.6 #1 0x00000000004bce52 in rfbLog (format=0x5d575d "Xvnc version %s\n") at init.c:956 #2 0x00000000004bbb59 in InitOutput (screenInfo=0x721aa0, argc=19, argv=0x7fbfffee68) at init.c:411 #3 0x000000000041d9f4 in main (argc=19, argv=0x7fbfffee68) at main.c:349 (gdb) q Expected Results: I would expect vncserver to start.