DbusScripts - Revision history

79.120.63.226: /* Running dbus-scripts on the session bus */

2012-10-31T08:02:37Z

Running dbus-scripts on the session bus

← Older revision		Revision as of 08:02, 31 October 2012
Line 85:		Line 85:

	start on started hildon-desktop		start on started hildon-desktop
	stop on stopping hildon-desktop		#stop on stopping hildon-desktop
			stop on starting shutdown

	console none		console none

imported_>gkuenning at 02:59, 28 November 2011

2011-11-28T02:59:13Z

Show changes

213.240.181.249: add wait for dbus, otherwise it may fail

2011-09-09T05:37:02Z

add wait for dbus, otherwise it may fail

← Older revision		Revision as of 05:37, 9 September 2011
Line 88:		Line 88:

	console none		console none

			pre-start script
			/usr/bin/run-standalone.sh /usr/sbin/waitdbus session
			end script

	exec run-standalone.sh /usr/sbin/dbus-scripts --session		exec run-standalone.sh /usr/sbin/dbus-scripts --session

imported_>amigadave: /* The incredibly useful --debug flag */ minor tidy

2011-03-17T13:03:30Z

The incredibly useful --debug flag: minor tidy

← Older revision		Revision as of 13:03, 17 March 2011
Line 105:		Line 105:
	==== The incredibly useful --debug flag ====		==== The incredibly useful --debug flag ====

	The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through run-standalone.sh).		The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through <code>run-standalone.sh</code>). For example:

	ie		<pre>
	<~~source lang=text~~>
	sudo dbus-scripts --debug		sudo dbus-scripts --debug
	sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session		sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session
	</~~source~~>		</pre>

	== Usage, tips and tricks ==		== Usage, tips and tricks ==

imported_>phedders: /* The incredibly useful --debug flag */ Added note about run-standalone and an example to cut and paste.

2011-03-17T10:50:14Z

The incredibly useful --debug flag: Added note about run-standalone and an example to cut and paste.

← Older revision		Revision as of 10:50, 17 March 2011
Line 105:		Line 105:
	==== The incredibly useful --debug flag ====		==== The incredibly useful --debug flag ====

	The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session".		The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through run-standalone.sh).

			ie
			<source lang=text>
			sudo dbus-scripts --debug
			sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session
			</source>

	== Usage, tips and tricks ==		== Usage, tips and tricks ==

imported_>amigadave: /* /usr/bin/offmsn */ bash

2010-08-02T11:51:04Z

/usr/bin/offmsn: bash

← Older revision		Revision as of 11:51, 2 August 2010
Line 393:		Line 393:
	</source>		</source>
	==== /usr/bin/offmsn ====		==== /usr/bin/offmsn ====
	<source lang="~~text~~">
			<source lang="bash">
	#!/bin/sh		#!/bin/sh
	# If we got disconnected from MSN (eg by signing in via Pidgin on desktop PC) then set it offline until further notice		# If we got disconnected from MSN (eg by signing in via Pidgin on desktop PC) then set it offline until further notice

imported_>magick777: /* Set MSN (pecan) to stay offline when disconnected */

2010-07-28T19:48:32Z

Set MSN (pecan) to stay offline when disconnected

← Older revision		Revision as of 19:48, 28 July 2010
Line 381:		Line 381:
	=== Set MSN (pecan) to stay offline when disconnected ===		=== Set MSN (pecan) to stay offline when disconnected ===

	Since MSN allows only one client connection at a time, signing into MSN from my N900 ~~will disconnect~~ it ~~from Pidgin~~ on my desktop PC, and vice versa.		Since MSN allows only one client connection at a time, signing into MSN from the N900 disconnects it on my desktop PC, and vice versa.

	Pidgin handles this gracefully by disabling the account until I manually connect it. msn-pecan, on the other hand, helpfully auto-reconnects on its own authority and fails to respect my disabling ~~autoconnect~~ via mc-tool; if the requested status remains as "available", it reconnects, and that disconnects Pidgin on my desktop again. Grr.		Pidgin on my desktop PC handles this gracefully by disabling the account until I manually connect it. msn-pecan, on the other hand, helpfully auto-reconnects on its own authority and fails to respect my disabling auto-connect via mc-tool; if the requested status remains as "available", it reconnects, and that disconnects Pidgin on my desktop again. Grr.

	You need an instance of dbus-scripts '''on the session bus''' for this one (see above), then you can do the following:		You need an instance of dbus-scripts '''on the session bus''' for this one (see above), then you can do the following:

imported_>magick777: /* Set MSN (pecan) to stay offline when disconnected */

2010-07-28T19:47:23Z

Set MSN (pecan) to stay offline when disconnected

← Older revision		Revision as of 19:47, 28 July 2010
Line 381:		Line 381:
	=== Set MSN (pecan) to stay offline when disconnected ===		=== Set MSN (pecan) to stay offline when disconnected ===

	Since MSN allows only one client connection at a time, signing into MSN from my N900 will disconnect it from Pidgin on my desktop PC, and vice versa. Pidgin handles this gracefully by disabling the account until I manually connect it. msn-pecan, on the other hand, helpfully auto-reconnects on its own authority and fails to respect my disabling autoconnect via mc-tool; if the requested status remains as "available", it reconnects, and that disconnects Pidgin on my desktop again. Grr. You need an instance of dbus-scripts '''on the session bus''' for this one (see above), then you can do the following:		Since MSN allows only one client connection at a time, signing into MSN from my N900 will disconnect it from Pidgin on my desktop PC, and vice versa.

			Pidgin handles this gracefully by disabling the account until I manually connect it. msn-pecan, on the other hand, helpfully auto-reconnects on its own authority and fails to respect my disabling autoconnect via mc-tool; if the requested status remains as "available", it reconnects, and that disconnects Pidgin on my desktop again. Grr.

			You need an instance of dbus-scripts '''on the session bus''' for this one (see above), then you can do the following:

	==== /etc/dbus-scripts.d/dbus-scripts-settings ====		==== /etc/dbus-scripts.d/dbus-scripts-settings ====

imported_>magick777: /* The incredibly useful --debug flag */

2010-07-28T19:41:49Z

The incredibly useful --debug flag

← Older revision		Revision as of 19:41, 28 July 2010
Line 105:		Line 105:
	==== The incredibly useful --debug flag ====		==== The incredibly useful --debug flag ====

	The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts.		The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session".

	== Usage, tips and tricks ==		== Usage, tips and tricks ==

imported_>magick777: /* System vs. session buses */

2010-07-28T19:40:31Z

System vs. session buses

← Older revision		Revision as of 19:40, 28 July 2010
Line 73:		Line 73:
	=== dbus-scripts daemon options ===		=== dbus-scripts daemon options ===

	==== ~~System vs.~~ session ~~buses~~ ====		==== Running dbus-scripts on the session bus ====

	By default, the dbus-scripts daemon listens on the system message bus, which reports system events but not those from the user session. If you want to access events such as an application being launched, you'll need to configure the daemon to listen to the session bus. You'll probably want to run a second instance of dbus-scripts without breaking the one on the system bus.		By default, the dbus-scripts daemon listens on the system message bus, which reports system events but not those from the user session. If you want to access events such as an application being launched, you'll need to configure the daemon to listen to the session bus as well. You'll probably want to run a second instance of dbus-scripts without breaking the one on the system bus.

	Ignore <code>/etc/init.d/dbus-scripts</code> and <code>/etc/default/dbus-scripts</code> as these would seem to have been superseded by upstart. Make a copy of <code>/etc/event.d/dbus-scripts</code> as <code>/etc/event.d/dbus-scripts-session</code> and edit it so your <code>/etc/event.d/dbus-scripts-session</code> will look like this:		Ignore <code>/etc/init.d/dbus-scripts</code> and <code>/etc/default/dbus-scripts</code> as these would seem to have been superseded by upstart. Make a copy of <code>/etc/event.d/dbus-scripts</code> as <code>/etc/event.d/dbus-scripts-session</code> and edit it so your <code>/etc/event.d/dbus-scripts-session</code> will look like this: