Bug 466792

Summary: Erratic cursor and text display when emacs uses X-window display; Toshiba A305-S6857
Product: [Fedora] Fedora Reporter: Richard Ryniker <ryniker>
Component: xorg-x11-drv-i810Assignee: Adam Jackson <ajax>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: rawhideCC: mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: xorg-x11-drv-i810-2.5.0-1.fc10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-29 23:21:46 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
Xorg startup log.
none
Xorg startup log for working, revised configuration. none

Description Richard Ryniker 2008-10-13 16:41:34 UTC 
Description of problem: emacs window suffers erratic display of cursor and
keyboard-entered data.  Hardware:  Toshiba laptop A305-S6857, Intel
Graphics Media Accelerator X3100.  Software:  Fedora 10 snap1 installed
to hard drive, updated from rawhide.


Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-2.4.2-9.fc10.x86_64
emacs-22.2-5.fc9.x86_64
emacs-common-22.2-5.fc9.x86_64

How reproducible: always with local (laptop) display.  Does not occur when
using remote display (different host, different display hardware).


Steps to Reproduce:
1. Start emacs with X-window display.
2. Observe cursor, enter text or use cursor movement keys.
3.
  
Actual results:
After a short while (less than 30 seconds) the cursor disappears (stops
blinking).  It may re-appear some seconds later, then disappear, etc.
When entering text from the keyboard, display of characters typed may
stop.  Ctrl-L forces redisplay of window, then the missing characters appear and
cursor display resumes, but the condition is likely to recur a short while later.

Expected results:
No interrupted display of cursor or characters entered from keyboard.

Additional info:
Comment 1 Richard Ryniker 2008-10-13 16:43:53 UTC 
Created attachment 320202 [details]
Xorg startup log.
Comment 2 Richard Ryniker 2008-10-14 01:43:17 UTC 
Improvement.

Executed system-config-display, which would not offer the native display
resolution of 1280x800 but 1024X758 at best.  Manually configured as a
generic LCD display with 1280x800 resolution, using system-config-display.

Early indication, after reboot, is this has corrected the problem.

I surmise it is the presence of an xorg.conf file, rather than this specific
display definition, that results in superior initialization of the X server.
I shall attach the present, working Xorg startup log so it can be compared
with the original log.

This bug is probably incorrectly associated with component xorg-x11-drv-i810
now, but where it belongs is not clear to me.
Comment 3 Richard Ryniker 2008-10-14 01:46:37 UTC 
Created attachment 320240 [details]
Xorg startup log for working, revised configuration.
Comment 4 Matěj Cepl 2008-10-14 14:10:26 UTC 
Isn't this duplicate of bug 463023 ?
Comment 5 Matěj Cepl 2008-10-14 14:27:08 UTC 
(In reply to comment #4)
> Isn't this duplicate of bug 463023 ?

No, it isn't
Comment 6 Matěj Cepl 2008-10-15 08:52:00 UTC 
Are you using compiz?
Comment 7 Richard Ryniker 2008-10-15 20:07:11 UTC 
Compiz is part of the Snap1 live image that was installed on this machine,
and the compiz libraries are present.  However, "desktop effects"
(System->Preferences->Look and Feel->Desktop Effects->Enable Desktop Effects)
was never selected.  Therefore, if I understand your question accurately,
the answer is "No."
Comment 8 Richard Ryniker 2008-10-15 20:13:30 UTC 
"Improvement" reported in Comment #2 is incorrect.  The problem continues.

I have a qualitative impression it is less frequent than originally
perceived, but it definitely occurs.
Comment 9 Richard Ryniker 2008-10-29 22:38:15 UTC 
Bug fixed after update from xorg-x11-drv-i810-2.4.2-9.fc10.x86_64
to xorg-x11-drv-i810-2.5.0-1.fc10.x86_64 (or maybe by a change in
a related package).  I assume this was an upstream change, and therefore
this report can now be closed.