Bug 1133299 - Discolored bar when Docky is hidden on intel graphics
Summary: Discolored bar when Docky is hidden on intel graphics
Keywords:
Status: CLOSED DUPLICATE of bug 1119348
Alias: None
Product: Fedora
Classification: Fedora
Component: docky
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Meng
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-24 12:24 UTC by Richard Körber
Modified: 2014-08-25 00:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-25 00:48:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot (70.75 KB, image/jpeg)
2014-08-24 12:24 UTC, Richard Körber
no flags Details

Description Richard Körber 2014-08-24 12:24:06 UTC
Created attachment 930120 [details]
Screenshot

Description of problem:
When the Docky dock is hidden, a rectangular bar above the docking area is slightly discolored.

I could reproduce this bug only on Intel graphics. On another system with Nvidia graphics and the proprietary Nvidia driver, Docky works fine. I'm not sure if this is a Docky or Intel driver issue, but since Docky is the only program I had graphic issues so far, I reported it for Docky.

I use Cinnamon as desktop environment.

Version-Release number of selected component (if applicable):
docky-2.2.0-1.fc20.x86_64
kernel-3.15.8-200.fc20.x86_64
xorg-x11-drv-intel-2.21.15-7.fc20.x86_64

How reproducible:
Always (on Intel graphics).

Steps to Reproduce:
1. Start Docky
2. Hide the Docky dock

Actual results:
The dock hides, but a rectangular area above it is discolored.

Expected results:
The dock just hides.

Additional info:
Attached is a screenshot of the screen's bottom. It was made while the Docky dock is disappearing. The discoloration is already visible above it.

Comment 1 Christopher Meng 2014-08-25 00:48:39 UTC

*** This bug has been marked as a duplicate of bug 1119348 ***


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