Bug 357549

Summary:	ksysguard covers password dialog
Product:	[Unmaintained] ksysguard	Reporter:	gnastyle <BM-2cTv4XtvC9UQ8TdFCfPNySv2omc8T6m3sv>
Component:	ksysguard	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	justin.zobel
Priority:	NOR
Version First Reported In:	5.5.2
Target Milestone:	---
Platform:	Chakra
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description gnastyle 2016-01-04 22:39:49 UTC

When you start ksysguard from ctrl+esc it appears in "keep above others" mode,
that means other windows can't cover it.
This is great, except when you try to kill a root process.
In that case a window asking for privileges will appear, bu obviously it is covered by ksysguard and you cannot see it.
Please make the password window in "keep above others" mode, like ksysguard, when launched from ctrl+esc. 

Reproducible: Always

Steps to Reproduce:
1. launch ksysguard by pressing ctrl+esc as user
2. try to kill a root process
3. see the password dialog covered by ksysguard

Actual Results:  
the password dialog is covered and cannot be seen

Expected Results:  
the password dialog should be placed above ksysguard

Comment 1 Justin Zobel 2020-11-21 11:10:38 UTC

I've been testing this on ksysguard 5.20.3 and I can't replicate this issue as ksysguard is no longer started as an always on top window.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 2 Bug Janitor Service 2020-12-06 04:34:01 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2020-12-21 04:34:48 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!