| Summary: | Google Signon UI takes ages to load | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] telepathy | Reporter: | David Edmundson <kde> |
| Component: | accounts-kcm | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | mklapetek |
| Priority: | NOR | ||
| Version: | git-latest | ||
| Target Milestone: | Future | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
David Edmundson
2015-04-11 11:19:07 UTC
Looks like a dbus timeout. Does that happen everytime? Can you provide a bustle/dferry log and possibly also the output of kcmshell5 kaccounts? Think it might have just been a slow network. seems fine today. Would be nice if it showed the window whilst it loaded. Indeed, signon-ui shows the dialog only on QWebView::loadFinished() signal, which isn't ideal. I'll see if that can be improved. For the record keeping purposes: <mck182> hey, what would you think about this patch for signon-ui https://paste.kde.org/p8w8onz9a <mck182> this way it appears immediately with the spinning wheel and it just happily spins away while the page is being loaded <mardy> I don't like it, because it often happens that once the webpage is loaded, it immediately redirects you to the callback page, and in that case the current code doesn't show any UI at all <mardy> the idea is that the client would use a spinner or some other indicator while performing the authentication <mardy> there's also an underused feature in signond, that lets authentication plugins send progress reports to the client <mardy> anyway, if you disagree, I don't mind having some #ifdef there <mardy> ah, but no, ifdef is not very good <mardy> there might be an Ubuntu machine where signon-ui is used by both KDE and Unity <mardy> maybe an enviornment variable, or config file? I think I'll just resort to set the whole UI to disabled and add some spinning wheels here and there. |