Tilda without true tansparency after system start

Bug #518447 reported by Waldgeist_dI
90
This bug affects 19 people
Affects Status Importance Assigned to Milestone
tilda (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: tilda

I included Tilda in my startup applications. After a fresh system start tilda can be opened with F12 (custom setting). However, despite its configuration, the appearing window does not provide true transparency. Once I've closed the fresh tilda console via ^d and restart tilda, true transparency reappeares. See also the screenshots.

What can I do to shed more light onto the issue?

Regards, Waldgeist

ProblemType: Bug
Architecture: i386
Date: Sun Feb 7 17:26:38 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/tilda
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
NonfreeKernelModules: nvidia
Package: tilda 0.09.6-2
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SourcePackage: tilda
Uname: Linux 2.6.32-12-generic i686

Revision history for this message
Waldgeist_dI (noway) wrote :
Revision history for this message
Waldgeist_dI (noway) wrote :
Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

I can confirm this on Lucid Lynx with Tilda 0.09.6-2. Restarting Tilda fixes this a while, but not for long.

Changed in tilda (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

I also get this on Lucid, but not on Karmic.

Revision history for this message
tonyx3 (tonybivens) wrote :

It's definitely doing this for me too in Lucid. No transparency if it autostarts at boot, but if i quit it and start it again manually, it's fine.

I don't get it. What's different about the command ':~$ tilda' being run by the startup applications manager from me running it from the terminal or clicking it in the applications menu? As far as I can tell, that's the only difference between the two instances.

Revision history for this message
Jeremy Wilkins (jer-wilkins) wrote :

Encountering exactly this issue immediately after upgrading from Karmic to Lucid.

Revision history for this message
opus440 (opus440) wrote :

Confirm. Clean install of Lucid. Did not have problem with Karmic.

Revision history for this message
Alexandre Bastien (alexandre-bastien) wrote :

Same for me, only occurs in Lucid.

I'm not sure but tilda might load before compiz, and is not able to get real transparency because of this.

A simple workaround for me was to load this script at boot time instead:

#! /bin/bash
sleep 5
tilda
exit

Revision history for this message
Waldgeist_dI (noway) wrote :

That last suggestions sounds very reasonable to me! But, luckily my laptop now works with tilda and transparency (64 bit Lucid) without workarounds. Have to test it with my other box, though. Will report back.

Revision history for this message
Waldgeist_dI (noway) wrote :

On my work system (64 bit Lucid) the problem persists. Autostarted tilda comes up without transparency. Will try your workaround, Alexandre!

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

Alexandre's script works for me. Obviously not ideal, but it's a decent workaround in the meantime.

Revision history for this message
Waldgeist_dI (noway) wrote :

Obviously, my statement was too fast and therefore incorrect. Both my two 64 bit machines start tilda w/o real transparancy which makes sense after Alexandre's explanation. My third box at home might be slow enough to bring up compiz first, because I didn't notice the flaw here. Maybe this kinda race condition can have different winners depending on rainfall or mean temperature of the last 11 days or so :] ... only joking, sorry!

Revision history for this message
Alexander (jufofu) wrote :

It's not an Ubuntu-specific bug, I have the same in Debian with XFCE and its compositing. The reason might be that Tilda starts before the compositing has started and chooses non-transparent mode.
http://bbs.archlinux.org/viewtopic.php?id=90305

Revision history for this message
Ryan Kelln (ryankelln) wrote :

Also affect by this bug, Lucid fresh install on SSD disk.

Possible work around is to use this command instead when starting Tilda in the start-up programs:

sh -c "sleep 2; exec tilda"

Revision history for this message
anubite (jirka-zarsky-gmail) wrote :

Same problem.

This work around works for me:
sh -c "sleep 2; exec tilda"

Revision history for this message
William F Pearson (wfpearson) wrote :

I'm almost sure this has to do with Tilda attempting to start before the compositing engine is ready. The "fix" here would be to have the ability to control startup application priority.

Revision history for this message
Sebastian Geiger (lanoxx) wrote :

This analysis is correct, tilda will start without real transparency if this is not supported by the window manager. Unfortunately there is not much that can be done in tilda. This is a problem of the startup script or what ever mechanism is responsible to start tilda. If tilda is started before compositing is active, then it just does not work.

I am closing this bug as Invalid.

Changed in tilda (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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