Bug 969699

Summary:	Any active text input freezes Qt apps in current F19
Product:	[Fedora] Fedora	Reporter:	Linus Torvalds <torvalds>
Component:	qt	Assignee:	Than Ngo <than>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	itamar, jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-01 22:44:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Linus Torvalds 2013-06-01 22:35:25 UTC

Description of problem:

Qt applications (current builds of the Qt version of "subsurface", but also things like "qt-creator" that comes with Fedora 19) lock up whenever a text field becomes active.


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

qt-creator-2.7.0-1.fc19.x86_64

How reproducible:

100%

Steps to Reproduce:
1. run "qtcreator some-file-to-edit"
2. Try to mnove around in the text with the cursor keys
3. Profit!

Actual results:

Hung application - trying to close it from the upper right corner will (after the five-second pause) result in "Qt Creeator is not responding" and "You may choose to wait a short while for it to continue or force the application to quit"

Expected results:

Able to move around and edit the file or text field.

NOTE! Qt-creator is just an example. It is not limited to Qt-creator.

Additional info:

This is an up-to-date as of today install of F19.

Comment 1 Rex Dieter 2013-06-01 22:44:09 UTC

See
https://admin.fedoraproject.org/updates/FEDORA-2013-9749/qt-4.8.4-19.fc19

and bug #968794

*** This bug has been marked as a duplicate of bug 968794 ***

Comment 2 Rex Dieter 2013-06-01 22:45:00 UTC

At least, I'm hoping it was the problematic qt-4.8.4-18.fc19 build to blame here.  holler if you have evidence to the contrary.