Notices

Originally Posted by steven676

Firstly, did you restart your device after installing Browser Switchboard? If not, try that before doing anything else.

If restarting doesn't help, then try the following:

1. Upgrade to Browser Switchboard 3.1-2fremantle1. (This shouldn't solve your problem, but it will make finding the problem easier.)
2. Open an X Terminal, then type the following, pressing Enter after each line (the $ is a prompt that will be displayed to you, not something you type):
   
   Code:

   $ killall browser-switchboard
   $ browser-switchboard

   You should get output that looks something like this:
   
   Code:

   continuous_mode: 0
   default_browser: 'fennec'
   other_browser_cmd: 'NULL'
   Starting main loop

3. Try to open one of your home screen bookmarks.
4. Assuming it doesn't work, copy all of the stuff Browser Switchboard writes to the xterm and post it here so that I can have a look at it.

Originally Posted by jlacombe

I certainly appreciate your help. Here is what I get after I follow your instructions....

continuous_mode: 1
default_browser: 'fennec'
other_browser_cmd: 'NULL'
Couldn't acquire name com.nokia.osso_browser

JL

Originally Posted by luca

I can't thank you enough for browser-switchboard, but at the same time I cannot forget that on a sane platform all this contortions shouldn't be necessary.

Originally Posted by steven676

Hopefully the following should now 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).

Originally Posted by jukey

I repeated the produce step by step after "killall browser-switchboard; browser-switchboard" but without a complete restart of the device. This time after step 4 again only the initial bookmark page is shown. No empty page.

This is the output:

Code:

~ $ killall browser-switchboard
~ $ browser-switchboard        
continuous_mode: 1
default_browser: 'fennec'
other_browser_cmd: 'NULL'
Starting main loop
open_address 'http://maemo.org/packages/repository/qa/fremantle_extras-testing/'
launch_other_browser with uri 'http://maemo.org/packages/repository/qa/fremantle_extras-testing/'
command: 'fennec 'http://maemo.org/packages/repository/qa/fremantle_extras-testing/''
Waited for a zombie
launch_microb with uri 'new_window'
Waiting for MicroB to start
Checking to see if MicroB is ready
Message has only 0 arguments, but more were expected

Originally Posted by steven676

Okay, I'm not 100% sure I understand what happened here, but I am pretty sure it starts from a state which Browser Switchboard shouldn't end up in (MicroB running, but not handling com.nokia.osso_browser). Can you please try this again with a freshly restarted device?

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).

Originally Posted by jukey

The problem seems to be that you are not killing the microb browserdeamon after the last microb window is closed.

Originally Posted by jukey

Is a system message (don't know the correct word for that) sent if the last browser windwo closed?

Originally Posted by jukey

What is the next step I can do to help you?

Originally Posted by steven676

If steps 1-8 outlined in my previous post actually work correctly 100% of the time for anyone on Fremantle, could you please speak up with your firmware version? (Failure reports would be appreciated as well, but success reports would be more puzzling.)



Bingo. What we're supposed to see after "MicroB ready" is this:

Code:

Checking to see if we should kill MicroB
Checking to see if we should kill MicroB
Closing MicroB

(which has been observed at least once in the wild -- which makes this report rather troubling).



Is any documented signal sent when the last window closes? Not that I know of. I'm relying on behavior gleaned from tracing MicroB in the SDK to determine when the last browser window closes. Clearly, at least in your case, that behavior is not happening.



Can you repeat steps 1 to 6, and this time, find the PIDs for browserd ("ps -ef | grep browserd") before step 4

, after step 4,

and after step 6?

(In the SDK, there are two browserds after step 4, and one of them closes and is replaced after step 6; it's this change that I have several ways of looking for. If this isn't happening consistently on the device, we're back to square 1 ...)

Originally Posted by jukey

Sounds like the SDK does the same as the device itself? Or did I misunderstand "one of them closes and is replaced after step 6"?