View Single Post
Posts: 114 | Thanked: 201 times | Joined on Apr 2009
#48
Originally Posted by qwerty12 View Post
After running "dbus-send --session --type=method_call --print-reply --dest="com.nokia.osso_browser" /com/nokia/osso_browser/request com.nokia.osso_browser.exit_browser":

[snip]
Hm, okay, so that suggests that (1) browser-switchboard isn't picking up the cue to send the exit_browser method call, (2) MicroB doesn't always close in response to the exit_browser call, or (3) the method call is getting lost in transit.

Originally Posted by qwerty12 View Post
OK, trying after rebooting and browser-switchboard running in the X Terminal...

Just rebooted; no attempts to open any browser.

[snip]
Yet there seems to be a browser-switchboard running before you start one from the shell? Somewhat strange.

Originally Posted by qwerty12 View Post
With the windows closed:

[snip]
With continuous mode off, it's normal for browser-switchboard to exit after closing MicroB (and possibly trying to kill browserd), so I'm not sure why you had to Ctrl-C it here.

Originally Posted by qwerty12 View Post
OK, so I couldn't reproduce it again. So I then opened the link again (in the same Browser Switchboard session). Success!

[snip]
Bother; that supports idea (2) or (3) above ("Closing MicroB" should be printed right before the method call, and the error message comes from the attempt to kill browserd, which occurs after the method call is issued). I was hoping to avoid a straight kill() for fear of data loss, but it looks like we'll have to see if that works more reliably.
 

The Following User Says Thank You to steven676 For This Useful Post: