touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Suspicious that Mir update 0.5.1 went out just before this bug was reported. And Mir 0.5.1 only contained one change:
https://code.launchpad.net/~andreas-pokorny/mir/fix-1346952/+merge/227993

** Also affects: mir
   Importance: Undecided
       Status: New

** Changed in: mir
    Milestone: None => 0.7.0

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

Title:
  Keyboard no longer works in Unity8 desktop session

Status in Mir:
  New
Status in “maliit-framework” package in Ubuntu:
  Invalid
Status in “mir” package in Ubuntu:
  New
Status in “qtmir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Incomplete
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  The keyboard no longer works in the Unity 8 desktop session.  Looking
  at the ~/.cache/upstart/unity8.log, it looks as though the socket
  Unity 8 is trying to connect to does not exist.  I see some of the
  following messages:

  UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer:
  Invalid name"

  then the last message says:

  Failed to connect to "/run/user/1001/ubuntu-keyboard-info" after 10
  failed attempts

  I looked in /run/user/1001 and did not see any file by that name.

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