Bug 700077

Sorry, the problem does seem to occur in other "apps" too, but is much more subtle there.

Case in point: in plasma (kde desktop), the top taskbar has a piece of it (to the right hand side) that looks as if it has been "eaten" away, depending on its size. The bottom taskbar has some short white lines near its right hand side (covering the clock, and the systray)

===> so seems to be an i915 graphics driver problem... (... and very hard to debug, as the module cannot be unloaded unless modeset=0 is set, but in that case, the X server can only be started with a ridiculously small resolution...)

All this happens with all possible accelerations switched off:

Section "Module"
        Disable "extmod"
        Disable "dbe"
        Disable "dri"
        Disable "dri2"
        Disable "glx"
        Disable "record"
EndSection

Section "Device"
        Identifier  "Videocard0"
        #Driver      "intel"
        #Driver      "vesa"
        #Driver      "fbdev"
        VendorName  "Videocard vendor"
        BoardName   "Intel 865"
        #VideoRam    8192
        VideoRam    4096
        Option "Accel"   "Off"
        Option "NoAccel"   "True"
        Option "DRI" "False"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device "Videocard0"
EndSection

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Screen0"
EndSection


With vesa or fbdev driver, the achievable resolution is too small to judge whether the problem is gone, or just scrolled off the right hand edge of the screen.

Actually, after further trial & error, I discovered a setting that works:

Option "Shadow" "On"

This on its own seems to "fix" the problem, no other settings needed (such as disabling modules, Accel Off, ...)

Maybe this could be auto-selected upon detection of an 82865G chip?

# lspci -vn | fgrep -A10 -i vga
00:02.0 0300: 8086:2572 (rev 02) (prog-if 00 [VGA controller])
        Subsystem: 1028:0174
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at ed98 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power Management version 1
        Kernel driver in use: i915
        Kernel modules: i915


# lspci -v | fgrep -A10 -i vga
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Dell Device 0174
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at ed98 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power Management version 1
        Kernel driver in use: i915
        Kernel modules: i915

I suspect this bug is actually an xserver bug, and should be fixed by xorg-x11-server-1.10.1-14.fc15.  Please test, and reopen if this problem still occurs (with NoAccel; obviously shadowfb works around it as well).

I just upgraded to xorg-x11-server-Xorg-1.10.1-14.fc15.i686 , but the problem still occurs (with NoAccel and without Shadow)

Are you using any particularly special cursor theme?

Does this go away (or at least look different) if you say Option "SWCursor" "on" in the intel driver section?

Can you attach a screenshot of the corruption?  The Print Screen key in Gnome should capture one for you.

Created attachment 498332 [details]
Mouse droppings in Thunderbird message list

No, even with SWCursor, the problem remains.

On the attached screenshot, you can see not only that the mouse leaves droppings (message list top right), but also that the taskbar has short white stripes (see near the digital clock, and elsewhere)

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping