By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2244 - TDE Menu Background cannot be changed/removed after changing it
Summary: TDE Menu Background cannot be changed/removed after changing it
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-12-08 15:09 CST by Kristopher
Modified: 2014-12-13 10:27 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Screenshot of this bug (188.23 KB, image/png)
2014-12-08 15:09 CST, Kristopher 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2014-12-08 15:09:41 CST 
Created attachment 2392 [details]
Screenshot of this bug

After changing the background of the TDE Menu several times, the background will cease to remove/change when I attempt to change it.

In the screenshot, you can see that the background is set to "Default" and the Apply button is disabled, suggesting that the background should be set to "Default". However, if you look at the TMenu, it is stuck on the "Light Gray" option, and changing the color does not affect the TMenu's background. Even after re-logging, I cannot change the background of the TMenu.
Comment 1 Kristopher 2014-12-13 10:27:33 CST 
Well this is a big whoops on my part. The "gray" background in the screenshot is coming from Configure Panel -> Appearance -> Advanced Options -> Use Deep Buttons . Removing the check mark from that option fixes this problem and allows changing the background of the TMenu.

Marking as RESOLVED INVALID due to my discovery that this is not an actual bug.