cannot start screenlets

[schoeggu]

whne i want to start a screenlet i get following error:
schoeggu@supertux:~/.screenlets/Clock> ./ClockScreenlet.py
CachingBackend: Loading instances from cache
Found a running session - adding new instance by service.
<Interface <ProxyObject wrapping <dbus.Bus on SESSION at 0xb66b5f6c> org.screenlets.Clock /org/screenlets/Clock at 0xb66c20ac> implementing 'org.screenlets.ScreenletService' at 0xb66c20ec>
Introspect error: The name org.screenlets.Clock was not provided by any .service files
Traceback (most recent call last):
File "./ClockScreenlet.py", line 433, in <module>
screenlets.session.create_session(ClockScreenlet)
File "/usr/local/lib/python2.5/site-packages/screenlets/session.py", line 301, in create_session
session.start()
File "/usr/local/lib/python2.5/site-packages/screenlets/session.py", line 155, in start
srvc.add('')
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 102, in __call__
reply_message = self._connection.send_with_reply_and_block(message , timeout)
File "dbus_bindings.pyx", line 456, in dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: The name org.screenlets.Clock was not provided by any .service files


anyone can help me?

[RYX]

Hi schoeggu!

There seems to be an instance of the Clock already running and the new one can't be added through the service. Do you have python-dbus installed? And why do you want to start the Clock from the ~/.screenlets directory? Does this work:/usr/local/share/screenlets/Clock/ClockScreenlet.py?

[schoeggu]

hey ryx,

sorry i didn't answer for so long, but the Tux inside my computer was very ill and did almost die, i needed to cure him first (short, my computer was really f*cked up)

anyways, yes i have python-dbus, i've uninstalled all the older versions of screenlets and reinstalled v. 0.9 but i get same error (i started as you sayd from/usr/local/share/screenlets/ )
when i try things like screenletsd start, screenletd stop or screenletsd add Clock
i get following message:
Screenletsd v0.0.1 | (c) RYX (Rico Pfaus) 2007 | released under the GPL
/usr/local/bin/screenletsd: line 99: syntax error near unexpected token `('
/usr/local/bin/screenletsd: line 99: ` echo " 'add <name>' : add a Screenlet (e.g. 'add Clock')"'

[RYX]

Screenletsd is not used any longer, you need to start each screenlet individually now. What output do you get if you start a screenlet like this:/usr/local/share/screenlets/Control/ControlScreenlet.py??

:)

[schoeggu]

i get following output:
schoeggu@supertux:/usr/local/share/screenlets/Clock> ./ClockScreenlet.py
CachingBackend: Loading instances from cache
Found a running session - adding new instance by service.
<Interface <ProxyObject wrapping <dbus.Bus on SESSION at 0xb66caf6c> org.screenlets.Clock /org/screenlets/Clock at 0xb66d70ac> implementing 'org.screenlets.ScreenletService' at 0xb66d70ec>
Introspect error: The name org.screenlets.Clock was not provided by any .service files
Traceback (most recent call last):
File "./ClockScreenlet.py", line 433, in <module>
screenlets.session.create_session(ClockScreenlet)
File "/usr/local/lib/python2.5/site-packages/screenlets/session.py", line 301, in create_session
session.start()
File "/usr/local/lib/python2.5/site-packages/screenlets/session.py", line 155, in start
srvc.add('')
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 102, in __call__
reply_message = self._connection.send_with_reply_and_block(message , timeout)
File "dbus_bindings.pyx", line 456, in dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: The name org.screenlets.Clock was not provided by any .service files

[RYX]

That's strange. I think there is a somehow misconfigured or otherwise hanging instance of the clock running, that's why you can't add a new one ... Try "killall python" to kill all open screenlets-processes (be sure to do that without any unsaved data in your other apps) and then try starting the ControlScreenlet with the above command ...

Does adding new screenlets through Applications/Screenlets work? And is it only the clock that causes trouble?

[schoeggu]

thanks for the help...

killall python just says no process killed, so there is no instance of Clock already runnig.

with /usr/local/share/screenlets/Control/ControlScreenlet.py (and other screenlets) i get the same output as with the clock

[RYX]

I'll look into that later today. Very odd ... it looks as if it creates the dbus-service and then tries to access it immediately (it should just start instead). What distribution are you running? (I only have tested on Ubuntu Feisty yet)