Bug 486593

Summary:	Open Plasma Vault Dialog Text Box Does Not Have Focus
Product:	[Plasma] Plasma Vault	Reporter:	Dashon <dashonwwIII>
Component:	general	Assignee:	Ivan Čukić <ivan.cukic>
Status:	VERIFIED UPSTREAM
Severity:	normal	CC:	dashonwwIII, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=485430
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dashon 2024-05-04 22:12:38 UTC

SUMMARY
Sometime after the update to plasma 6, it seems that the password dialog window, that opens when you are unlocking a plasma vault, no longer has focus on the text box. This means you have to click to focus on the text box and then type your password. This is inconsistent with other plasma password dialogs which normally have focus on the input field so that you may immediately start typing.

STEPS TO REPRODUCE
1. Create a plasma vault.
2. Lock it if it isn't already locked.
3. Try unlocking it.

OBSERVED RESULT
Input field in dialog box does not have focus and I have to click on the input box.

EXPECTED RESULT
Input field should automatically have focus.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C95
System Version: 1.0

Comment 1 Nate Graham 2024-05-05 02:48:46 UTC

Can confirm. Seems like the same issue as Bug 485430 in Gwenview, which seems to have been caused by a Qt change. We could do the same change, but it might be better to see what happened in Qt and maybe fix it there.

Comment 2 Dashon 2024-05-24 23:56:33 UTC

I updated to Qt 6.7.1 as well plasma 6.1 beta in Arch and no longer seem to have this issue. The input box now has focus again upon opening, so I will close this issue as solved.

Comment 3 Nate Graham 2024-06-12 14:05:25 UTC

Can confirm, fixed now.