← Back to team overview

touch-packages team mailing list archive

[Bug 1473720] Re: keyboard stops working, maliit and unity8 consuming cpu

 

Seems the problem was triggered by a change in qtubuntu, with the new
faster resizing implementation:

http://bazaar.launchpad.net/~phablet-team/qtubuntu/trunk/revision/266

For some reason this results in the keyboard surface stuck in a loop
constantly swapping buffers when returning to the messaging app (the
keyboard has to be visible prior to the image import from the camera
app, so that its surface gets resized when going to the fullscreen
camera and then back to the normal sized messaging window). With that
change reverted everything behaves normally.

** Description changed:

  Phone:
  Arale @ rc-proposed #61
  
  Reproduce:
  1. Open Messaging App
- 2. Tap camera icon
- 3. Take picture and accept it
+ 2. Start a conversation
+ 3. Tap messaging area to show keyboard
+ 4. Tap camera icon
+ 5. Take picture and accept it
  
  What happens:
  Keyboard goes away and does not come back when focusing the text input.
  
  What should happen:
  The keyboard should function normally
  
  Note: only a reboot seems to fix this

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1473720

Title:
  keyboard stops working, maliit and unity8 consuming cpu

Status in Canonical System Image:
  Confirmed
Status in qtubuntu:
  New
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Phone:
  Arale @ rc-proposed #61

  Reproduce:
  1. Open Messaging App
  2. Start a conversation
  3. Tap messaging area to show keyboard
  4. Tap camera icon
  5. Take picture and accept it

  What happens:
  Keyboard goes away and does not come back when focusing the text input.

  What should happen:
  The keyboard should function normally

  Note: only a reboot seems to fix this

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473720/+subscriptions


References