Bug 431674 - Viewing picts in GoogleEarth fails (and destablizes other graphics)
Summary: Viewing picts in GoogleEarth fails (and destablizes other graphics)
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drivers   
(Show other bugs)
Version: 8
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-06 12:44 UTC by John Curcio
Modified: 2008-02-06 16:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-06 12:54:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description John Curcio 2008-02-06 12:44:16 UTC
Description of problem: While running the advanced graphics driver kmod-nvidia,
I can run GoogleEarth, however when I attempt to view a picture stored on
GoogleEarth I see only see black surrounded by the frame of the picture. Once
that occurs, most of my graphics stop working reliably ... such as choosing
firefox or the  shutdown pop-up window now only shows black.


Version-Release number of selected component (if applicable):
kmod-nvidia-96xx-2.6.23.14-107.fc8-96.43.01-20.lvn8
xorg-x11-drv-nvidia-96xx-96.43.01-3.lvn8.1
kmod-nvidia-96xx-96.43.01-20.lvn8


How reproducible:


Steps to Reproduce:
1.open GoogleEarth
2.view a picutre in GoogleEarth (tan button)
3.reopen firefox, etc 
  
Actual results:


Expected results:


Additional info:

dmesg and /var/log/messages show nothing

Comment 1 Ignacio Vazquez-Abrams 2008-02-06 12:54:59 UTC
Those drivers are not provided by Fedora.

Comment 2 John Curcio 2008-02-06 16:20:22 UTC
:-) I waited weeks to see if this would get fixed and the day I finally post the
problem is the day newer advanced drivers get posted ... and sure enough, fixed
the problem! :-) Timing is everything!

Please close this issue as fixed by the latest versions of drivers.


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