From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Description of problem:
When emacs is started with any backgroung except for white cursor inside emacs window takes a bold X shape. It makes inconvenient for users to select text. Moving cursor to the icon bar above text window fixes the cursor shape. Moving cursor to the menu bar changes the shape back to X. After the exit cursor stays X until it is pointed to another window, where it becomes normal again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. emacs -bg gray
2. have fun with the cursor
Actual Results: See description
Expected Results: Arrow or I shaped cursor.
The previous version emacs-21.2-18 did not suffer from that.
I tested this issue under GNOME, KDE, and Failsafe. The result is the same. Prior to testing I removed all files from home directory including ~/.emacs except for .cshrc.
emacs -bg white works fine.
Setting emacs.background X resource to any color produces the same result.
Does this still happen with RHEL3 U6 ?
What did you upgrade from? (emacs-21.2 hasn't
I can't reproduce this on RHEL4 or Fedora Core.
Sorry about the incomplete sentence. That should say:
"(emacs-21.2 hasn't shipped in RHEL3.)"
I used a system that was installed from original CDs I received from Dell
along with the system. I did not use any external source for emacs.
Today I have upgraded a system to everything latest:
[root@chico root]# cat /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 6)
Currently on that system:
[root@chico root]# rpm -q emacs
I tested emacs with not-white backgroup. The issue is still there, no changes.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.