uDIG

Linux MOZILLA_FIVE_HOME required for Information tool

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: UDIG 1.0.6, UDIG 1.1.M5
  • Fix Version/s: UDIG 1.2.M6
  • Component/s: tools and editing, webservices
  • Labels:
    None
  • Environment:
    Centos4 (RHEL4 equivalent), uDig-bundled JRE, uDig 1.1M6 (also reproducable under uDig 1.0.x)

Description

The Information Tool does not work, at least not with WMS layers though I suspect it's non-functional for all layer types.

Under v1.1M6 I can't get the Information Tool to show up in the toolbar at all. Going to Window > Show View > Other... and selecting "Information" from the list doesn't give me a new Information view. No error windows pop-up either. If I run udig via the commandline I get the following output there:

Unhandled event loop exception
Reason:
No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]

Under v1.0.x the problem is slightly different: the Information Tool shows up in the toolbar but selecting it and then clicking on a layer does nothing. No user feedback whatsoever. Again, when running udig from the commandline the same messages are printed as above when clicking with the Information tool:

Unhandled event loop exception
Reason:
No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
This is actually a problem using using the internal browser, you should be able to set things up a bit
better in the windows preference page.

I know Jesse has some experience both good and bad with using an embded browser on linux. Richard is
also a linux user so I will assign this bug to him.
Show
Jody Garnett added a comment - This is actually a problem using using the internal browser, you should be able to set things up a bit better in the windows preference page. I know Jesse has some experience both good and bad with using an embded browser on linux. Richard is also a linux user so I will assign this bug to him.
Hide
Permalink
Jody Garnett added a comment -
This may need to be a change the installation instructions for uDig, is there anyway we can refuse to start without MOZILLA_FIVE_HOME set?
Show
Jody Garnett added a comment - This may need to be a change the installation instructions for uDig, is there anyway we can refuse to start without MOZILLA_FIVE_HOME set?
Hide
Permalink
Corey Puffalt added a comment -
I think it would be preferable to:

a) Pop-up an error dialog notifying the user of the problem for any operation that requires the embedded browser. In the current situation there's no user feedback: nothing visible happens which is very frustrating for the user.

b) Make the Mozilla home location configurable within the uDig gui. (uDig could also make some educated guesses on the location out of the box.)

Show
Corey Puffalt added a comment - I think it would be preferable to: a) Pop-up an error dialog notifying the user of the problem for any operation that requires the embedded browser. In the current situation there's no user feedback: nothing visible happens which is very frustrating for the user. b) Make the Mozilla home location configurable within the uDig gui. (uDig could also make some educated guesses on the location out of the box.)
Hide
Permalink
Richard Gould added a comment -
You are right - uDig should make a guess, and let the user configure it.

There are a couple eclipse bugs on this but I am not sure they help at all.
This problem is really Eclipse specific, not uDig specific. Perhaps we could propagate the change up to them..

I will try and fix this in a week or so.
Show
Richard Gould added a comment - You are right - uDig should make a guess, and let the user configure it. There are a couple eclipse bugs on this but I am not sure they help at all. This problem is really Eclipse specific, not uDig specific. Perhaps we could propagate the change up to them.. I will try and fix this in a week or so.
Hide
Permalink
Richard Gould added a comment -
More details about MOZILLA_FIVE_HOME. It seems that eclipse looks for "libgtkembedmoz.so" library, so perhaps a uDig start up script could try and locate this library automatically
Show
Richard Gould added a comment - More details about MOZILLA_FIVE_HOME. It seems that eclipse looks for "libgtkembedmoz.so" library, so perhaps a uDig start up script could try and locate this library automatically
Hide
Permalink
Richard Gould added a comment -
Jesse mentioned that all that might be required to fix this is to move the information tool's view to the newer browser API
Show
Richard Gould added a comment - Jesse mentioned that all that might be required to fix this is to move the information tool's view to the newer browser API
Hide
Permalink
Jody Garnett added a comment -
Peter writes on email:

I write this so that the archive will contain this information.

I have successfully managed to get the info window working under Linux
(Slackware 11.0, xfce) using Firefox 2.0.0.3. Here's what I did:

1. Download the 2.0.0.3 mozilla source tree from
<ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.3/source/firefox-2.0.0.3-source.tar.bz2>
(that should be all one line between the <>'s)
Unpack in /usr/local/src (installs as /usr/local/src/mozilla)

2. cd /usr/local/src/mozilla

3. Following instructions at
  http://developer.mozilla.org/en/docs/Configuring_Build_Options
  Create .mozconfig as follows:
(.mozconfig begins)
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-@CONFIG_GUESS@
. $topsrcdir/browser/config/mozconfig

ac_add_options --enable-optimize
ac_add_options --disable-debug

ac_add_options --enable-default-toolkit=gtk2
ac_add_options --enable-xft

ac_add_options --disable-static --enable-shared
(.mozconfig ends)

4. make -f client.mk build

5. cd obj-i686-pc-linux-gnu; su; make install

This install creates /usr/local/include/firefox-2.0.0.3
 /usr/local/lib/firefox-2.0.0.3
and puts a few files into
 /usr/local/lib/pkgconfig/
 /usr/local/bin
 /usr/local/share/idl

6. I run udig from xfce using a launcher that points not to udig itself
but instead to a small shell script I named /usr/local/udig/udig-start:

(udig-start begins)
#!/bin/bash

export MOZILLA_FIVE_HOME=/usr/local/lib/firefox-2.0.0.3
export LD_LIBRARY_PATH=/usr/local/lib/firefox-2.0.0.3

/usr/local/udig/udig -vmargs -Xmx1536m
(udig-start ends)

And the info window now appears when I click on a feature. Whew!

The reason why I used this launcher script is that for normal web
browsing I use the Firefox package the Slackware provides, which
is installed in /usr/lib/firefox-2.0.0.3 (with a symlink called
/usr/lib/firefox).

Peter
Show
Jody Garnett added a comment - Peter writes on email: I write this so that the archive will contain this information. I have successfully managed to get the info window working under Linux (Slackware 11.0, xfce) using Firefox 2.0.0.3. Here's what I did: 1. Download the 2.0.0.3 mozilla source tree from <ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.3/source/firefox-2.0.0.3-source.tar.bz2> (that should be all one line between the <>'s) Unpack in /usr/local/src (installs as /usr/local/src/mozilla) 2. cd /usr/local/src/mozilla 3. Following instructions at   http://developer.mozilla.org/en/docs/Configuring_Build_Options   Create .mozconfig as follows: (.mozconfig begins) mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-@CONFIG_GUESS@ . $topsrcdir/browser/config/mozconfig ac_add_options --enable-optimize ac_add_options --disable-debug ac_add_options --enable-default-toolkit=gtk2 ac_add_options --enable-xft ac_add_options --disable-static --enable-shared (.mozconfig ends) 4. make -f client.mk build 5. cd obj-i686-pc-linux-gnu; su; make install This install creates /usr/local/include/firefox-2.0.0.3  /usr/local/lib/firefox-2.0.0.3 and puts a few files into  /usr/local/lib/pkgconfig/  /usr/local/bin  /usr/local/share/idl 6. I run udig from xfce using a launcher that points not to udig itself but instead to a small shell script I named /usr/local/udig/udig-start: (udig-start begins) #!/bin/bash export MOZILLA_FIVE_HOME=/usr/local/lib/firefox-2.0.0.3 export LD_LIBRARY_PATH=/usr/local/lib/firefox-2.0.0.3 /usr/local/udig/udig -vmargs -Xmx1536m (udig-start ends) And the info window now appears when I click on a feature. Whew! The reason why I used this launcher script is that for normal web browsing I use the Firefox package the Slackware provides, which is installed in /usr/lib/firefox-2.0.0.3 (with a symlink called /usr/lib/firefox). Peter
Hide
Permalink
Jody Garnett added a comment -
So now that we use Eclipse 3.4 can we move the info tool to the new browser API? (Of course I would like a link telling me what the new browser API is?)
Show
Jody Garnett added a comment - So now that we use Eclipse 3.4 can we move the info tool to the new browser API? (Of course I would like a link telling me what the new browser API is?)

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.