For the time being, I've worked around this bug by creating my own wrapper around mozilla-runtime.
I dpkg-diverted mozilla-runtime out of the way:
sudo dpkg-divert --local --add --rename /usr/lib/xulrunner-1.9.3a4pre/mozilla-runtime
I then created in a text editor (nano) and marked executable (chmod +x ) a new mozilla-runtime with the following contents:
#!/bin/sh
export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.3a4pre/:$LD_LIBRARY_PATH
exec /usr/lib/xulrunner-1.9.3a4pre/mozilla-runtime.distrib $@
It seems mozilla-runtime is being called with neither PATH nor LD_LIBRARY_PATH containing the xulrunner directory.
Once we get an official fix, you can undo my changes by deleting the custom "mozilla-runtime" wrapper, and then un-diverting the original:
sudo dpkg-divert --local --remove --rename /usr/lib/xulrunner-1.9.3a4pre/mozilla-runtime
For the time being, I've worked around this bug by creating my own wrapper around mozilla-runtime.
I dpkg-diverted mozilla-runtime out of the way: xulrunner- 1.9.3a4pre/ mozilla- runtime
sudo dpkg-divert --local --add --rename /usr/lib/
I then created in a text editor (nano) and marked executable (chmod +x ) a new mozilla-runtime with the following contents: PATH=/usr/ lib/xulrunner- 1.9.3a4pre/ :$LD_LIBRARY_ PATH xulrunner- 1.9.3a4pre/ mozilla- runtime. distrib $@
#!/bin/sh
export LD_LIBRARY_
exec /usr/lib/
It seems mozilla-runtime is being called with neither PATH nor LD_LIBRARY_PATH containing the xulrunner directory.
Note that since I have overridden mozilla-runtime, apport now gives me "This report does not apply to a packaged program": /bugs.launchpad .net/apport/ +bug/83105
https:/
Once we get an official fix, you can undo my changes by deleting the custom "mozilla-runtime" wrapper, and then un-diverting the original: xulrunner- 1.9.3a4pre/ mozilla- runtime
sudo dpkg-divert --local --remove --rename /usr/lib/