Bug 312751

Summary: fbdev + radeonfb + overlapped xterm = screen corruption
Product: [Fedora] Fedora Reporter: Lev Melnkovsky <melnikovsky>
Component: xorg-x11-drv-fbdevAssignee: Dave Airlie <airlied>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: imc, mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-18 23:30:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
terminal screenshot taken with GIMP
none
sample xorg.conf
none
...and the logfile none

Description Lev Melnkovsky 2007-09-29 22:08:09 UTC
Description of problem:
xterm (I have tried other terminal emulators as well) window is corrupted if
another overlapping window is 

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

xorg-x11-drv-fbdev-0.3.1-2.fc7
xterm-227-1.fc7

How reproducible: Always

Steps to Reproduce: 
1. start two xterm windows
2. set color text background (like kernel menuconfig or Midninght Commander)
3. move one window by mouse overlaping another
  
Actual results: See screenshot

Comment 1 Lev Melnkovsky 2007-09-29 22:08:09 UTC
Created attachment 211431 [details]
terminal screenshot taken with GIMP

Comment 2 Matěj Cepl 2007-10-02 10:04:11 UTC
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.

Comment 3 Lev Melnkovsky 2007-10-02 19:29:07 UTC
Thank you very much for the response.

> Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
Unfortunatelu X11 fails to run without config and exits with

Fatal server error:
Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices


Comment 4 Lev Melnkovsky 2007-10-02 19:29:31 UTC
Created attachment 213871 [details]
sample xorg.conf

My real xorg.conf is longer, but the problem I described can be reproduced with
this config. The motivation of using "fbdev" rather than "radeon" driver is the
"Rotate" option. The bug, however, does not depend on "Rotate"...

Comment 5 Lev Melnkovsky 2007-10-02 19:30:56 UTC
Created attachment 213881 [details]
...and the logfile

Comment 6 Lev Melnkovsky 2007-12-22 18:17:41 UTC
Any hope to have the priority raised? The bug is still there in Fedora 8 :-(

Comment 7 Ian Collier 2008-02-18 16:47:31 UTC
This seems to be the same as bug 332791 and also
https://bugs.freedesktop.org/show_bug.cgi?id=12003 (which describes the problem
quite comprehensively).

I have experienced this bug on:
ATI Radeon X1300 Pro
xterm-231-1.fc7.x86_64
xorg-x11-server-Xorg-1.3.0.0-16.fc7.x86_64
xorg-x11-drv-fglrx-8.452.1-3.8.01.lvn7.x86_64

And also on:
nVidia Quadro NVS 285
xterm-231-1.fc7.x86_64
xorg-x11-server-Xorg-1.3.0.0-16.fc7.x86_64
xorg-x11-drv-vesa-1.3.0-8.fc7.x86_64

But *not* on:
ATI Radeon X1300 Pro
xterm-231-1.fc7.x86_64
xorg-x11-server-Xorg-1.1.1-47.9.fc6.x86_64
xorg-x11-drv-fglrx-8.40.4-2.lvn7.x86_64

The freedesktop.org bug mentioned above is using the sis driver.  Therefore this
looks like a core X server bug introduced somewhere between 1.1 and 1.2.

Comment 8 Matěj Cepl 2008-02-18 23:30:42 UTC
You are right. Closing as duplicate of bug 332791

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