summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Drop the McdConnection probation timer when the TpConnection is releasedtelepathy-mission-control-5.4Vivek Dasmohapatra2010-08-191-5/+25
| | | | | | Also: Check that we haven't accidentally called the timer callback after releasing the TpConnection, as this avoids a SEGV (and g_warn if we find ourselves in this situation)
* More checks on built strings (from coverity report)Vivek Dasmohapatra2010-08-191-12/+19
|
* Unused variableVivek Dasmohapatra2010-08-191-2/+0
|
* Can't use the AvatarRetrieved signal to find out if an avatar has been removedVivek Dasmohapatra2010-07-291-10/+59
| | | | | | | The signal only fired for those contacts that had an avatar, so if the connection signals that the avatar has been updated, and we then try to fetch the avatar via this signal, we simply never receive any data and the avatar we have never gets erased.
* Implement a test for a remote client unsetting our avatarVivek Dasmohapatra2010-07-292-2/+16
|
* Treat calls ended locally with No_Answer as missedWill Thompson2010-07-021-1/+2
| | | | | | | If the actor is the self handle, and the reason is No_Answer, then something on our side (either the CM or some client) decided we weren't going to answer and gave up. From the user's PoV, these calls are missed, so mark them as such.
* Reduce INITIAL_RECONNECTION_TIME to 3 secondsWill Thompson2010-06-161-1/+1
| | | | | This gives us pretty much the same progression, but with the first reconnection happening fast enough for the test suite.
* Add a #define for the reconnect interval capWill Thompson2010-06-161-3/+4
|
* Attempt to reconnect less frequently.Will Thompson2010-06-161-2/+2
| | | | | | | | The previous constants made MC really keen. Trying again after 1 second is fine if the CM crashed, but the normal situation is that the server fell over, or the network is broken, in which case 10 seconds, 30 seconds, 1½ minutes, 4½ minutes, 13½ minutes, then every half hour seems a lot more reasonable.
* Include reconnection time in debug messageWill Thompson2010-06-161-1/+2
|
* Add a #define for reconnection timeout multiplierWill Thompson2010-06-161-1/+2
|
* Nano versionSimon McVittie2010-06-162-1/+6
|
* Prepare version 5.4.3telepathy-mission-control-5.4.3Simon McVittie2010-06-162-3/+11
|
* Enable ERROR_CFLAGS in every Makefile.am that compiles CSimon McVittie2010-06-167-0/+12
|
* configure.ac: remove alleged AM_CFLAGS that were never actually used for ↵Simon McVittie2010-06-161-3/+0
| | | | anything
* Remove obsolete datadir_expanded check from configure.acSimon McVittie2010-06-161-11/+0
| | | | We use g_get_system_data_dirs() etc. now.
* Add code to a couple of existing tests to verify that serialization in key ↵Simon McVittie2010-06-163-9/+45
| | | | | | files is as intended (Backported from master to not expect account storage to be diverted)
* _mcd_account_dup_parameters: if unable, explain whySimon McVittie2010-06-161-0/+3
|
* McdAccount: clear_register_dup_params_cb: survive if params is NULLSimon McVittie2010-06-161-0/+6
| | | | | It can be NULL in crash-recovery.py, apparently. Unfortunately, the async implementation doesn't tell us why it failed, only that it did.
* account-manager/recover-from-disconnect.py: comment why register=TrueSimon McVittie2010-06-161-1/+2
|
* Remove duplicate call to _mcd_account_set_parameter()Simon McVittie2010-06-161-2/+0
|
* fd.o #28118: clear the 'register' flag when an account goes to CONNECTEDSimon McVittie2010-06-162-3/+37
|
* Nano versionSimon McVittie2010-05-262-1/+6
|
* Prepare version 5.4.2telepathy-mission-control-5.4.2Simon McVittie2010-05-262-3/+14
|
* Coverity 7707 REVERSE_INULL two gchar ** deref'd w/o check in set_paramVivek Dasmohapatra2010-05-261-15/+20
| | | | | Also gchar ** strv_type_key potentially leaked in the 'clear' and 'unset' cases (cherry picked from commit c4b90bf71b14da5a6c11bd7ef1898cd2734ffbab)
* Coverity 21106 RESOURCE_LEAK in dispatch_operation_claimVivek Dasmohapatra2010-05-261-3/+7
| | | | (cherry picked from commit 07599a7ab74d654d50bc4dd8493f6f4cef5459df)
* Merge branch '54-unsafe-param-reuse' into telepathy-mission-control-5.4Simon McVittie2010-05-264-20/+177
|\ | | | | | | Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
| * _mcd_account_dup_parameters: don't assume that borrowed parameters remain validSimon McVittie2010-05-261-7/+16
| |
| * _mcd_account_set_parameters: don't assume that borrowed parameters remain validSimon McVittie2010-05-261-4/+9
| |
| * mcd_account_check_parameters: don't assume that borrowed parameters remain validSimon McVittie2010-05-261-6/+18
| |
| * _mcd_account_migrate_secrets: don't assume that a borrowed string remains validSimon McVittie2010-05-261-3/+5
| |
| * _mcd_manager_dup_protocol, _mcd_manager_protocol_free: addSimon McVittie2010-05-263-0/+129
|/ | | | | | Copied from telepathy-glib 0.11.6 to avoid a dependency on that version in this stable branch; in git master, they should be replaced by calls to the newer telepathy-glib API.
* Nano versionSimon McVittie2010-05-252-1/+6
|
* Prepare version 5.4.1telepathy-mission-control-5.4.1Simon McVittie2010-05-252-2/+4
|
* update NEWSSimon McVittie2010-05-251-1/+9
|
* Don't cache whether we have the requests interfaceSimon McVittie2010-05-251-5/+6
| | | | | | | | | | One use of the caching (in _mcd_connection_request_channel) was subtly incorrect: before using the cached variable we checked whether the TpConnection was ready, but that's not the same thing as checking whether our on_connection_ready() callback (which caches it) has actually been called yet. This fixes a regression in dispatcher/connect-for-request.py.
* Add a regression test for fd.o #25684Simon McVittie2010-05-252-0/+65
| | | | | This turns out to be a regression in the 5.5 branch, but adding a test in the stable branch seems a good way to avoid introducing this bug.
* set '0' as UserActionTime when HandleWith() is calledGuillaume Desmottes2010-05-191-3/+2
| | | | | | '0' means 'no user action' which is the safer choice to prevent focus stealing. User should use a futur variant of HandleWith() allowing him to pass a UserActionTime when needed.
* account-manager/presence.py: GetInterfaces can be called twiceGuillaume Desmottes2010-05-191-3/+8
|
* mctest.py: no need to import 'sha'Guillaume Desmottes2010-05-191-1/+0
|
* Start 5.4.1 developmentSimon McVittie2010-04-152-1/+6
|
* Prepare release 5.4.0telepathy-mission-control-5.4.0Simon McVittie2010-04-152-2/+4
|
* Distribute Logger.client as well as AbiWord.clientSimon McVittie2010-04-151-0/+1
| | | | This hopefully fixes distcheck.
* Re-generate doc stuff with gtk-doc 1.14Simon McVittie2010-04-1526-0/+108
|
* Document the Recover feature in NEWSSimon McVittie2010-04-151-0/+7
|
* Add missing #includesSimon McVittie2010-04-152-1/+4
|
* McdHandlerMap: perform channel->account lookup internallySenko Rasic2010-04-153-7/+11
| | | | Instead of giving access to the whole map to the user.
* _mcd_client_recover_observer: don't leak connection referenceSenko Rasic2010-04-151-3/+1
|
* tests: assert that observer info "recovering" key is set in observer recoverySenko Rasic2010-04-152-2/+6
|
* moved _mcd_tp_channel_* to a separate fileSenko Rasic2010-04-157-138/+217
|
View Lorry Controller Status