For Fremantle users, there's now a 3.1-2fremantle4 release on the Garage download page and in Fremantle extras-devel.

Changes in this release:

• Fix a race condition between our installing a watch for MicroB startup and the startup itself, which might cause us to loop forever waiting for MicroB to start. (commit 1, commit 2)
• Make sure only one browser-switchboard process is active at any one time; this prevents a failure mode where hildon-desktop asks dbus-daemon to start another browser-switchboard in the window between our releasing the com.nokia.osso_browser D-Bus name and MicroB acquiring it, which was causing bewildering startup failures. (commit)

Many, many thanks to qwerty12, who provided feedback and eventually remote access to a device to help resolve these bugs.

Once again, the aim is for the following to work 100% of the time:

1. Configure Browser Switchboard with any default browser other than MicroB.
2. Restart the device.
3. Open a link from an application or a desktop widget; the link should open in the default browser you configured.
4. Open MicroB by using the Web menu entry (you don't need to change the default browser setting or restart the device).
5. Open a link from an application or a desktop widget; the link should open in MicroB.
6. Close all the MicroB browser windows.
7. Open a link from an application or a desktop widget; the link should open in the default browser you configured.
8. Open MicroB by using the Web menu entry (it should come up).

Please let me know whether this works consistently now or not, and whether or not you notice any other inconsistent or strange behaviors. If anything doesn't work as expected along the way, please let me know; if you can, open an xterm, run "killall browser-switchboard; browser-switchboard", go through the sequence of steps, and then provide the output that browser-switchboard produces in the terminal when reporting your problem.

Also, please report any problems you have with MicroB losing bookmarks, history, or settings when it's closed; a change to more heavy-handed measures for killing MicroB in a previous release may have introduced such bugs.

Assuming no one experiences problems (knock on wood), there should be a 3.2 release (for both Diablo and Fremantle) towards the end of this week.

Speaking of 3.2, I'm still looking for feedback regarding the proposed change in this post; if I don't hear any, I'll assume that no one objects and go ahead with it.