Red Hat Bugzilla – Bug 195628
Draws without clicking the mouse and out of screen
Last modified: 2009-01-09 01:57:38 EST
Description of problem:
Wierd pixels are drawn when I move the mouse.
I can even draw the same wierd pixels out side of the drawing area, and still
with out clicking the mouse.
See attached screenshot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Gimp.
3. Move the mouse around.
It draws pixels inside and out side of the drawing area.
It Should not draw pixels inside and out side of the drawing area.
My hardware is:
Mainboard: Asus A8N-VM CSM with nForce 430 chipset.
I am using the onboard graphicscard which uses a shared memory of 16MB. Could be
bug have something to do what that?
Created attachment 131017 [details]
Wierd pixels inside and outside of drawing area
I have a similar problem when returning from text mode. Please see
No mouse and very wrong colors when returning from text mode
If all goes as planned, I'll soon have an x86_64 machine with which I can test
this. Meanwhile, does this problem still show with a current gimp package
I don't know.
Installing the nVidia drivers "resolved" the problem...
Does this problem still exist on current Fedora versions (F7, (preferrably) F8)?
I have the same problem with Gimp on F8. Before reinstall from FC6 it was OK.
HW: Athlon XP, ATI Radeon 7000.
Michal, I assume that this is a problem in the X server/driver, possibly related
to bug #182517 (even though you have different hardware). I'll change the
component to xorg-x11-drv-ati and reassign.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 290151 [details]
X server config file
Created attachment 290152 [details]
X server log file
Created attachment 290153 [details]
X server log file, started without xorg.conf
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.