Bug 78803 – Slooow cursor blink rate in quanta (and kate)

Bug 78803 - Slooow cursor blink rate in quanta (and kate)

Summary:	Slooow cursor blink rate in quanta (and kate)

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	quanta (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	wdovlrrw
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-11-30 15:24 EST by Claus L. Rasmussen
Modified:	2007-04-18 12:48 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-07-20 13:36:38 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Claus L. Rasmussen 2002-11-30 15:24:05 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
The cursor in quanta (and kate) blinks far to slow. And if you move it using the
arrow keys it disappears completely.


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


How reproducible:
Always

Steps to Reproduce:
1. Start quanta
2. Enter 'qwertyuiop'
3. Move the cursor back and forth using the arrow keys
	

Actual Results:  The cursor becomes invisible

Expected Results:  The cursour should have stayed visible

Additional info:

I have tried:

o RedHat's version of Qt, KDE, and quanta
o A version of KDE I compiled myself
o A version of quanta I compiled myself
o Adjusting the blink-rate in qtconfig
o Turning auto-completion and highlighting off
o Begging and cursing the machine

All to no avail...

Comment 1 Ngo Than 2003-07-20 13:36:38 EDT

please try quanta-3.1, which is included in RHL 9. It should fix this problem.

Note You need to log in before you can comment on or make changes to this bug.