After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647396 - Graphical issues on NVIDIA hardware using provided drivers
Graphical issues on NVIDIA hardware using provided drivers
Status: RESOLVED DUPLICATE of bug 645814
Product: gnome-shell
Classification: Core
Component: drivers
3.0.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-10 22:13 UTC by Tamas
Modified: 2011-04-10 22:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Main Menu glitch (410.78 KB, image/png)
2011-04-10 22:15 UTC, Tamas
Details
Main Menu glitch scrolled to bottom (353.66 KB, image/png)
2011-04-10 22:17 UTC, Tamas
Details
Chat glitch with scroll bar at bottom (770.48 KB, image/png)
2011-04-10 22:18 UTC, Tamas
Details

Description Tamas 2011-04-10 22:13:30 UTC
There are several visual glitches that occur when scolling/scrollbars are visible. These glitches occur on both a NVIDIA 8400M GS and a NVIDIA GeForce 275 gtx on both the Fedora and openSUSE version of Gnome 3.0 available at http://www.gnome.org/getting-gnome/

Attached are some example images:
Comment 1 Tamas 2011-04-10 22:15:17 UTC
Created attachment 185669 [details]
Main Menu glitch
Comment 2 Tamas 2011-04-10 22:17:00 UTC
Created attachment 185670 [details]
Main Menu glitch scrolled to bottom
Comment 3 Tamas 2011-04-10 22:18:47 UTC
Created attachment 185671 [details]
Chat glitch with scroll bar at bottom
Comment 4 Jasper St. Pierre (not reading bugmail) 2011-04-10 22:34:40 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This was a bug in the nouveau driver. It has since been fixed. I'm not sure when the LiveCD will update.

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