dx-packages team mailing list archive

[Launchpad Bug Tracker <1222828@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package libunity -
7.1.1+13.10.20130918.1-0ubuntu1

---------------
libunity (7.1.1+13.10.20130918.1-0ubuntu1) saucy; urgency=low

  [ Michal Hruby ]
  * Allow permanent scope "removal" just by using dconf.
  * Make sure libunity-tool doesn't crash when it can't connect to the
    bus. (LP: #1219792)

  [ Pawel Stolowski ]
  * Check actual return value of GLib.Module.open to avoid assertion
    errors and fail early rather than on get_version check later. (LP:
    #1222828)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 290
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Wed, 18 Sep 2013 07:54:38 +0000

** Changed in: libunity (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1222828

Title:
  unity-scope-loader doesn't handle missing modules correctly

Status in LibUnity:
  Fix Committed
Status in “libunity” package in Ubuntu:
  Fix Released

Bug description:
  unity-scope-loader doesn't correctly handle return value of
  GLib.Module.open(). If module is missing, it fails at a later stage
  when checking module version, which produces assertion errors on
  module != NULL and a misleading error about missing get_version
  function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1222828/+subscriptions