Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 213162 - Windows don't remember transparency settings when closes and reopened
Windows don't remember transparency settings when closes and reopened
Product: Fedora
Classification: Fedora
Component: compiz (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
Depends On:
  Show dependency treegraph
Reported: 2006-10-30 19:24 EST by Rodd Clarkson
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-14 18:15:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rodd Clarkson 2006-10-30 19:24:18 EST
Description of problem:

Being able to set windows as transparent offers some interesting options, but
sadly, when you set the transparency of a window, the state isn't remembered the
next time you open it.

For example, the Send and Receive Mail dialog in Evolution which come up each
time it's opened as solid, regardless of the transparency level set the last
time it was used.

Transparency should be like size (and location) which is remembered when the
window closes and then reused when opened (although sadly location seems to be a
bit of a black art).

Version-Release number of selected component (if applicable):

Comment 1 k3dzngrp8w2xtc9 2007-01-12 18:52:39 EST
Try Devil's Pie which can remember and set transparency of windows among other

Comment 2 Kristian Høgsberg 2007-08-14 18:15:14 EDT
When an application remembers the size and position of it's window, it's
something the application implements.  Either using the session protocol or in
gconf or similar.  In other words, it's something the application needs to support.

I would look into DevilsPie as suggested in comment #1.

Note You need to log in before you can comment on or make changes to this bug.