← Back to team overview

touch-packages team mailing list archive

[Bug 1534541] Re: Dash doesn't accept input (appears frozen) after youtube scope auth

 

Some more observations / remarks:

- I cannot reproduce it with Facebook scope (which uses similiar auth scenario - i.e. a special card in the scope search results, as opposed to authentication from a preview).
- I cannot reproduce it with Ubuntu Store scope (which uses different auth scenario - from a preview).
- I'm able to reproduce with Youtube scope every time.

In all authentication scenarios the dash calls into online accounts api.
For the duration of authentication (i.e. when the auth prompt is
displayed), the dash runs a QEventLoop with disabled input processing,
so that it's not possible to interact with the dash until auth fails or
succeeds:

    QEventLoop loop;
    connect(&future_watcher, &QFutureWatcher<void>::finished, &loop, &QEventLoop::quit);
    loop.exec(QEventLoop::ProcessEventsFlag::ExcludeUserInputEvents);

This loop is stopped as soon as auth API finishes processing the prompt
(see http://bazaar.launchpad.net/~unity-team/unity-scopes-
shell/trunk/view/head:/src/Unity/logintoaccount.cpp).

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

Title:
  Dash doesn't accept input (appears frozen) after youtube scope auth

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  1. Make sure youtube scope is not favorited.
  2. Remove Google account from Accounts settings.
  3. Open youtube scope via Manage Dash
  4. Hit the orange 'Log-in to..' button
  5. Authenticate with google.
  6. Wait till youtube results are refreshed.

  The dash appears frozen now. It doesn't crash though, in fact the
  process is running and the dash responds to the dbus signal which
  invalidates current scope and forces a refresh (tested with dbus-send
  --session --type=signal '/com/canonical/unity/scopes'
  com.canonical.unity.scopes.InvalidateResults string:'clickscope').

  Note, the launcher as well as apps still receive input and work ok.

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


References