Community
Participate
Working Groups
- I generated metadata for 3.4 M2 and for I20071029-0800 in a local repo. - I provisioned a 3.4M2 SDK + end user UI using the RCP agent from HEAD (due to path problems in the donwloaded agent). - This SDK starts up fine, end user UI is there, etc. - I successfully added the releng tools (but was not prompted to restart/apply) - I restarted the SDK manually - I got the auto updates prompt and then saw that an update was available for the SDK - I tried to update to this version (from my local repo) - It did a lot of work (progress only showed in the details of the progress bar, not in the main progress bar) - It seemed to complete successfully - I was not prompted to restart
Investigate
The problem is a threading issue. The restart dialog is trying to open in a non-UI thread and before it hits the standard threading exception, it tries to look up an image with a null display. This could be fixed, but fixing it would open another can of worms given bug #208251, fixing it would likely cause a bunch of bogus restart dialogs to surface when sizing an install. This could be fixed, but..... ...I think it's best to address this for M4.
I added a workaround for bug #208251 so this dialog is back now.
*** Bug 210668 has been marked as a duplicate of this bug. ***