[Bug 310002] New: Frequently get the notification This Capability Is Not Available

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=310002

            Bug ID: 310002
          Severity: normal
           Version: 0.5.1
          Priority: NOR
          Assignee: kde-telepathy-bugs at kde.org
           Summary: Frequently get the notification This Capability Is Not
                    Available
    Classification: Unclassified
                OS: Linux
          Reporter: kde at davidedmundson.co.uk
          Hardware: Other
            Status: NEW
         Component: general
           Product: telepathy

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.