Bug 453743 - Admin password request is hidden by 'scanning devices' window
Summary: Admin password request is hidden by 'scanning devices' window
Status: RESOLVED DUPLICATE of bug 429770
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 21.12.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-13 15:05 UTC by Random Guy
Modified: 2022-05-13 15:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Random Guy 2022-05-13 15:05:13 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open KDE partition manager as normal user 

OBSERVED RESULT
Under wayland:  
The main window opens; the admin password request flashes on screen; then the 'scanning devices' window appears, pushing the main window (it's parent window) into focus and leaving the password request window in the background

Under X.org: 
Almost the same, except the 'scanning devices' window does not pull the main window into focus, but does still open on top of the password request window.  

EXPECTED RESULT
The password request window would be in focus after opening so the password can be entered without needing to look for the window, For example:
The partition manager would wait for admin permissions before it starts to scan devices, therefore leaving the password request window in focus, and opening the 'scanning devices' window after the password request was successful and that window has closed.  

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE plasma
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Graphics Platform: Wayland/X.org
Comment 1 Andrius Štikonas 2022-05-13 15:12:01 UTC

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