Progress window on startup doesn't go away

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start raft.pyw, Ubuntu 10.10
2. Blank "Progress" window appears
3. Main Raft window appears
4. "Progress" window never disappears
5. "Progress" window cannot be closed (nothing happens)

What is the expected output? What do you see instead?
Progress window should disappear once main app is loaded

Please use labels and text to provide additional information.

Original issue reported on code.google.com by justinen...@gmail.com on 29 Mar 2011 at 5:29

[GoogleCodeExporter]

Could not verify in previous version of Ubuntu. Everything worked fine. The 
only place a progress dialog is shown on startup is the try statement starting 
on line 176 through 190 of raft.pyw. Perhaps there is a file writing or 
permissions issue not allowing the tool to write or overwrite previous versions 
of temp.db and reqtemp.db. Check permissions and try deleting previous temp.db 
and reqtemp.db files and try starting RAFT again. 

Original comment by nham...@gmail.com on 29 Mar 2011 at 6:26

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I've observed this behavior as well on all platforms.

This is probably related to  issue 2  and interactions with the main UI thread.

Original comment by gfleisch...@gmail.com on 29 Mar 2011 at 7:02

[GoogleCodeExporter]

Changing folder permissions, deleting temp.db and reqtemp.db made no difference.

I also tried putting print statements around the self.Progress.close() on 190, 
both of them output correctly, so it is reaching and successfully executing the 
finally block, just self.Progress.close() isn't actually closing the window.

The progress window DOES go away if you do something else that uses it, like 
load a file.  The window displays the bar (incorrectly), and then goes away 
when it should.

I'm baffled as to why it doesn't show up on NH's system, but it does on GF and 
JE's boxen.

Original comment by justinen...@gmail.com on 29 Mar 2011 at 8:31

[GoogleCodeExporter]

I haven't seen this occur in a while.  I believe it was fixed in some of the 
threading changes.

Ok to close?

Original comment by justinen...@gmail.com on 8 Aug 2011 at 8:13

[GoogleCodeExporter]

http://shakeydd.com/index.php/component/easyblog/entry/pop-3d-2015?Itemid=101

Original comment by bobfilm2...@gmail.com on 21 Apr 2015 at 4:37