summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-12-22Changes need to cross compile MC for windowsHEADmasterSiraj Razick1-0/+4
we need to include io.h to make unmask work when cross compiling
2011-12-19In the [unlikely] event the id key has the wrong type, don't leak the GValueVivek Dasmohapatra1-0/+4
2011-12-19AgManager::enabled-event doesn't have the AgAccount::enabled multi-trigger bugVivek Dasmohapatra1-25/+10
2011-11-21Support building for Android, modified from an original patch by Derek ForemanAlvaro Soliverez8-3/+110
https://bugs.freedesktop.org/show_bug.cgi?id=42508
2011-11-21Build on systems without gettextAlvaro Soliverez16-17/+0
Modified from an original patch by Derek Foreman https://bugs.freedesktop.org/show_bug.cgi?id=42508
2011-11-16Use _unref instead of _free _destroy when possible.unrefXavier Claessens14-38/+38
Replace g_(ptr_)array_free (foo, TRUE) and g_hash_table_destroy with respectively g_(ptr_)array_unref (foo) and g_hash_table_unref. I used this command to generate this patch: for f in `find -name "*.c"`; do sed -i $f -re 's/g_ptr_array_free \(([^ ,]+), TRUE\)/g_ptr_array_unref \(\1\)/'; done See Danielle's blog for explanation of possible bug _free can do: http://blogs.gnome.org/danni/2011/11/16/mistakes-with-g_value_set_boxed/
2011-11-11value-is-same: stop testing G_TYPE_CHARGuillaume Desmottes1-6/+0
g_value_set_char() has been deprecated in GLib and, as said in the FIXME, we don't need to test this as it's not supported by D-Bus.
2011-11-10Put request paths under /org/fd/T/CDWill Thompson1-1/+1
2011-11-08Merge branch 'telepathy-mission-control-5.10'Will Thompson2-8/+12
Conflicts: configure.ac
2011-11-08Bump version to 5.10.1+Will Thompson1-1/+1
2011-11-08Version 5.10.1Will Thompson1-1/+1
2011-11-08NEWS for 5.10.1Will Thompson1-0/+12
2011-11-08Remove stray <enum/> from GSettings schemaWill Thompson1-8/+0
I forgot to remove this when duplicating the one key I wanted to steal from Empathy, and ioni reported that it clashes with the same enum definition provided by Empathy. (I'm not 100% sure why—I'd've assumed they'd be namespaced by the GSettings schema, not the DConf path—but hey.)
2011-11-07And again to 5.10.999+ for the unstable branch.Will Thompson1-1/+1
2011-11-07Bump version to 5.10.0+Will Thompson1-1/+1
2011-11-07Version 5.10.0Will Thompson2-2/+2
2011-11-07NEWS for 5.10.0Will Thompson1-3/+32
2011-11-04Merge branch 'gsettings'Will Thompson8-4/+53
Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=42068>
2011-11-04exec-with-log.sh.in: export POSIX_ME_HARDER=1Will Thompson1-2/+4
2011-11-04ConnectivityMonitor: fix debug messageWill Thompson1-1/+1
2011-11-04.gitignore: ignore connectivity monitor test toolWill Thompson1-0/+1
2011-11-04Bind use-conn GSettings key to ConnectivityMonitorWill Thompson4-0/+17
This GSettings key does the same thing as the Empathy one it's an alias for does: if use-conn is False, the network state from NM/ConnMan is ignored, and MC will allow you to try to sign in even if there is supposedly no network connection! It's pretty great. (When I first committed this, it didn't work. Now it does. I don't know why.)
2011-11-04Add a GSettings schema with use-conn keyWill Thompson5-0/+31
When the NM/ConnMan code lived in Empathy, there was a GSettings key which could be flipped to false to make Empathy always assume it had a network connection. This schema provides one GSettings key, im.telepathy.MissionControl.FromEmpathy use-conn, which happens to use the same dconf path as the Empathy key uses. This should make the two GSettings keys aliases for the same underlying value in dconf; we get a migration path for free.
2011-11-04tests: add --enable-installed-testsAlban Crequy14-29/+249
This configure option makes it possible to install the twisted tests in /usr/share/telepathy-mission-control-tests and run them without the sources. https://bugs.freedesktop.org/show_bug.cgi?id=41927
2011-11-04update-parameters.py: fix the cache directoryAlban Crequy1-2/+2
Use $XDG_CACHE_HOME instead of $MC_ACCOUNT_DIR to find the file mcp-test-diverted-account-plugin.conf because the test-only plugin mcp-account-diversion uses g_get_user_cache_dir(). This is a no-op because both variables have the same value, as defined in tests/twisted/Makefile.am: BASIC_TESTS_ENVIRONMENT = \ MC_ACCOUNT_DIR=@abs_top_builddir@/tests/twisted/tmp-$(TMPSUFFIX) \ XDG_CACHE_HOME=@abs_top_builddir@/tests/twisted/tmp-$(TMPSUFFIX) \ However, this was not semantically correct, and the two directories could be different in the future, with installed tests for example.
2011-11-03.gitignore: remove obsolete libmcclient referencesWill Thompson1-2/+0
libmcclient is gone forever, so let's not ignore detritus from it.
2011-11-03Merge branch 'ChangingPresence'Will Thompson3-11/+53
Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk> Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=42548>
2011-11-03Account: only set ChangingPresence if we actually areWill Thompson2-7/+46
Previously, ChangingPresence could become True on accounts which were not Enabled, which makes no sense: we're not changing our presence in that case. It happened if you requested an offline presence on a disabled account whose current RequestedPresence is something online; or if you disabled an Enabled account whose RequestedPresence (and CurrentPresence) was offline. Here we change the implementation of setting RequestedPresence to only set ChangingPresence to True if it actually takes some action. There are situations where the presence has "changed" (maybe you changed the message associated with being offline) but no change actually needs to be applied.
2011-11-03account-manager/presence: modernizeWill Thompson1-4/+2
2011-11-03mc-tool: show ChangingPresenceWill Thompson1-0/+5
2011-10-07connectivity-monitor: fix build with UPower but no NM or ConnManJonny Lamb1-4/+3
http://bugs.debian.org/644589 Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-10-04Bump version to 5.9.3+Will Thompson2-1/+6
2011-10-04Version 5.9.3Will Thompson2-2/+2
2011-10-04NEWS for 5.9.3Will Thompson1-0/+25
2011-10-04Merge branch 'upower'Will Thompson5-16/+118
Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=28370>
2011-10-04Connectivity: move upower-specific code inside ifdefWill Thompson1-8/+8
connectivity_monitor_set_awake() is only called by the code paths that listen to signals from upower, so passing --disable-upower to configure triggered a defined-but-not-used warning for it.
2011-10-04Merge branch 'telepathy-mission-control-5.8+'Will Thompson3-1/+11
2011-10-04NEWS for 5.8.2Will Thompson1-0/+9
2011-10-04McdClient: don't allow unique_name to become NULLWill Thompson2-1/+2
_mcd_client_registry_found_name() is called in three situations: • the initial call to ListNames() has returned; • the initial call to ListActivatableNames() has returned; and • NameOwnerChanged has been emitted for a client-shaped well-known name. In the first two cases, unique_name_if_known is NULL; in the first case, activatable is FALSE. I don't really understand what business the McdClientRegistry has telling the McdClient what its unique name is even when it's non-NULL, but passing NULL to _mcd_client_proxy_set_active() made McdClient violate an internal invariant. The first action McdClient takes is to discover the client's unique name, if any; if the client is not running, unique_name is set to "" (not NULL). Other parts of the McdClient internals assume (and assert) that unique_name is not NULL by the time they run. I *believe* that the client registry need not ever call _mcd_client_proxy_set_active(), but I am loathe to make that change without fully understanding the code and writing some tests. Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=39767> Reviewed-by: Xavier Claessens <xclaesse@gmail.com>
2011-09-28Connectivity: refactor signalling state changesWill Thompson1-21/+25
As Guillaume pointed out on <https://bugs.freedesktop.org/show_bug.cgi?id=28370#c5>, previously McdConnectivityMonitor would signal ::state-change even if the state hasn't changed in some cases. This patch reduces duplication and fixes that case.
2011-09-28Master: Always bind connection to a transportWill Thompson1-2/+1
Previously, when a connection was brought online in response to an event other than a transport becoming connected, it would always be bound to a transport (if any transport plugins are loaded, obviously), regardless of whether the dictionary o' conditions was empty or not. However, when a transport coming online caused a connection to be brought up, that connection would not be bound to the transport that caused it to come online if the conditions were empty (which they generally are). For reasons I can't quite fathom, this actually doesn't seem to have affected anything: it could be because monitor_state_changed_cb in McdKludgeTransport also binds waiting connections to the transport that came online. But this seems like a sensible change for sanity and consistency reasons.
2011-09-28Connectivity: go offline when laptop suspends.Will Thompson3-3/+74
Woop woop.
2011-09-28configure: optionally depend on upower-glibWill Thompson1-0/+28
2011-09-28Merge branch 'fd.o-38978-connectivity'Will Thompson27-198/+1467
Fixes: <http://bugs.freedesktop.org/show_bug.cgi?id=38978> Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
2011-09-28fakeconnectivity: use constant for NM interfaceWill Thompson1-1/+1
2011-09-28KludgeTransport: debug when connections get queuedWill Thompson1-0/+2
2011-09-28Account: reconnect if RequestedPresence is not offlineWill Thompson2-2/+22
Previously, when a network connection came back up, only accounts with ConnectAutomatically set would be re-connected. But if RequestedPresence is something online-flavoured, I think it makes sense to bring such accounts back online, too: if the user has asked to be online, a network blip shouldn't affect that.
2011-09-28am/connectivity: extract BillyIdleWill Thompson1-10/+12
2011-09-28Account: when reconnecting, use RequestedPresence if possibleWill Thompson2-7/+22
Previously, if an account was taken offline due to the internet connection disappearing, when it was brought back up the AutomaticPresence would be used, trampling on whatever the user had put into RequestedPresence. I guess this was deliberate … but it doesn't seem like very useful behaviour. If I've explicitly set my presence to ('available', 'you can talk to me now'), despite my AutomaticPresence being ('busy', 'probably doing something else'), I don't see why a network connection blip should cause my lovingly-written presence to be discarded.
2011-09-28am/connectivity: check for SetPresence callWill Thompson1-2/+7
I'd like to be sure that setting RequestedPresence before the network connection comes up causes that presence to be applied when it does, as opposed to just that the account be brought online.
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-16 01:50:18 +0000