Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-ppc-user
Navigation:
Lists: gentoo-ppc-user: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentooppc-user@g.o
From: David Chamberlain <daybird@g.o>
Subject: Re: vnc
Date: Mon May 6 18:53:04 2002
Hi Derek,

there are i386 settings in the vnc ebuild.  It's on my todo list, and 
I'll move it to the top of the list, unless someone else wants to claim it.
I don't know what the problem would be with tightvnc.  You could try 
recompiling with lower optimisation (i.e. change CFLAGS in 
/etc/make.conf or export the setting at time of build).

David

Derek Greentree wrote:

>Hi all,
>  I've tried this with tightvnc and regular vnc ebuilds: I emerge
>(tight)vnc, and after tweaking the font path settings, I got vncserver
>to launch an actual Xvnc process that wouldn't die. However, I'm having
>2 problems:
>  I'd like to use fluxbox, and if I put that in my .vnc/xstartup file,
>if I start anything else in that file (like gkrellm or panel), the Xvnc
>process will die. It has to be fluxbox, and only fluxbox.
>  Secondly, when I connect from another box using vncviewer (on
>Windows), colors are all messed up, and things don't redraw properly. I
>was wondering if anyone else had this problem. My machine's a pismo
>Powerbook.
>
>Thanks,
>Derek Greentree
>
>
>
>_______________________________________________
>gentooppc-user mailing list
>gentooppc-user@g.o
>http://lists.gentoo.org/mailman/listinfo/gentooppc-user
>
>.
>
>  
>



References:
vnc
-- Derek Greentree
Navigation:
Lists: gentoo-ppc-user: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
vnc
Next by thread:
rage128 fb
Previous by date:
vnc
Next by date:
xemacs ppc ebuild fail


Updated Jun 17, 2009

Summary: Archive of the gentoo-ppc-user mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.