I'm having trouble with some latex documents, using the packages todonotes, tikz-cd and circuitikz (so I guess that tikz package is part of the problem).

The array elements within those environments are missplaced when okular displays the dvi file, while graphic elements as arrows and boxes are correclty displayed.

The problem doesn't seem to be from the latex compilation, because:
1) the same dvi file is correctly displayed by yast in a windows machine
2) the same dvi file, after dvips and ps2pdf, is correctly displayed by okular (I mean the resulting pdf file).

Could it be a a configuration issue of my okular? Or is ti something harder?

PS: I realized that okular can do backward search of pdf, so I can avoid dvi files. But I wonder if there is a better solution than that.

I would suspect that this is a bug in the DVI backend Okular is using, or it's integration with it.
Is it possible for you to provide the *.dvi file for testing?

I made a smaller file with just the environments causing trouble

http://dl.dropbox.com/u/9463081/tikzTest.dvi

I tested this file in yap (windows) and works ok, but it is displayed wrong by last version of okular on a PClinuxOS.

You can see the version my system rendered here - http://simplest-image-hosting.net/png-0-wb4065
I suspect it is wrong as well.

In this instance, assuming the texlive tools themselves work correctly, I would suggest filing a bug report at bugs.kde.org.

Yes, exactly the same that my okular displays.

But in yap, it renders as: https://www.dropbox.com/s/dfkjp86v5azrf4f/SceenShot.PNG

So, is it possible to correct it?

Anyway, now i'm doing it on pdf, and have no problem. But if you have any idea about how to correct this, please tell me.

Unfortunately I suspect it will require corrections in the source code.
You will need to file a bug report at bugs.kde.org regarding this. Please include the *.dvi file with this.

I found it was already pointed as a possible bug by august 2012 https://bugs.kde.org/show_bug.cgi?id=305713
it is still considered as unconfirmed, so I added my example.

Greetings,

Germán

To help other users who find this topic in the future, could you please paste a link to the bug report in question?