View Single Post
Posts: 114 | Thanked: 201 times | Joined on Apr 2009
#74
Originally Posted by qwerty12 View Post
After doing the above steps once, opening the Browser from the menu again and noticing that oddity above, I closed the browser. When I went to open the Browser using the menu entry, Tear popped up so I closed it.
Okay, I understand this now. Occasionally, dbus-daemon decides that it has to have something handling com.nokia.osso_browser at all times; thus, when we release the name (waiting for MicroB to pick it up), it starts the program in the service definition (another copy of browser-switchboard). This results in the second browser-switchboard handling the load_url request coming from the first -- which causes the browser-switchboard default browser (in this case Tear) to come up.

EDIT: no, hildon-desktop is requesting this:
Code:
$ dbus-monitor
[snip]
method call sender=:1.35 -> dest=org.freedesktop.DBus serial=291 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "com.nokia.osso_browser"
   uint32 0
[snip]
$ dbus-send --session --print-reply --type=method_call --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID string:":1.35"
method return sender=org.freedesktop.DBus -> dest=:1.535 reply_serial=2
   uint32 1123
$ ps -ef | grep 1123
 1123 user      108m S    /usr/bin/hildon-desktop
Not sure how to stop this from happening, but I suppose we could use some form of locking to make sure that the second browser-switchboard doesn't get in the way.

Last edited by steven676; 2010-02-15 at 07:08.
 

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