Bug 127563 - colorization is mishandled in some applets
Summary: colorization is mishandled in some applets
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: i386 Linux
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-07-09 19:41 UTC by Zack Cerza
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-19 14:54:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshots (306.81 KB, application/x-gzip)
2004-07-09 19:54 UTC, Zack Cerza
no flags Details

Description Zack Cerza 2004-07-09 19:41:49 UTC
Description of problem:
Some panel applets become unusable when using a fully-opaque solid
color panel, and some will not recover until the panel color is reset
to "None."

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

How reproducible:

Steps to Reproduce:
1. Open "Panel Properties."
2. In the "Background" tab, choose "Solid color."
3. Move the "Style" slider to "Transparent." The panel should now be
transparent. This is shown in screen shots named '*-1'.
4. Move the slider to "Opaque." As shown in the screenshots named
'*-2', some of the applets become unusable.
5. Move the slider back to "Transparent." As shown in the screenshots
named '*-3', some of the applets recover and some don't.
Actual results:
See "Steps to Reproduce"

Expected results:
Panel applets should either gracefully obey color and opacity
settings, or else completely ignore them. Background color and text
color should not be allowed to be the same (or even too close, ideally).

Additional info:
Missing from the "Utility" screenshots are "InputMethod Switcher" and
"System Monitor" which keep making my panel crash... more on that later.

Comment 1 Zack Cerza 2004-07-09 19:54:27 UTC
Created attachment 101766 [details]

Comment 2 Mark McLoughlin 2004-07-19 14:54:27 UTC
Yeah, this is a known issue and I think most applets with the problem
have bugs reported against them (we need a bug for each applet). I'm
going to close this UPSTREAM since we'll probably never get around to
fixing each applet. It would be good, though, if you could ensure each
applet with the problem has a bug logged against it in
bugzilla.gnome.org. Thanks ...

Comment 3 Zack Cerza 2004-07-19 15:11:08 UTC
I meant to close this as UPSTREAM myself. I filed this bug on
gnome-panel and gnome-applets, but the one on -applets was closed as a
duplicate. I assume if I file 10 more, they will as well :)

Should I do it anyway?

Comment 4 Mark McLoughlin 2004-07-19 19:00:31 UTC
This one is still open, though:


but I'll close that one out as soon as I get a chance to catch up with
my upstream bug mail :-)

For each applet which you know has the problem, I'd first check to see
if the bug has already been logged and if not log it.

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