screenlets reposition if autostarted

Bug #235835 reported by Teo
2
Affects Status Importance Assigned to Milestone
gDesklets
Confirmed
Medium
gDesklets Core Team

Bug Description

On Xubuntu 8.04, with Compiz and Emerald, if I put gdesklets in autostarted applications the screenlets change position on reboot.
It happens only for some random items and the bug (?) isn't present if I run gdesklets from terminal.
Nothing related to desklets configuration or function.
Maybe only related to something else autostarted..
Teo.

Revision history for this message
Bjoern Koch (h.humpel) wrote :

Same thing here on ubuntu 8.04 (standard).
Sometimes some Desklets start in the upper left corner even though they should be somewhere else.
Very random! Amount and selection of these Desklets varies, but it seems that the Desklets which are first loaded are missplaced more often. The desklets which are loaded at the end are never missplaced (I am running about 8 Desklets).
This seems to happen only on autostart. After that I can type a "gdesklets restart" or "gdesklets slay && gdesklets start" (even a few times) and everything works fine again (no missplaced Desklets).

Changed in gdesklets:
assignee: nobody → gdesklets-core-team
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Bjoern Koch (h.humpel) wrote :

More news:
when restarting from terminal and using the workspace switcher things are getting - most times - messed up, too. Even the Desklets to be loaded at the end can be affected when switching workspaces.

Revision history for this message
Bjoern Koch (h.humpel) wrote :

And even more news:
bringing down things to just one workspace: trying to switch (using keys) doesn't affect the Desklets (probably as there is no switching ;) ).
Back to more than one workspace: switching workspaces messes up the position of some Desklets.
And even with only one workspace left some Desklets are randomly miss-positioned on auto-start.

Revision history for this message
Bjoern Koch (h.humpel) wrote :

Well, I still cannot figure out what is causing this problem, but it got worse here on my ubuntu system.
Strange thing, too: this doesn't happen (never ever until know as far as I remember) on my gentoo machine ?!

Anyway, all I could think of right now would be a dirty hack like a startup delay from within gdesklets (configurable). But this would really be a bad and dirty hack (if it would be working at all ?!) ....

Any opinions or other ideas on this one ?

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.