Bug 906745 - gnome-terminal opacity always resets to zero
gnome-terminal opacity always resets to zero
Product: Fedora
Classification: Fedora
Component: gnome-terminal (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-02-01 06:10 EST by Andre Costa
Modified: 2013-02-17 19:44 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-17 19:44:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 692753 None None None Never

  None (edit)
Description Andre Costa 2013-02-01 06:10:32 EST
Description of problem:
gnome-terminal background transparency is reset to zero after the last window is closed (which means all terminals are completely transparent at login)

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

How reproducible: always

Steps to Reproduce:
1. choose a profile, set its background to transparent and set transparency to a value between 0 and 100%
2. all other terminals with the same profile are affected immediately
3. close all terminals with the same profile
4. open another terminal with the same profile as before
Actual results:
new terminal is completely transparent (opacity is reset to zero)

Expected results:
transparency settings should be persistent

Additional info:
This has already been filed on Jun 2012 as bug 832716 but it might go unnoticed for F18 since it was filed for F17, thought I should open a new issue for F18.
I filed this bug upstream as well [https://bugzilla.gnome.org/show_bug.cgi?id=692753] and the response was: "Looks like a gconf bug to me; there's no code writing to the opacity gconf key when creating a new terminal."
Comment 1 Andre Costa 2013-02-17 19:44:37 EST
This is not a gnome-terminal bug, it's probably caused by gnome-settings-daemon. Just filed bug 912161 to track this. Closing as NOTABUG.

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