Bug 2050337

Summary:	Focused Form elements do not receive input
Product:	[Fedora] Fedora	Reporter:	Onyeibo Oku <onyeibo>
Component:	qutebrowser	Assignee:	Timothée Floure <timothee.floure>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	36	CC:	sanjay.ankur, timothee.floure
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-05 07:27:53 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 Onyeibo Oku 2022-02-03 18:02:17 UTC

Description of problem:
Text input boxes in forms (e.g. Log in, sign-in) receive focus but not text input from keyboard. Pressing [TAB] moves to the next indexed form element.  Buttons work but not text fields.

Version-Release number of selected component (if applicable):
2.4.0-2.fc36

How reproducible:
Its been consistent between reboots for some days

Steps to Reproduce:
1.  Update Fedora Rawhide to recent repo packages
2.  Fire up qutebrowser and try to log into an online account (e.g. bugzilla)
3.  *done*

Actual results:
Text input fields on the forms will only get focus but not receive text input

Expected results:
User should see text on screen as they are being typed into the textboxes

Additional info:

Comment 1 Ben Cotton 2022-02-08 20:17:13 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Timothée Floure 2022-06-02 18:53:49 UTC

My gut feeling says it's a qt issue, not directly a qutebrowser issue. Does the issue persist? If so, please paste the content your qutebrowser `:version` page here (so that we have more infos on your environment).

Comment 3 Onyeibo Oku 2022-06-17 11:11:13 UTC

rgr(In reply to Timothée Floure from comment #2)
> My gut feeling says it's a qt issue, not directly a qutebrowser issue. Does
> the issue persist? If so, please paste the content your qutebrowser
> `:version` page here (so that we have more infos on your environment).

nah, it's gone.
Latest is happening in Firefox.  You can close this ticket.