raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as Won't Fix.
** Changed in: gnome-screensaver (Ubuntu Raring)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: gnome-screensaver
Status: New = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088495
Title:
Onboard Keyboard is sometimes nonresponsive in Raring while unlocking
** Changed in: ubuntu-nexus7
Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088495
Title:
Onboard Keyboard is sometimes
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088495
Title:
Onboard Keyboard is sometimes nonresponsive in Raring while unlocking
screen
To manage notifications about this
** Changed in: gnome-screensaver
Status: Unknown = New
** Changed in: gnome-screensaver
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088495
Title:
Onboard
So no, Onboard isn't the cause. The unlock dialog's buttons still lock
up when Onboard isn't embedded into the screensaver.
The ultimate cause most likely lies within gnome-screensaver itself,
there is a lot of pointer grabbing going on during normal operation.
However, the trigger seems to be
** Bug watch added: GNOME Bug Tracker #690244
https://bugzilla.gnome.org/show_bug.cgi?id=690244
** Also affects: gnome-screensaver via
https://bugzilla.gnome.org/show_bug.cgi?id=690244
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Confirming, I've seen this too. However I'm not convinced yet this is
Onboard's doing. When it happens here, the whole screen becomes
unresponsive, including the buttons of the unlock dialog. This doesn't
happen when I plug Onboard into any other XEmbed socket. Not saying
Onboard is necessarily
** Also affects: onboard (Ubuntu)
Importance: Undecided
Status: New
** Changed in: onboard (Ubuntu)
Importance: Undecided = High
** Also affects: onboard (Ubuntu Raring)
Importance: High
Status: New
--
You received this bug notification because you are a member of Ubuntu
