screenlets gives back errors

[some-guy]

i installed screenlets 0.0.9 on gnome, suse 10.2 64-bit, and when i try to launch the control screenlet i get > /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 0xc50a50> org.screenlets.Clock /org/screenlets/Clock at 0xc32a70> implementing 'org.screenlets.ScreenletService' at 0xc33ea8>
Introspect error: The name org.screenlets.Clock was not provided by any .service files
Traceback (most recent call last):
File "/usr/local/share/screenlets/Clock/ClockScreenlet.py", line 433, in <module>
screenlets.session.create_session(ClockScreenlet)
File "/usr/local/lib64/python2.5/site-packages/screenlets/session.py", line 301, in create_session
session.start()
File "/usr/local/lib64/python2.5/site-packages/screenlets/session.py", line 155, in start
srvc.add('')
File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib64/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]

This seems to be another case of the mysterious dbus issue that seems to happen on Kubuntu and Suse systems ... But you are the first gnome-user reporting it, so my guess that it could be KDE-related is off the table. There has to be some similarity between the users who have this problem, but what?

From what I can say it looks like it first finds a running instance over the dbus-service and then tries to access it and fails because it isn't there. So the problem should be somewhere in the code that checks for a running instance (I had that in mind anyway) ... I can try to implement another method of checking for running instances, but still I'd like to get behind the source of the problem.

:)

[some-guy]

actually i have kde installed (because some programs wont run without it:o i.e. K3B) that's probobly the reason.

[RYX]

I will release a new version soon (somewhen this weekend). That should eliminate the problem, even though the source remains and I'd still like to know where it comes from ...

:)

[bennyj]

Hi.I have installed the latest screenlets and followed the directions for install but can't seem to get it running.Hoping I can get some help.Im running debian etch with 2.6.22.1 kernel.I keep getting the following error when trying to start the screenlets

benny@debian:~$ /usr/local/share/screenlets/Clock/ClockScreenlet.py
Traceback (most recent call last):
File "/usr/local/share/screenlets/Clock/ClockScreenlet.py", line 17, in ?
import screenlets
File "/usr/lib/python2.4/site-packages/screenlets/__init__.py", line 33, in ?
import rsvg
ImportError: No module named rsvg

[RYX]

Hi bennyj!

You need to install the package "python-gnome2-desktop". Unfortunately the rsvg/wnck-bindings for python are bundled into that package. Also install python-xdg, in case you haven't.

:)

[bennyj]

Hi bennyj!

You need to install the package "python-gnome2-desktop". Unfortunately the rsvg/wnck-bindings for python are bundled into that package. Also install python-xdg, in case you haven't.

:)

Thank for the fast reply.I checked synaptic and I have both of those packages installed already.Any other Idea's ?

[RYX]

Hmm - did you check your repo for some python-bindings to librsvg? Maybe librsvg-python? Chances are good that the gnome-devs decide to split rsvg into its own package, maybe they already have ...

And do you have librsvg itself installed?

[bennyj]

Hmm - did you check your repo for some python-bindings to librsvg? Maybe librsvg-python? Chances are good that the gnome-devs decide to split rsvg into its own package, maybe they already have ...

And do you have librsvg itself installed?

librsvg2-2 installed.This is a bit perplexing:confused:

I don't need compiz to run this do I ?

[RYX]

It could be that it is installed for the wrong python version. Do you have only 2.4 installed or 2.5, too? A "ls /usr/lib/python* -d" should give info about that.

[bennyj]

It could be that it is installed for the wrong python version. Do you have only 2.4 installed or 2.5, too? A "ls /usr/lib/python* -d" should give info about that.

benny@debian:~$ ls /usr/lib/python* -d
/usr/lib/python2.3 /usr/lib/python2.5
/usr/lib/python2.4 /usr/lib/python-support

[leal]

Hi, RYX:

I came to the same error output as some-guy's, and here are some info about my distro:

# uname -a
Linux core2 2.6.18-1.2798.fc6.me #2 SMP Mon Jun 18 10:00:58 CST 2007 i686 i686 i386 GNU/Linux

# ls /usr/lib/python* -d
/usr/lib/python2.4

gnome version 2.16.3
screenlet version 0.0.10

compiz enabled and the latest avant-window-navigator installed.

When I run with /usr/local/share/screenlets/Clock/ClockScreenlet.py, I got the same errors with some-guy's. I have also tried screenlet 0.0.9, and got the same errors with above python script. But with 0.0.9, screenletsd is still available, so I have managed to run some screenlets with below commands:

# screenletsd start
# screenletsd add Clock
# screenletsd add Flower

They both show as normal and look pretty, but with /usr/local/share/screenlets/Clock/ClockScreenlet.py, same error came out.

However, screenlet is really bloody and I love it. Thank you RYX, and hope you could trace and fix the problem. Good luck!

i installed screenlets 0.0.9 on gnome, suse 10.2 64-bit, and when i try to launch the control screenlet i get > /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 0xc50a50> org.screenlets.Clock /org/screenlets/Clock at 0xc32a70> implementing 'org.screenlets.ScreenletService' at 0xc33ea8>
Introspect error: The name org.screenlets.Clock was not provided by any .service files
Traceback (most recent call last):
File "/usr/local/share/screenlets/Clock/ClockScreenlet.py", line 433, in <module>
screenlets.session.create_session(ClockScreenlet)
File "/usr/local/lib64/python2.5/site-packages/screenlets/session.py", line 301, in create_session
session.start()
File "/usr/local/lib64/python2.5/site-packages/screenlets/session.py", line 155, in start
srvc.add('')
File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 25, in __call__
ret = self._proxy_method (*args, **keywords)
File "/usr/lib64/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

[some-guy]

i have awn install too :D. And screenlets 0.0.7 works \o/
strange........

[krkhan]

I get the same dbus exceptions on all screenlets and manager too, even though:

[kamran@orthanc ~]$ ps -A | grep dbus
2343 ? 00:00:00 dbus-daemon
2728 tty1 00:00:00 dbus-launch
2729 ? 00:00:01 dbus-daemon


:(