Bug 490214

Summary:	space in front of password field in hotspot configuration in plasma settings
Product:	[Applications] systemsettings	Reporter:	renner0
Component:	kcm_networkmanagement	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jgrulich, kdedev, nate
Priority:	NOR
Version First Reported In:	6.2.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	6.3.0
Sentry Crash Report:
Attachments:	hotspot password field space character

Description renner0 2024-07-13 08:54:47 UTC

Created attachment 171621 [details]
hotspot password field space character

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. open wifi networking settings
2. click configuration button (above reset button)
3. show password of hostpot
4. type in password

OBSERVED RESULT
a single space character at the beginning of the password

EXPECTED RESULT
no space character

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Kinoite 40
(available in About System)
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

Comment 1 Ben Cooksley 2024-12-23 18:23:36 UTC

Bulk transfer as requested in T17796

Comment 2 TraceyC 2025-01-09 22:27:22 UTC

Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with either Plasma 5.27.11 (the current LTS version) or Plasma 6.2.4 (the latest released version)? I'm not able to reproduce this on 6.2.4.

If you can still reproduce the bug, please change the Status to "CONFIRMED". Thanks.

Comment 3 renner0 2025-01-11 18:27:32 UTC

Can reproduce with:
Operating System: Bazzite 41
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1

Comment 4 Nate Graham 2025-01-29 05:32:07 UTC

I can't reproduce this in current git master; must have been fixed.