Screenlets do not display at all in lxde/openbox

Bug #1087416 reported by David Dombrowsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Screenlets
New
Undecided
Unassigned

Bug Description

This might very well be a configuration problem on my end. I run xubuntu 12.04 with lightdm/lxde/openbox as by window manager. I can start the manager just fine from the command line, and select "clock" , and click "launch/add":

 davek@home$ screenlets
Xlib: extension "RANDR" missing on display ":0".
True
Starter already exists.
DAEMON FOUND!
True
Launch Clock
Logging output goes to: /home/davidd/.config/screenlets/ClockScreenlet.log
Xlib: extension "RANDR" missing on display ":0".
REGISTER screenlet: ClockScreenlet
True
Quit!

No obvious error message, and the daemon ends up in the systray, but there's nothing to be found. No window, no screenlet, no nothing. No errors in ~/.xsession-errors. I'm not sure where else to check.

Info:
Screenlets 0.1.6
Linux e2-07l 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
openbox 3.5.0-2ubuntu2
lxde 0.5.0-4ubuntu3

Revision history for this message
David Dombrowsky (davek) wrote :

This might be a clue:

 davek@home$ cat .config/screenlets/ClockScreenlet.log
Warning - SolarTZ module not found
CachingBackend: Loading instances from cache
Creating new entry for ClockScreenlet in /tmp/screenlets/screenlets.davidd.running
Loading instances in: /home/davidd/.config/screenlets/Clock/default/
No instance(s) found in session-path, creating new one.
WARNING: No theme found
OK - Clock has been initialized.
Failed to unregister from daemon: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
No more screenlets running.
Deleting global tempfile /tmp/screenlets/screenlets.davidd.running

dbus problem? What am I missing?

Revision history for this message
David Dombrowsky (davek) wrote :

This makes screenlets useless for me. I'll try building from source to see what I can find.

Revision history for this message
David Dombrowsky (davek) wrote :

If I run `dbus-launch`, and save the environment vars, I can get rid of the dbus error. But I still get no screenlet window.

Creating new entry for ClockScreenlet in /tmp/screenlets/screenlets.davidd.running
Loading instances in: /home/davidd/.config/screenlets/Clock/default/
Loaded config from: Clock1.ini
WARNING: No theme found
Set options in ClockScreenlet
OK - Clock has been initialized.
Restored instances from session 'default' ...

Revision history for this message
David Dombrowsky (davek) wrote :

I posted to "invalid" bug https://bugs.launchpad.net/screenlets/+bug/1048808/comments/2

So far I've not been able to get a local install to run.

    Traceback (most recent call last):
      File "/usr/share/screenlets-manager/screenlets-daemon.py", line 370, in <module>
        daemon = ScreenletsDaemon()
      File "/usr/share/screenlets-manager/screenlets-daemon.py", line 69, in __init__
        pixbuf = icontheme.load_icon("screenlets", 24, 0)
    glib.GError: Icon 'screenlets' not present in theme

And at this point I have to get back to work.... shelving screenlets hacking
again for another day.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.