Bug 87974 - Application Launch Cosmetic Bug
Summary: Application Launch Cosmetic Bug
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 9
Hardware: i686
OS: Linux
low
low
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-04 04:11 UTC by Aaron Ballman
Modified: 2006-03-14 19:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-04-04 17:34:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Aaron Ballman 2003-04-04 04:11:16 UTC
Description of problem:

When launching applications in RH 9, the UI-feedback is rather ugly.  You currently have an expanding rectangle that starts at the bottom of the screen, and grows larger.  This is fine with me, and it was great in previous versions of RedHat, where it was a grey rectangle.  I run RedHat 9 at work and at home, and on both machines, this rectangle is _yellow_.  I've tried finding someplace to change the color of this, or turn it off, but to no avail.  I think it's awesome that this is the ONLY gripe I can come up with for RedHat, but I still would love a way to get the grey rectangle back since this yellow thing seems to bother the hell out of me.

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


How reproducible:

Every time a new process is launched in X

Steps to Reproduce:
1. Launch a new process in X
2. Get out sunglasses and watch the scary yellow rectangle.
3.
    
Actual results:

No crashes or anything like that.  Just a disruption.  A yellow rectangle for the feedback UI (while the app launches).


Expected results:

I would expect to see a growing grey rectangle like in previous versions of the OS.

Additional info:

Comment 1 Mike A. Harris 2003-04-04 17:34:48 UTC
I have no idea why you filed this against XFree86, as XFree86 has absolutely
nothing whatsoever to do with this.


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