Re: [DMX-Devel] Chromium and DMX beginner troubles

Andres Felipe Molina Villamizar wrote:
> The only way to get DMX to run is when each node is started in TWM. When =

> logged in Gnome or KDE it fails to connect? Any particular reason?

You shouldn't run a window manager on the back-end nodes.  It's =

superfluous and would likely give strange visual artifacts anyway.  (I'm =

not sure whether DMX operates in OverrideRedirect mode on the back-ends.)

> Once DMX runs, UI elements such as icons and text don=92t show up properl=
y =

> (specially under Gnome). Only way to make it visualize properly is to =

> use the =96norender parameter when running the Dmx command (just two =

> displays for testing purposes):
> =

> $ startx -- /usr/bin/Xdmx :1 =96display guaviare:0 =96display guaviare3:0 =

> +xinerama -norender

That's correct.  However, I think this problem has been alleviated by =

the recent X.org builds.  What version of DMX are you running, code from =

the deprecated DMX sourceforge web site, or the DMX that comes from the =

X.org code tree?  More precisely, what DMX is yum giving you?

> I am unable to run chromium once DMX is running. I followed the steps =

> detailed in the chromium docs page (manual run), but I get the following =

> message from the mothership:
> =

> $ CR Warning(guaviare:22281): Tilesort bucket_mode =3D Non-Uniform Grid, =

> but tiles don't form a non-uniform grid!  Falling back to Test All Tiles =

> mode.

That's not a problem, it's just a warning.  And you'll get it when your =

chromium configuration forms a non-uniform grid.  Some powerwalls =

(TwinView comes to mind) are designed like this.  If yours is not, if it =

truly is a uniform grid, then you have a bug somewhere in your chromium =

config file.

Have you been able to successfully run Chromium across your system =

without DMX in the picture?  That's a good "walk before you run" test.

> And the following repeated message from the crserver on guaviare3:
> =

> $ CR Warning(guaviare3:10322): Render SPU: render_to_app/crut_window =

> option is set but the window ID 0x1400002 is invalid on the display =

> named guaviare3:0.0

Not sure why you would have a CRUT problem.  Why are you setting CRUT =

options?  I would try running a serial non-CRUT application first =

(glxgears comes to mind) before you try anything more complex.

-Sean

__
Sean Ahern
Oak Ridge National Laboratory
AIM: ornlsean
865-241-3748


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/