[Bug 353372] Re: BOINC patch 003 launches the wrong browser

[Joseph Stateson]

My mistake - I should have downloaded the tag 6.10.43 (instead of trunk)
and indeed your patch is there as well as in the apt-get source you
suggested I use.

I cannot use 6.2.12 as these systems run CUDA and need latest or
recommended boinc.  From the boinc web site I downloaded 6.10.43 and
copied the binaries over to /usr/bin, at least for the system running
9.1  For the system running Dotsch_UX I used the 6.10.17 that the author
supplied.  Both have the problem with launching the project url.  At
least the Dotch_UX does not cause other problems (see last url)

So ExecuteLink was patched - I assume that patch was in the debian code?  IANE on linux, but, reading the bug description at the top I quote " this patch is less than helpful when using Ubuntu, since Epiphany is not installed by default.
It should at least default to firefox or, ideally, use /etc/alternatives/x-www-browser."   That seems to be the problem - there is no default to firefox or it does not work.  So what can be done to get this problem identified and fixed?  The problem that I want to report is that when firefox is selected in that default app dialog, it does NOT get launched by boincmgr.  In looking thru http://www.xaraxtreme.org/maillists/archive/dev/dev_052006/msg00348.html  I see where vfs.keys had to be edited and Epiphany replaced with the desired browser (for email links to work).  What is more interesting is that firefox is not one of the 6 or so listed browsers in that vfs.keys source.

Anyway, this is really a minor problem and can be worked around by
selecting any of the other browsers listed in that default apps program.
I picked Epiphany as I see it is the gnome default.

  There are much worse bugs to solve.  Currently, I had to go back to
8.1 (from 9.1) because of bugs involving CUDA devices. hsee
ttp://boinc.berkeley.edu/dev/forum_thread.php?id=5562

-- 
BOINC patch 003 launches the wrong browser
https://bugs.launchpad.net/bugs/353372
You received this bug notification because you are a member of Debian
BOINC Maintainers, which is subscribed to boinc in ubuntu.