Using a different (and fresh) profile did not help. The FW Tools variant
behaves the same way as OpenEV. It is beginning to look like a Windows
problem but everything else works; only OpenEV and variants fail. Wait, is
that music I hear? and that voice - it sounds like Rod Serling. Nah, there
has to be a logical explanation. :-)
On Mon, 2 Oct 2006, Claude Marinier wrote:
> Created a BAT file for testmain.py patterned after openev.bat. Executing
> this produces a small blank window (landscape orientation) with a title
> matching the program name. It also produces a tall narrow blank Layers
> window. After that it hangs. No revelation here.
> The program gvtest.exe produces an empty 'DOS box' and hangs. While
> waiting, I had a look at the contents of all the shared drives without
> problem. One odd thing is that the cursor (which was over Windows
> Explorer) was cycling between the normal arrow and the hourglass about
> once per second; with each cycle, some of the lines in the left pane
> were redrawn (only the lines after the local drives starting with the
> shares were redrawn).
> Next steps
> - try the FW Tools build, and
> - may try with a fresh profile (just because the profile is one
> of the usual suspects).
> Thank you.
> On Wed, 20 Sep 2006, Steve Rawlinson wrote:
>> I haven't seen that specific problem before but I have seen OpenEV hang
>> on Windows at the file Open dialog. It happens when GTK tries to get a
>> list of the drives on the PC but one of a network drive is not
>> accessible. Eventually it times out after a minute or two. I'm not
>> sure how long you have tried waiting, but you could trying leaving it
>> for a while to see if whatever is hung eventually times out.
>> Other thoughts:
>> - Try running gvtest.exe (usually in the Openev\bin directory). This
>> is a very basic version of OpenEV written entirely in C (no Python).
>> If it works then you know OpenEV, GTK and OpenGL are working, and it
>> may be something at the Python level that is broken.
>> - Try running OpenEV\pymod\testmain.py - you will need to setup your
>> environment with something like the openev.bat script otherwise you
>> will get a gtk.dll error.
>> - Where did your OpenEV build come from? Does the problem happen with
>> both the FW Tools build, and the version from SourceForge?
>> - You may have already asked this question, but has anything on the PC
>> changed recently that might give a clue as to the problem? (new video
>> drivers, newly installed software or hardware?)
>> - If you don't mind getting into the Python code a bit, look at
>> OpenEV\pymod\openev.py and try putting some print statements or tracing
>> though the functions to narrow down where it is getting hung.
>> That's all I can think of for now. It's certainly a strange problem,
>> and one that I have never encountered before.
>> On Wed, 13 Sep 2006, Claude Marinier wrote:
>> > OnenEV is working well on a few PCs except one which started
>> > misbehaving after working for some time. We deleted OpenEV and
>> > re-installed it but that did not help. The OS is MS Windows XP. We
>> > are using a recent version of OpenEV.
>> > When we start OpenEV, the command line window echos paths to a bunch
>> > of Python scripts, the Layers windows pops-up, then the program
>> > hangs. We have to kill it with the Windows Task Manager.
>> > Has anyone seen this and found a solution?
>> > Can someone suggest a test that will help discover the cause of this?
>> > I am planning to run a small Python-GTK program to verify that Python
>> > and GTK are running properly. We ran a Python program in the test
>> > sub-directory; it ran with a few complaints about skipping tests
>> > because it could not find the corresponding module.
>> > Help is appreciated. Thank you.
Claude Marinier, Information Technology
Defence Research & Development Canada (Ottawa)
Telephone: (613) 998-4901