Bug 715370 - F15 libreoffice welcome screen graphical corruption
F15 libreoffice welcome screen graphical corruption
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: libreoffice (Show other bugs)
15
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-22 13:05 EDT by Reartes Guillermo
Modified: 2011-06-22 15:31 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-06-22 15:31:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot (78.30 KB, image/png)
2011-06-22 13:05 EDT, Reartes Guillermo
no flags Details

  None (edit)
Description Reartes Guillermo 2011-06-22 13:05:51 EDT
Created attachment 506060 [details]
screenshot

Description of problem:

When at the libreoffice welcome screen, if you hoover "open", the sreen breaks until something makes it refresh.

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

libreoffice-core.x86_64      1:3.3.3.1-1.fc15 

kdebase.x86_64                6:4.6.3-1.fc15      @updates
kdebase-libs.x86_64           6:4.6.3-1.fc15      @updates
kdebase-runtime.x86_64        4.6.3-1.fc15        @updates
kdebase-runtime-flags.noarch  4.6.3-1.fc15        @updates
kdebase-runtime-libs.x86_64   4.6.3-1.fc15        @updates
kdebase-workspace.x86_64      4.6.3-5.fc15        @updates
kdebase-workspace-libs.x86_64 4.6.3-5.fc15        @updates

xorg-x11-drv-intel.x86_64     2.15.0-3.fc15       @updates

Actual results:
minor graphical corruption

Expected results:
no graphical problem

Additional info:

VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
Comment 1 Caolan McNamara 2011-06-22 15:31:43 EDT
filed upstream somewhere or other, not going to spend time on fixing this myself

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