[Fresco-devel] Re: Fresco-devel digest, Vol 1 #201 - 1 msg

On Fri, 2003-04-25 at 04:31, [email protected] wrote:

> Is the cursor stuck before you run the client? Do you run the client
> directly from the server? (berlin -e fresco-demo) 
> 
> Are you running it from within X? If so, the title bar should say what
> 'console' of Berlin you're using: SDL or GGI, and whether using GL or
> not.

The error occurs when I am not running X, I should have been more clear
on that. The exact command I am using is:

bin/berlin --pixels=800x600 -e bin/fresco-demo

I'm forcing 800x600, any other resolution results in an error. 

However when running from X (GGI-on-X), the mouse does seem to work
okay, though it leaves big trails wherever the mouse travels (no redraw
after the mouse leaves an area) 

> Some people have reported problems where they can run the server ok, but
> the server gets 'stuck' on running a client.
> 
> Are you using the M2 source? I'm not sure if you might get more success
> using CVS, as I think some changes have gone in to reduce those problems
> (the kit-dependency solution by Stefan went in post-M2, right?)

I am using Fresco-030415 snapshot.. I'll try a newer version as well.

> 
> If you think you can handle it, try using the logging and tracing
> options, the latter requiring building with tracing enabled
> (--enable-tracer during configure). Use -l and -t to turn this on when
> running berlin; examine -h/--help if you want to see a few more options
> :)

I have used logging and tracing, but even using those didn't give me
much of a clue as to why the mouse would not work. I take it that this
is not a known problem? I'll keep playing around more to see what I can
find.

Regards,

John Morris