Bug 484692

Summary:	black cursor not visible against black window backgrounds
Product:	[openSUSE] openSUSE 11.1	Reporter:	Shrenik Bhura <shrenik.bhura>
Component:	Other	Assignee:	David Reveman <dreveman>
Status:	RESOLVED NORESPONSE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Shrenik Bhura 2009-03-12 10:50:24 UTC

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 (.NET CLR 3.5.30729)

I am using rdesktop and seamlessrdp to connect to some windows applications that have a text area with black background. In such cases the black cursor seems to be lost in the background. However, when using the cursor keys we can detect the movement with a white blink. 

This problem occurs irrespective of using seamlessrdp. I am not sure of the appropriate solution, however the solution given here -
http://swartzlander.org/rdesktop-1.6.0-bswartz-cursor.patch
seems to address this issue. This may be used to fix the same else an alternate solution is required. 

When running the same application in Windows purely, it clearly shows a visible cursor.

Reproducible: Always

Steps to Reproduce:
This may be tough to reproduce if you don't have access to a Windows application with such a black text-area. I am using an accounting software very specific to this region called Tally (version 7.2 or 9.0).
1. From a terminal run 'rdesktop <windows-terminal-server-ip-or-host>'
2. Open the application such as Tally having such a black text-area 
3. Navigate to the text-area and the cursor is no longer visible
Actual Results:  
Cursor not visible

Expected Results:  
Cursor should be visible in some clearly distinguishable color

Comment 1 Larry Finger 2011-04-04 03:02:14 UTC

The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!