Bug 1276727 - Terminal theme preferences don't change immediately
Terminal theme preferences don't change immediately
Product: Fedora
Classification: Fedora
Component: gnome-terminal (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-10-30 12:08 EDT by Jiri Prajzner
Modified: 2016-07-19 15:58 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 15:58:42 EDT
Type: Bug
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 Jiri Prajzner 2015-10-30 12:08:37 EDT
Description of problem:
When user changes Terminal theme preferences, those don;t change immediately at the first time. Instead they change only after re-entering the menu.

Version-Release number of selected component (if applicable):
GNOME Terminal 3.16.2
A terminal emulator for the GNOME desktop
Using VTE version 0.40.2 +GNUTLS

How reproducible:
Every time after a fresh start on the first try

Steps to Reproduce:
1. Open Terminal > Preferences 
2. Uncheck Use dark theme variant

Actual results:
No change. User has to re-enter the menu

Expected results:
Theme changes immediately

Additional info:
Comment 1 Fedora End Of Life 2016-07-19 15:58:42 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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