| Summary: | Frequently get the notification This Capability Is Not Available | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | David Edmundson <kde> |
| Component: | general | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | heri+kde, mklapetek, razorx |
| Priority: | NOR | ||
| Version: | 0.5.1 | ||
| Target Milestone: | Future | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I also sometimes get this notification. Often this happens after login, before entering the KWallet password. The error message that is presented to me appears to be random. Sometimes it is an authentication failure, sometimes a network error (?, iirc), sometimes an unavailable capability. (In reply to comment #1) > I also sometimes get this notification. Often this happens after login, > before entering the KWallet password. That is WRONG. My memory played tricks on me. I get this after returning the computer from standby. I immediately get notifications for almost all accounts about the capability issue. One account reports an authentication problem instead. The issue persists with Telepathy/KDE 0.5.2. Are you behind a wifi that requires you to sign in? do you use NetworkManager? (In reply to comment #4) > Are you behind a wifi that requires you to sign in? do you use > NetworkManager? yes. yes. I am within a WiFi, which is (locally) managed by NetworkManager. I do not need to enter a password for it, because it is saved by the NetworkManager (in KWallet?). When my laptop returns from standby, I usually get a bunch of these messages, before it actually connects. I am starting to get this on login. Even if I remove my kwallet password I get this error. It still connects to my accounts, so I have no idea why this pops up. Does this still happen in 0.5.80? Please reopen if you see it. A year with no comment, closing this. Please open a new bug report as this is about a Telepathy error being misinterpreted. |
Summary: 1) This error message is wrong. 2) It's caused by the backends incorrectly reporting network errors To reproduce: - disconnect from the network - disable NM (just so you can connect with MC being NM aware) - try and connect and account Error is: connectionStatusReason = 0 = ConnectionStatusReasonNoneSpecified connectionError: "org.freedesktop.Telepathy.Error.NotAvailable" connectionErrorDetails: QMap(("debug-message", QVariant(QString, "g-resolver-error-quark (#0): couldn't connect to server: Error resolving 'chat.facebook.com': Name or service not known") ) ) this is displayed as "this capability is not available" Error Dictionary has: } else if (dbusErrorName == QLatin1String(TP_QT_ERROR_NOT_AVAILABLE)) { return i18nc("Verbose user visible error string", "This capability is not available"); and } else if (dbusErrorName == QLatin1String(TP_QT_ERROR_NOT_AVAILABLE)) { return i18nc("Short user visible error string", "Capability not available"); The spec has no mention of this being to do with capabilities. Spec says: " The requested channel type cannot be created with the given handle" The backend is being particularly unhelpful here by not reporting it as a network error and instead reports the error as type "None Specified" We need to: 1) Reword this error message to be correct 2) Treat it as a network error (that way we go through the "network manager is online code") This will reduce the problems, but won't fix all of them. For example cases where you're at a wifi that requires you to sign in after you've connected (such as those you find at an airport). Longterm I think we need to rethink what error messages need showing and how, but lets keep this bug report specifically on the problem of the "This capability is not available" bug.