[ubuntu-mono] [Bug 538796] Re: cannot open Firefox/Chromium/Google Chrome when libmoon is installed

Launchpad Bug Tracker 538796 at bugs.launchpad.net
Wed Feb 23 20:36:33 UTC 2011


This bug was fixed in the package moon - 2.3-0ubuntu4.1

---------------
moon (2.3-0ubuntu4.1) maverick-proposed; urgency=low

  * Fix LP: #538796 - cannot open Firefox/Chromium/Chrome when moonlight
    is installed, due to a symbol collision with the icedtea plugin. Thanks
    to Evan Martin and Chris Toshok for figuring this out
    - add debian/patches/avoid_icedtea_symbol_collision.patch
    - update debian/patches/series
 -- Chris Coulson <chris.coulson at canonical.com>   Mon, 31 Jan 2011 16:26:09 +0000

** Changed in: moon (Ubuntu Maverick)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to moon in ubuntu.
https://bugs.launchpad.net/bugs/538796

Title:
  cannot open Firefox/Chromium/Google Chrome when libmoon is installed

Status in Chromium:
  Invalid
Status in “moon” package in Ubuntu:
  Fix Released
Status in “moon” source package in Lucid:
  Fix Released
Status in “moon” source package in Maverick:
  Fix Released
Status in “moon” source package in Natty:
  Fix Released
Status in “moon” source package in Karmic:
  Fix Committed

Bug description:
  after installing Shockwave via mozplugger I deleted pluginreg.dat and tried to boot firefox. as opposed to auto-generating the file, firefox crashes. after running firefox in terminal noticed "user at SDF-1:~$ firefox
  Attempting to load the system libmoon 
  Segmentation fault (core dumped)"

  proceeded to uninstall moon packages and firefox then behaves as
  intended.

  after doing a clean install I attempted to recreate the bug without
  the presence of other non-default packages and proceeded to install
  moonlight and then deleted pluginreg.dat from firefox to the same
  results.

  I am using the current 3/13/10 daily-build of lucid 64bit
  I apologize for the lack of an apport bug report but it doesn't seem to be working right now.



More information about the Ubuntu-mono mailing list