Menu

#1353 Port tightVNC to the IBM POWER v2 ABI archicture

open
nobody
None
5
2015-10-10
2015-05-05
No

Currently tightvnc doesn't run on POWER new ABI v2[1] architecture, and fails to load.

It builds properly, but fails to execute at:

Xtightvnc :1
05/05/15 14:15:57 Xvnc version TightVNC-1.3.9
05/05/15 14:15:57 Copyright (C) 2000-2007 TightVNC Group
05/05/15 14:15:57 Copyright (C) 1999 AT&T Laboratories Cambridge
05/05/15 14:15:57 All Rights Reserved.
05/05/15 14:15:57 See http://www.tightvnc.com/ for information on TightVNC
05/05/15 14:15:57 Desktop name 'x11' (debian:1)
05/05/15 14:15:57 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
05/05/15 14:15:57 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
Segmentation fault

The strace log could be found at https://gist.github.com/ee72b94a4f1e396e922c.

[1] https://wiki.debian.org/ppc64el#ABI_Documentation

Related

Bugs: #1353

Discussion

  • curaga

    curaga - 2015-06-05

    The attached two patches fix this issue on top of the 1.3.10 release, tested on Unicamp's minicloud. Valgrind clean (only a couple unrelated warnings about uninitialized padding bytes being sent, something that was fixed in the upstream X a few years ago, but this is based on over a decade old X).

    Patch 1 cleans up some malloc confusion, and patch 2 adds the ppc64el support.

     
    • Breno Leitao

      Breno Leitao - 2015-06-05

      Good. I will working to validate it.

      On Fri, Jun 5, 2015 at 10:14 AM, curaga curaga@users.sf.net wrote:

      The attached two patches fix this issue on top of the 1.3.10 release,
      tested on Unicamp's minicloud. Valgrind clean (only a couple unrelated
      warnings about uninitialized padding bytes being sent, something that was
      fixed in the upstream X a few years ago, but this is based on over a decade
      old X).

      Patch 1 cleans up some malloc confusion, and patch 2 adds the ppc64el
      support.

      Attachment: 0001-Clean-up-the-malloc-conflicts.patch (2.0 kB; text/plain)
      0002-Add-ppc64el-support.patch (3.3 kB; text/plain)


      Status: open
      Group:
      Created: Tue May 05, 2015 06:21 PM UTC by Breno Leitao
      Last Updated: Thu Jun 04, 2015 01:52 AM UTC
      Owner: nobody

      Currently tightvnc doesn't run on POWER new ABI v2[1] architecture, and
      fails to load.

      It builds properly, but fails to execute at:

      Xtightvnc :1
      05/05/15 14:15:57 Xvnc version TightVNC-1.3.9
      05/05/15 14:15:57 Copyright (C) 2000-2007 TightVNC Group
      05/05/15 14:15:57 Copyright (C) 1999 AT&T Laboratories Cambridge
      05/05/15 14:15:57 All Rights Reserved.
      05/05/15 14:15:57 See http://www.tightvnc.com/ for information on TightVNC
      05/05/15 14:15:57 Desktop name 'x11' (debian:1)
      05/05/15 14:15:57 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
      05/05/15 14:15:57 Listening for VNC connections on TCP port 5901
      Font directory '/usr/share/fonts/X11/Speedo/' not found - ignoring
      Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
      Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
      Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
      Segmentation fault

      The strace log could be found at
      https://gist.github.com/ee72b94a4f1e396e922c.

      [1] https://wiki.debian.org/ppc64el#ABI_Documentation

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/vnc-tight/bugs/1353/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #1353

  • Breno Leitao

    Breno Leitao - 2015-06-08

    I just tried the patches against the tighvnc version 1.3.10 and I am able to connect to a ppc64el vnc server. Thanks!

     
  • David Edelsohn

    David Edelsohn - 2015-06-27

    Any progress with merging the patch?

     
  • David Edelsohn

    David Edelsohn - 2015-10-06

    If TightVNC cannot merge the patches, can they be incorporated into the downstream Linux distro patch sets for Open Source packages?

     
  • curaga

    curaga - 2015-10-06

    Yes, they are already in Ubuntu (15.10, since June 30) and waiting to be in Debian.

     
  • David Edelsohn

    David Edelsohn - 2015-10-06

    Any outreach to SuSE or Red Hat? The also maintain downstream patches.

     
  • David Edelsohn

    David Edelsohn - 2015-10-07

    What's the ETA for Debian? We will consider downstream patches in Ubuntu and Debian as success with respect to the bounty.

     
  • curaga

    curaga - 2015-10-07

    It needs a Debian developer to upload the change, unfortunately I'm not one. I will ask around.
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788107

     
  • David Edelsohn

    David Edelsohn - 2015-10-07

    IBM also has contacts with Debian community and can help if you don't get a response.

     
  • curaga

    curaga - 2015-10-10
     
  • David Edelsohn

    David Edelsohn - 2015-10-10

    Thanks. Good work. I'm waiting for Bountysource to allow the reward.

     

Log in to post a comment.