Screenlets 0.1.6 do not display on Ubuntu; Screenlets 0.1.4 work

[Reuben Firmin]

I pulled down 0.1.6 in an update a few days ago, and since then screenlets have not worked. I can see the processes running, but nothing is displayed. The screenlets manager will launch, but as soon as I press the start/stop checkbox for any of the supposedly running screenlets, it freezes.

[Märt Põder (boamaod)]

Please try to run the screenlets-daemon, screenlets-manager as well as individual screenlets from command line and provide the logs. Screenlets 0.1.6 works for other people, so probably you have a very specific bug. By now there is not enough information to deal with the bug.

[Märt Põder (boamaod)]

And also specify the Ubuntu version you are using.

[Reuben Firmin (reubenf)]

My bad, I thought I'd tried this yesterday w/ no logs. Here you go; this seems to include the error:

Warning - SolarTZ module not found
CachingBackend: Loading instances from cache
CachingBackend: Loading <Clock1>
opacity='1.0'
scale='1.0'
theme_name='station'
is_sticky='True'
keep_above='True'
lock_position='True'
is_dragged='False'
keep_below='False'
y='313'
x='3177'
skip_taskbar='True'
Found a running session of Clock, adding new instance by service.
Error in screenlets.services.get_service_by_name: org.freedesktop.DBus.Error.ServiceUnknown: The name org.screenlets.Clock was not provided by any .service files
Screenlet has already been added to /tmp/screenlets/screenlets.rfirmin.running
Loading instances in: /home/rfirmin/.config/screenlets/Clock/default/
Loaded config from: Clock1.ini
Set options in ClockScreenlet

[Reuben Firmin (reubenf)]

And, Ubuntu 11.10 w/ latest updates.

[Märt Põder (boamaod)]

My logs:

---
Warning - SolarTZ module not found
CachingBackend: Loading instances from cache
CachingBackend: Loading <Clock1>
theme_name='station'
is_sticky='True'
y='51'
keep_above='False'
lock_position='False'
is_dragged='False'
keep_below='True'
draw_buttons='True'
x='263'
skip_taskbar='True'
Creating new entry for ClockScreenlet in /tmp/screenlets/screenlets.mp.running
Loading instances in: /home/mp/.config/screenlets/Clock/default/
Loaded config from: Clock1.ini
Set options in ClockScreenlet
22067 /usr/lib/unity/unity-panel-service
OK - Clock has been initialized.

---
Warning - SolarTZ module not found
CachingBackend: Loading instances from cache
CachingBackend: Loading <Clock1>
theme_name='station'
is_sticky='True'
y='51'
keep_above='False'
lock_position='False'
is_dragged='False'
keep_below='True'
draw_buttons='True'
x='263'
skip_taskbar='True'
Found a running session of Clock, adding new instance by service.
Adding new instance through: <Interface <ProxyObject wrapping <dbus._dbus.SessionBus (session) at 0xa327d4c> :1.179 /org/screenlets/Clock at 0xa33248c> implementing 'org.screenlets.ScreenletService' at 0xa3325ec>

---
It seems that you have some kind of problem with DBus. Is it installed correctly? Is it a standard DBus of Oneiric? My 11.10 has dbus 1.4.14-1ubuntu1 and python-dbus 0.84.0-2 and works fine with 0.1.6.

[Reuben Firmin (reubenf)]

I also have 1.4.14-1ubuntu1 and 0.84.0-2.

I have not modified any dbug related settings as far as I know, and everything else seems to be behaving correctly.

[Chris (kyfho23)]

Here's my situation:

Ubuntu 11.10, all updates applied.
Screenlets 0.1.7

screenlets manager starts at login. However, using the manager to add screenlets does not start anything.

Starting /usr/share/screenlets-manager/screenlets-daemon.py from a terminal, after trying to get the "Wallpaper Clock" screenlet and ClockScreenlet set up give me the following output:

***
/usr/share/screenlets-manager/screenlets-daemon.py:223: Warning: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed
  item.set_always_show_image(True)
True
Starter already exists.
DAEMON FOUND!
Error in screenlets.services.get_service_by_name: org.freedesktop.DBus.Error.ServiceUnknown: The name org.screenlets.WallpaperClock was not provided by any .service files
True
True
REGISTER screenlet: ClockScreenlet
ScreenletsDaemon: registered ClockScreenlet
True
Traceback (most recent call last):
  File "/usr/share/screenlets/screenlets-pack-all/Clock/ClockScreenlet.py", line 553, in <module>
    screenlets.session.create_session(ClockScreenlet)
  File "/usr/lib/pymodules/python2.7/screenlets/session.py", line 480, in create_session
    session.start()
  File "/usr/lib/pymodules/python2.7/screenlets/session.py", line 254, in start
    sl = self.screenlet(session=self, id=self.__get_next_id())
  File "/usr/share/screenlets/screenlets-pack-all/Clock/ClockScreenlet.py", line 156, in __init__
    **keyword_args)
  File "/usr/lib/pymodules/python2.7/screenlets/__init__.py", line 837, in __init__
    self.load_buttons(None)
  File "/usr/lib/pymodules/python2.7/screenlets/__init__.py", line 1302, in load_buttons
    self.closeb = self.gtk_icon_theme.load_icon ("gtk-close", 16, 0)
glib.GError: Icon 'gtk-close' not present in theme
WallpaperClockScreenlet.desktop duplicate entry
Removed duplicate entry
Create autostarter for: /usr/share/screenlets/screenlets-pack-all/Clock/ClockScreenlet.py
***

Killing the screenlets manager from the manager-icon gives me this terminal output:

***
Error in screenlets.services.get_service_by_name: org.freedesktop.DBus.Error.ServiceUnknown: The name org.screenlets.WallpaperClock was not provided by any .service files
***

NOTE: "killall screenlets" and "killall screenlets-manger" have no effect.

Running "screenlets-daemon" from a terminal give me the first line of the output I posted above:

***
/usr/share/screenlets-manager/screenlets-daemon.py:223: Warning: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed
  item.set_always_show_image(True)
***

Running "screenlets-manager" from the command line starts the manager icon, opens the manager window (to be specific, the window where you can choose what you want displayed). However, starting this way leaves the "Start/Stop" option boxes greyed out. Also greyed out: AutoStart at Login. Terminal gives this output:

***
alien@P5NSLI:~$ screenlets-manager
True
Starter already exists.
DAEMON FOUND!

***
I tried with a variety of screenlets from the manager. Nothing shows up on the screen. Also, I don't know how to start an individual screenlet from the terminal.

[Chris (kyfho23)]

As always, anything you want me to try, report or dance a silly dance to will be experimented with. I draw the line at public nudity, however, for aesthetic reasons.

[Chris (kyfho23)]

uh....um...well, this wouldn't be the first time a problem has been solved by a reboot. Ignore me.

[Märt Põder (boamaod)]

Did you install some non-standard icon themes? It seems that there was a problem finding icons and that's why starting things failed. Glad, it's ok now, though.

[Chris (kyfho23)]

A ha! I never thought of icons as being part of the problem. Yes, I've got
the Buuf 3.2 icon set installed. However, as I said, a reboot got
screenlets running well.

Thanks again, not only for the reply, but for the thought involved. And if
you're one of the devs, thanks for the hard work.

Chris in Kentucky

On Mon, Feb 27, 2012 at 4:00 AM, tabbernuk <email address hidden> wrote:

> Did you install some non-standard icon themes? It seems that there was a
> problem finding icons and that's why starting things failed. Glad, it's
> ok now, though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/927101
>
> Title:
> Screenlets 0.1.6 do not display on Ubuntu; Screenlets 0.1.4 work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/screenlets/+bug/927101/+subscriptions
>

--
Check out my favorite radio station: Radio
Paradise<http://www.radioparadise.com/index.php>

*When the going gets weird, The weird turn pro ~ Hunter S. Thompson*
*
*
*
*