Bug 495151
Summary: | xterm scrolling is broken | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Howells <dhowells> | ||||||||||
Component: | xorg-x11-drv-ati | Assignee: | Dave Airlie <airlied> | ||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | rawhide | CC: | bruno, fdc, mlichvar, pertusus, xgl-maint | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-04-17 06:01:19 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: |
|
Created attachment 339013 [details]
Kernel log
Created attachment 339017 [details]
Picture of broken xterm
This is most likely a video driver problem. David, Could you also add Xorg.0.log from the nomodeset attempt ? Thanks in advance --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 339088 [details]
X server log (nomodeset)
I don't know if this is the same issue or not, but with xorg-x11-drv-ati-6.12.1-9.fc11.x86_64 I am seeing improper scrolling in xterm as well. This is with the fvwm desktop, modesetting and an rv530. (I don't see this on another machine which is not using modesetting, is using gnome for a desktop and is an rv280.) When text scolls part of lines are not redrawn, so that only partial lines are visible. Switching to another desktop space and back results in the text being correctly redrawn. The behavior started recently, but because there were 2 or 3 releases in short succession, I didn't notice the issue until I was on -9. If you need to know which version it originated in I can do some further testing. xorg-x11-drv-ati-6.12.1-10.fc11.x86_64 still shows the problem with the xterm used in fvwm. It seems with today's updates I can use gnome again and I am not seeing the problem in the terminal program I run there. I tried this again with today's rawhide plus the following from koji: kernel-2.6.29.1-85.fc11.x86_64 mesa-7.5-0.11.fc11.x86_64 (and i586) xorg-x11-drv-ati-6.12.2-4.fc11.x86_64 and am not seeing the behavior any more. That works for me, thanks! |
Created attachment 339011 [details] X server log Description of problem: Scrolling in xterms under the rawhide X server using kernel mode setting is broken. Version-Release number of selected component (if applicable): xterm-242-3.fc11.i586 xorg-x11-server-common-1.6.0-17.fc11.i586 How reproducible: 100% Steps to Reproduce: 1. Start xterm. 2. Run "ls /usr/bin" in it. Note the position of the new command prompt in the window. 3. Scroll the window using S-PgUp and S-PgDown. Actual results: In 2, I see the ls generate more lines than the xterm can hold, but the prompt the shell generates after the ls doesn't wind up on the last line of the window, but rather several lines up. Several blank lines follow it. In 3, scrolling about causes the chunks of data in the scroll buffer to go missing and be represented on the screen by blank space. Sometimes individual characters of text will be partially obscured. Expected results: In 2, the bash prompt after the ls should be on the bottom line of the window. In 3, the data in the scroll buffer should be displayed correctly, no matter how much scrolling is done. Additional info: This does not happen if nomodeset is provided to the kernel. I have a Radeon X300 based chipset in my laptop, and I currently have no Xorg.conf file. I'm attaching the X server log and the dmesg log.