Warning, /network/telepathy-logger-qt/spec/errors.xml is written in an unsupported language. File is not indexed.

0001 <?xml version="1.0" ?>
0002 <tp:errors xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0" namespace="org.freedesktop.Telepathy.Error">
0003 
0004   <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
0005     <p>The D-Bus errors used in Telepathy all start with
0006       <code>org.freedesktop.Telepathy.Error.</code>. They are used in
0007       D-Bus messages of type ERROR, and also as plain strings annotated with
0008       the <tp:type>DBus_Error_Name</tp:type> type.</p>
0009 
0010     <p>In principle, any method can raise any error (this is a general fact
0011       of IPC). For instance, generic D-Bus errors starting with
0012       <code>org.freedesktop.DBus.Error.</code> will occur in some
0013       situations.</p>
0014 
0015     <p>Telepathy methods can also raise implementation-specific errors to
0016       indicate specialized failure conditions. For better interoperability,
0017       if a suitable Telepathy error exists, it should be preferred.</p>
0018 
0019     <p>The namespace <code>org.freedesktop.Telepathy.Qt4.Error.</code>
0020       is reserved for use by the D-Bus client implementation in telepathy-qt4,
0021       which uses it to represent certain error situations that did not involve
0022       a D-Bus ERROR message. These errors are defined and documented as part of
0023       telepathy-qt4's C++ API, and should not be used on D-Bus.</p>
0024   </tp:docstring>
0025 
0026   <tp:error name="Network Error">
0027     <tp:docstring>
0028     Raised when there is an error reading from or writing to the network.
0029     </tp:docstring>
0030   </tp:error>
0031 
0032   <tp:error name="Not Implemented">
0033     <tp:docstring>
0034     Raised when the requested method, channel, etc is not available on this connection.
0035     </tp:docstring>
0036   </tp:error>
0037 
0038   <tp:error name="Invalid Argument">
0039     <tp:docstring>
0040     Raised when one of the provided arguments is invalid.
0041     </tp:docstring>
0042   </tp:error>
0043 
0044   <tp:error name="Not Available">
0045     <tp:docstring>
0046     Raised when the requested functionality is temporarily unavailable.
0047     </tp:docstring>
0048   </tp:error>
0049 
0050   <tp:error name="Permission Denied">
0051     <tp:docstring>
0052     The user is not permitted to perform the requested operation.
0053     </tp:docstring>
0054   </tp:error>
0055 
0056   <tp:error name="Disconnected">
0057     <tp:docstring>
0058       The connection is not currently connected and cannot be used.
0059       This error may also be raised when operations are performed on a
0060       Connection for which
0061       <tp:dbus-ref namespace="org.freedesktop.Telepathy.Connection">StatusChanged</tp:dbus-ref>
0062       has signalled status Disconnected for reason None.
0063 
0064       <tp:rationale>
0065         The second usage corresponds to None in the
0066         <tp:type>Connection_Status_Reason</tp:type> enum; if a better reason
0067         is available, the corresponding error should be used instead.
0068       </tp:rationale>
0069     </tp:docstring>
0070   </tp:error>
0071 
0072   <tp:error name="Invalid Handle">
0073     <tp:docstring>
0074     The handle specified is unknown on this channel or connection.
0075     </tp:docstring>
0076   </tp:error>
0077 
0078   <tp:error name="Channel.Banned">
0079     <tp:docstring>
0080     You are banned from the channel.
0081     </tp:docstring>
0082   </tp:error>
0083 
0084   <tp:error name="Channel.Full">
0085     <tp:docstring>
0086     The channel is full.
0087     </tp:docstring>
0088   </tp:error>
0089 
0090   <tp:error name="Channel.Invite Only">
0091     <tp:docstring>
0092     The requested channel is invite-only.
0093     </tp:docstring>
0094   </tp:error>
0095 
0096   <tp:error name="Not Yours">
0097     <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
0098       <p>The requested channel or other resource already exists, and another
0099         user interface in this session is responsible for it.</p>
0100 
0101       <p>User interfaces SHOULD handle this error unobtrusively, since it
0102         indicates that some other user interface is already processing the
0103         channel.</p>
0104     </tp:docstring>
0105   </tp:error>
0106 
0107   <tp:error name="Cancelled">
0108     <tp:docstring>
0109       Raised by an ongoing request if it is cancelled by user request before
0110       it has completed, or when operations are performed on an object which
0111       the user has asked to close (for instance, a Connection where the user
0112       has called Disconnect, or a Channel where the user has called Close).
0113 
0114       <tp:rationale>
0115         The second form can be used to correspond to the Requested member in
0116         the <tp:type>Connection_Status_Reason</tp:type> enum, or to
0117         to represent the situation where disconnecting a Connection,
0118         closing a Channel, etc. has been requested by the user but this
0119         request has not yet been acted on, for instance because the
0120         service will only act on the request when it has finished processing
0121         an event queue.
0122       </tp:rationale>
0123     </tp:docstring>
0124   </tp:error>
0125 
0126   <tp:error name="Authentication Failed">
0127     <tp:docstring>
0128       Raised when authentication with a service was unsuccessful.
0129       <tp:rationale>
0130         This corresponds to Authentication_Failed in the
0131         <tp:type>Connection_Status_Reason</tp:type> enum.
0132       </tp:rationale>
0133     </tp:docstring>
0134   </tp:error>
0135 
0136   <tp:error name="Encryption Not Available">
0137     <tp:docstring>
0138       Raised if a user request insisted that encryption should be used,
0139       but encryption was not actually available.
0140 
0141       <tp:rationale>
0142         This corresponds to part of Encryption_Error in the
0143         <tp:type>Connection_Status_Reason</tp:type> enum. It's been separated
0144         into a distinct error here because the two concepts that were part
0145         of EncryptionError seem to be things that could reasonably appear
0146         differently in the UI.
0147       </tp:rationale>
0148     </tp:docstring>
0149   </tp:error>
0150 
0151   <tp:error name="Encryption Error">
0152     <tp:docstring>
0153       Raised if encryption appears to be available, but could not actually be
0154       used (for instance if SSL/TLS negotiation fails).
0155       <tp:rationale>
0156         This corresponds to part of Encryption_Error in the
0157         <tp:type>Connection_Status_Reason</tp:type> enum.
0158       </tp:rationale>
0159     </tp:docstring>
0160   </tp:error>
0161 
0162   <tp:error name="Cert.Not Provided">
0163     <tp:docstring>
0164       Raised if the server did not provide a SSL/TLS certificate. This error
0165       MUST NOT be used to represent the absence of a client certificate
0166       provided by the Telepathy connection manager.
0167       <tp:rationale>
0168         This corresponds to Cert_Not_Provided in the
0169         <tp:type>Connection_Status_Reason</tp:type> enum. That error
0170         explicitly applied only to server SSL certificates, so this one
0171         is similarly limited; having the CM present a client certificate
0172         is a possible future feature, but it should have its own error
0173         handling.
0174       </tp:rationale>
0175     </tp:docstring>
0176   </tp:error>
0177 
0178   <tp:error name="Cert.Untrusted">
0179     <tp:docstring>
0180       Raised if the server provided a SSL/TLS certificate signed by an
0181       untrusted certifying authority. This error SHOULD NOT be used to
0182       represent a self-signed certificate: see the Self Signed error for that.
0183       <tp:rationale>
0184         This corresponds to Cert_Untrusted in the
0185         <tp:type>Connection_Status_Reason</tp:type> enum and to Untrusted in the
0186         <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum, with a clarification
0187         to avoid ambiguity.
0188       </tp:rationale>
0189     </tp:docstring>
0190   </tp:error>
0191 
0192   <tp:error name="Cert.Expired">
0193     <tp:docstring>
0194       Raised if the server provided an expired SSL/TLS certificate.
0195       <tp:rationale>
0196         This corresponds to Cert_Expired in the
0197         <tp:type>Connection_Status_Reason</tp:type> enum and to Expired in
0198         the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0199       </tp:rationale>
0200     </tp:docstring>
0201   </tp:error>
0202 
0203   <tp:error name="Cert.Not Activated">
0204     <tp:docstring>
0205       Raised if the server provided an SSL/TLS certificate that will become
0206       valid at some point in the future.
0207       <tp:rationale>
0208         This corresponds to Cert_Not_Activated in the
0209         <tp:type>Connection_Status_Reason</tp:type> enum and to
0210         Not_Activated in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0211       </tp:rationale>
0212     </tp:docstring>
0213   </tp:error>
0214 
0215   <tp:error name="Cert.Fingerprint Mismatch">
0216     <tp:docstring>
0217       Raised if the server provided an SSL/TLS certificate that did not have
0218       the expected fingerprint.
0219       <tp:rationale>
0220         This corresponds to Cert_Fingerprint_Mismatch in the
0221         <tp:type>Connection_Status_Reason</tp:type> enum and to
0222         Fingerprint_Mismatch in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0223       </tp:rationale>
0224     </tp:docstring>
0225   </tp:error>
0226 
0227   <tp:error name="Cert.Hostname Mismatch">
0228     <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
0229       <p>Raised if the server provided an SSL/TLS certificate that did not match
0230       its hostname.</p>
0231       <p>You MAY be able to get more details about the expected and certified
0232       hostnames by looking up the 'expected-hostname' and 'certificate-hostname'
0233       keys in the details map that came together with this error.</p>
0234       <tp:rationale>
0235         This corresponds to Cert_Hostname_Mismatch in the
0236         <tp:type>Connection_Status_Reason</tp:type> enum and to Hostname_Mismatch
0237         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0238       </tp:rationale>
0239     </tp:docstring>
0240   </tp:error>
0241 
0242   <tp:error name="Cert.Self Signed">
0243     <tp:docstring>
0244       Raised if the server provided an SSL/TLS certificate that is self-signed
0245       and untrusted.
0246       <tp:rationale>
0247         This corresponds to Cert_Self_Signed in the
0248         <tp:type>Connection_Status_Reason</tp:type> enum and to Self_Signed
0249         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0250       </tp:rationale>
0251     </tp:docstring>
0252   </tp:error>
0253 
0254   <tp:error name="Cert.Revoked">
0255     <tp:docstring>
0256       Raised if the server provided an SSL/TLS certificate that has been
0257       revoked.
0258       <tp:rationale>
0259         This corresponds to Cert_Revoked in the
0260         <tp:type>Connection_Status_Reason</tp:type> enum and to Revoked
0261         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0262       </tp:rationale>
0263     </tp:docstring>
0264   </tp:error>
0265 
0266   <tp:error name="Cert.Insecure">
0267     <tp:added version="0.19.11"/>
0268     <tp:docstring>
0269       Raised if the server provided an SSL/TLS certificate that uses an
0270       insecure cipher algorithm or is cryptographically weak.
0271       <tp:rationale>
0272         This corresponds to Cert_Insecure in the
0273         <tp:type>Connection_Status_Reason</tp:type> enum and to Insecure
0274         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0275       </tp:rationale>
0276     </tp:docstring>
0277   </tp:error>
0278 
0279   <tp:error name="Cert.Invalid">
0280     <tp:added version="0.19.11"/>
0281     <tp:docstring>
0282       Raised if the server provided an SSL/TLS certificate that is
0283       unacceptable in some way that does not have a more specific error.
0284       <tp:rationale>
0285         This corresponds to Cert_Other_Error in the
0286         <tp:type>Connection_Status_Reason</tp:type> enum and to Unknown
0287         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0288       </tp:rationale>
0289     </tp:docstring>
0290   </tp:error>
0291 
0292   <tp:error name="Cert.Limit Exceeded">
0293     <tp:added version="0.19.11"/>
0294     <tp:docstring>
0295       Raised if the length in bytes of the server certificate, or the depth of the
0296       server certificate chain exceeds the limits imposed by the crypto
0297       library.
0298       <tp:rationale>
0299         This corresponds to Cert_Limit_Exceeded in the
0300         <tp:type>Connection_Status_Reason</tp:type> enum and to Limit_Exceeded
0301         in the <tp:type>TLS_Certificate_Reject_Reason</tp:type> enum.
0302       </tp:rationale>
0303     </tp:docstring>
0304   </tp:error>
0305 
0306   <tp:error name="Not Capable">
0307     <tp:docstring>
0308     Raised when requested functionality is unavailable due to contact
0309     not having required capabilities.
0310     </tp:docstring>
0311   </tp:error>
0312 
0313   <tp:error name="Offline">
0314     <tp:docstring>
0315       Raised when requested functionality is unavailable because a contact is
0316       offline.
0317 
0318       <tp:rationale>
0319         This corresponds to Offline in the
0320         <tp:type>Channel_Group_Change_Reason</tp:type> enum.
0321       </tp:rationale>
0322     </tp:docstring>
0323   </tp:error>
0324 
0325   <tp:error name="Channel.Kicked">
0326     <tp:docstring>
0327       Used to represent a user being ejected from a channel by another user,
0328       for instance being kicked from a chatroom.
0329 
0330       <tp:rationale>
0331         This corresponds to Kicked in the
0332         <tp:type>Channel_Group_Change_Reason</tp:type> enum.
0333       </tp:rationale>
0334     </tp:docstring>
0335   </tp:error>
0336 
0337   <tp:error name="Busy">
0338     <tp:docstring>
0339       Used to represent a user being removed from a channel because of a
0340       "busy" indication. This error SHOULD NOT be used to represent a server
0341       or other infrastructure being too busy to process a request - for that,
0342       see ServerBusy.
0343 
0344       <tp:rationale>
0345         This corresponds to Busy in the
0346         <tp:type>Channel_Group_Change_Reason</tp:type> enum.
0347       </tp:rationale>
0348     </tp:docstring>
0349   </tp:error>
0350 
0351   <tp:error name="No Answer">
0352     <tp:docstring>
0353       Used to represent a user being removed from a channel because they did
0354       not respond, e.g. to a StreamedMedia call.
0355 
0356       <tp:rationale>
0357         This corresponds to No_Answer in the
0358         <tp:type>Channel_Group_Change_Reason</tp:type> enum.
0359       </tp:rationale>
0360     </tp:docstring>
0361   </tp:error>
0362 
0363   <tp:error name="Does Not Exist">
0364     <tp:docstring>
0365       Raised when the requested user does not, in fact, exist.
0366 
0367       <tp:rationale>
0368         This corresponds to Invalid_Contact in the
0369         <tp:type>Channel_Group_Change_Reason</tp:type> enum, but can also be
0370         used to represent other things not existing (like chatrooms, perhaps).
0371       </tp:rationale>
0372     </tp:docstring>
0373   </tp:error>
0374 
0375   <tp:error name="Terminated">
0376     <tp:docstring>
0377       Raised when a channel is terminated for an unspecified reason. In
0378       particular, this error SHOULD be used whenever normal termination of
0379       a 1-1 StreamedMedia call by the remote user is represented as a D-Bus
0380       error name.
0381 
0382       <tp:rationale>
0383         This corresponds to None in the
0384         <tp:type>Channel_Group_Change_Reason</tp:type> enum.
0385       </tp:rationale>
0386     </tp:docstring>
0387   </tp:error>
0388 
0389   <tp:error name="Connection Refused">
0390     <tp:docstring>
0391       Raised when a connection is refused.
0392     </tp:docstring>
0393   </tp:error>
0394 
0395   <tp:error name="Connection Failed">
0396     <tp:docstring>
0397       Raised when a connection can't be established.
0398     </tp:docstring>
0399   </tp:error>
0400 
0401   <tp:error name="Connection Lost">
0402     <tp:docstring>
0403       Raised when a connection is broken.
0404     </tp:docstring>
0405   </tp:error>
0406 
0407   <tp:error name="Already Connected">
0408     <tp:docstring>
0409       Raised when the user attempts to connect to an account but they are
0410       already connected (perhaps from another client or computer), and the
0411       protocol or account settings do not allow this.
0412 
0413       <tp:rationale>
0414         XMPP can have this behaviour if the user chooses the same resource
0415         in both clients (it is server-dependent whether the result is
0416         AlreadyConnected on the new connection, ConnectionReplaced on the
0417         old connection, or two successful connections).
0418       </tp:rationale>
0419     </tp:docstring>
0420   </tp:error>
0421 
0422   <tp:error name="Connection Replaced">
0423     <tp:docstring>
0424       Raised by an existing connection to an account if it is replaced by
0425       a new connection (perhaps from another client or computer).
0426 
0427       <tp:rationale>
0428         In MSNP, when connecting twice with the same Passport, the new
0429         connection "wins" and the old one is automatically disconnected.
0430         XMPP can also have this behaviour if the user chooses the same
0431         resource in two clients (it is server-dependent whether the result is
0432         AlreadyConnected on the new connection, ConnectionReplaced on the
0433         old connection, or two successful connections).
0434       </tp:rationale>
0435     </tp:docstring>
0436   </tp:error>
0437 
0438   <tp:error name="Registration Exists">
0439     <tp:docstring>
0440       Raised during in-band registration if the server indicates that the
0441       requested account already exists.
0442     </tp:docstring>
0443   </tp:error>
0444 
0445   <tp:error name="Service Busy">
0446     <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
0447       Raised if a server or some other piece of infrastructure cannot process
0448       the request, e.g. due to resource limitations. Clients MAY try again
0449       later.
0450 
0451       <tp:rationale>
0452         This is not the same error as Busy, which indicates that a
0453         <em>user</em> is busy.
0454       </tp:rationale>
0455     </tp:docstring>
0456   </tp:error>
0457 
0458   <tp:error name="Resource Unavailable">
0459     <tp:docstring>
0460       Raised if a request cannot be satisfied because a process local to the
0461       user has insufficient resources. Clients MAY try again
0462       later.
0463 
0464       <tp:rationale>
0465         For instance, the <tp:dbus-ref
0466           namespace="org.freedesktop.Telepathy">ChannelDispatcher</tp:dbus-ref>
0467         might raise this error for some or all channel requests if it has
0468         detected that there is not enough free memory.
0469       </tp:rationale>
0470     </tp:docstring>
0471   </tp:error>
0472 
0473   <tp:error name="Would Break Anonymity">
0474     <tp:added version="0.19.7"/>
0475     <tp:docstring>
0476       Raised if a request cannot be satisfied without violating an earlier
0477       request for anonymity, and the earlier request specified that raising
0478       an error is preferable to disclosing the user's identity (for instance
0479       via <tp:dbus-ref namespace="org.freedesktop.Telepathy"
0480         >Connection.Interface.Anonymity.AnonymityMandatory</tp:dbus-ref> or
0481       <tp:dbus-ref namespace="org.freedesktop.Telepathy"
0482         >Channel.Interface.Anonymity.AnonymityMandatory</tp:dbus-ref>).
0483     </tp:docstring>
0484   </tp:error>
0485 
0486   <tp:error name="Not Yet">
0487     <tp:added version="0.19.12"/>
0488     <tp:docstring>
0489       Raised when the requested functionality is not yet available, but is
0490       likely to become available after some time has passed.
0491     </tp:docstring>
0492   </tp:error>
0493 
0494   <tp:error name="Rejected">
0495     <tp:added version="0.21.2"/>
0496     <tp:docstring>
0497       Raised when an incoming or outgoing <tp:dbus-ref
0498       namespace="ofdT.Channel.Type">Call.DRAFT</tp:dbus-ref> is
0499       rejected by the the receiver.
0500     </tp:docstring>
0501   </tp:error>
0502 
0503   <tp:error name="Picked Up Elsewhere">
0504     <tp:added version="0.21.3"/>
0505     <tp:docstring>
0506       Raised when a call was terminated as a result of the local user
0507       picking up the call on a different resource.
0508     </tp:docstring>
0509   </tp:error>
0510 
0511   <tp:error name="Service Confused">
0512     <tp:added version="0.21.5"/>
0513     <tp:docstring>
0514       Raised when a server or other piece of infrastructure indicates an
0515       internal error, or when a message that makes no sense is received from
0516       a server or other piece of infrastructure.
0517 
0518       <tp:rationale>
0519         For instance, this is appropriate for XMPP's
0520         <code>internal-server-error</code>, and is also appropriate if
0521         you receive sufficiently inconsistent information from a server that
0522         you cannot continue.
0523       </tp:rationale>
0524     </tp:docstring>
0525   </tp:error>
0526 
0527   <tp:error name="Confused">
0528     <tp:added version="0.21.5"/>
0529     <tp:docstring>
0530       Raised if a server rejects protocol messages from a connection manager
0531       claiming that they do not make sense, two local processes fail to
0532       understand each other, or an apparently impossible situation is
0533       reached.
0534 
0535       <tp:rationale>
0536         For instance, this would be an appropriate mapping for XMPP's
0537         errors bad-format, invalid-xml, etc., which can't happen unless
0538         the local (or remote) XMPP implementation is faulty. This is
0539         also analogous to
0540         <tp:type>Media_Stream_Error</tp:type>_Invalid_CM_Behavior,
0541         <code>TP_DBUS_ERROR_INCONSISTENT</code> in telepathy-glib, and
0542         <code>TELEPATHY_QT4_ERROR_INCONSISTENT</code> in telepathy-qt4.
0543       </tp:rationale>
0544     </tp:docstring>
0545   </tp:error>
0546 
0547   <tp:copyright>Copyright © 2005-2010 Collabora Limited</tp:copyright>
0548   <tp:copyright>Copyright © 2005-2009 Nokia Corporation</tp:copyright>
0549   <tp:license xmlns="http://www.w3.org/1999/xhtml">
0550 <p>This library is free software; you can redistribute it and/or
0551 modify it under the terms of the GNU Lesser General Public
0552 License as published by the Free Software Foundation; either
0553 version 2.1 of the License, or (at your option) any later version.</p>
0554 
0555 <p>This library is distributed in the hope that it will be useful,
0556 but WITHOUT ANY WARRANTY; without even the implied warranty of
0557 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
0558 Lesser General Public License for more details.</p>
0559 
0560 <p>You should have received a copy of the GNU Lesser General Public
0561 License along with this library; if not, write to the Free Software
0562 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</p>
0563   </tp:license>
0564 </tp:errors>