1 |
Hi folks, |
2 |
Here's some of the stuff I've uncovered. Looking around on Google, |
3 |
some people have mentioned similar problems (but they were a long time |
4 |
ago - October 2000), dealing with various endianness issues and the r128 |
5 |
framebuffer driver. I'll poke around more, but so far on my pismo both |
6 |
vnc (tightvnc and regular vnc) and mplayer will display incorrectly: |
7 |
tightvnc and mplayer display with a strange yellow tint, and regular vnc |
8 |
looks like it's being drawn with an 8-bit depth, even though |
9 |
investigation shows that it's not. |
10 |
|
11 |
Thanks, |
12 |
Derek |
13 |
|
14 |
On Mon, 2002-05-06 at 08:30, Derek Greentree wrote: |
15 |
> Hi all, |
16 |
> I've tried this with tightvnc and regular vnc ebuilds: I emerge |
17 |
> (tight)vnc, and after tweaking the font path settings, I got vncserver |
18 |
> to launch an actual Xvnc process that wouldn't die. However, I'm having |
19 |
> 2 problems: |
20 |
> I'd like to use fluxbox, and if I put that in my .vnc/xstartup file, |
21 |
> if I start anything else in that file (like gkrellm or panel), the Xvnc |
22 |
> process will die. It has to be fluxbox, and only fluxbox. |
23 |
> Secondly, when I connect from another box using vncviewer (on |
24 |
> Windows), colors are all messed up, and things don't redraw properly. I |
25 |
> was wondering if anyone else had this problem. My machine's a pismo |
26 |
> Powerbook. |
27 |
> |
28 |
> Thanks, |
29 |
> Derek Greentree |
30 |
> |
31 |
> |