This bug was fixed in the package update-notifier - 0.130

---------------
update-notifier (0.130) raring; urgency=low

  [ Colin Watson ]
  * Only create a single GSettings instance for com.ubuntu.update-notifier,
    rather than several.
  * Remove unused u_abort function.
  * Make several more functions static that aren't used from other
    compilation units.
  * Correct a number of imprecise prototypes.
  * Defer instantiating GtkBuilders until the corresponding user interfaces
    actually need to be displayed, saving memory when they don't.
  * Restore code to keep a handle to crash and reboot notifications, so that
    they can be closed by later code (at least for notification-daemon
    users).
  * Fix several leaks of NotifyNotification objects.
  * Don't call show_hooks (which now includes instantiating the
    corresponding GtkBuilder) if there are no unseen hooks to show.

  [ Brian Murray ]
  * Remove calls to gnome-app-install and addon CD support (LP: #722887)
 -- Colin Watson <cjwat...@ubuntu.com>   Thu, 31 Jan 2013 03:32:33 +0000

** Changed in: update-notifier (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098235

Title:
  On screen Keybord non responsive for "Report problem" due to update-
  notifier using gksu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1098235/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to