Bug 199765

Summary: security icons usability problems
Product: [Plasma] Oxygen Reporter: kiddy
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CLOSED NOT A BUG    
Severity: normal CC: andrew.crouthamel, asraniel, kbugger, kde, sebas, wstephenson
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kiddy 2009-07-11 12:00:47 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

On installing kubuntu 9.04 the network plasmoid showed open/closed padlock icons to show whether wifi APs were encoded or unsecured. This was instantly clear since the padlock symbol is well established as representing a secure or unsecured connection in a browser context.

After updating the system new icons were shown that were a shield containing a green tick or a red cross. 

This is counter intuitive. The cross icon is commonly used to close a window or on a cancel button. It is generally negative or indicates something is wrong.

It appears that someone thinks an unsecured access point is somehow bad or wrong and is trying to project this idea onto all situations. This is inappropriate.

Many wifi hot spots require no security to access , this is legitimate, normal functioning.

In fact the tick suggests an AP is "good or OK" yet these are exactly the ones that generally cannot be connected to. 

I would suggest that these two icons are totally inappropriate and if anything should be the other way round. An X on a point that is secured and I cannot access would make more sense. 

In short , please revert to the older icons or come up with a better idea. The current ones are seriously unhelpful and confusing.
Comment 1 Will Stephenson 2009-07-23 09:37:52 UTC
reassigning to Oxygen project.

Oxygen: do you think we need padlock icons instead of security-*?
Comment 2 Andrew Crouthamel 2018-11-02 23:07:21 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 kiddy 2018-11-03 05:54:21 UTC
WOW nearly a decade for a NEEDSINFO response !

I no longer use KDE, but I don't see anything in this bug report that can not be quickly tested by anyone using KDE plasmoids. Are you still using the shield icons? That not something you outside help with , is it ? 

It could probably have been tested in the same time it took to enter the NEEDSINFO comment.  Or maybe this is just a robot posting a generic comment as a prelude to closing old bugs no one bothered looking at in ten years. ?  There is nothing in that comment that indicates the bug was ever read. 

Not a very encouraging response from KDE team.
Comment 4 Andrew Crouthamel 2018-11-05 02:57:24 UTC
(In reply to kiddy from comment #3)
> WOW nearly a decade for a NEEDSINFO response !
> 
> I no longer use KDE, but I don't see anything in this bug report that can
> not be quickly tested by anyone using KDE plasmoids. Are you still using the
> shield icons? That not something you outside help with , is it ? 
> 
> It could probably have been tested in the same time it took to enter the
> NEEDSINFO comment.  Or maybe this is just a robot posting a generic comment
> as a prelude to closing old bugs no one bothered looking at in ten years. ? 
> There is nothing in that comment that indicates the bug was ever read. 
> 
> Not a very encouraging response from KDE team.

A pseudo-robot. :) I'm just trying to help determine what is still valid for these old bugs. Sorry to hear about your dissatisfaction.
Comment 5 Justin Zobel 2022-12-02 01:23:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-17 05:13:17 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 7 kbugger 2022-12-17 07:02:24 UTC
(In reply to Bug Janitor Service from comment #6)
> 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!

Why do you have NEEDSINFO on this ?   Just read the original bug report and look at your icons:

>After updating the system new icons were shown that were a shield containing a green tick or a red cross. 
>This is counter intuitive. 

How hard is that ?
Comment 8 Bug Janitor Service 2023-01-01 05:19:45 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 9 kbugger 2023-01-01 07:43:31 UTC
Why do you have NEEDSINFO on this ?   Just read the original bug report and look at your icons:

I reported this 13 years ago and now you "need info" because you cannot be bothered to look at your own screen ?  FFS
Comment 10 Bug Janitor Service 2023-01-16 05:12:44 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 11 kbugger 2023-01-16 06:10:27 UTC
(In reply to Bug Janitor Service from comment #10)
> 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!

Five years on NEEDSINFO after nearly a decade before it gets a NEEDSINFO, because no one can be bothered to look at the icons. That means no one had even read the content of the bug report in 15 fickin years.  Way to go KDE.
Comment 12 Bug Janitor Service 2023-01-31 05:04:48 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 13 kbugger 2023-02-01 15:36:07 UTC
 >>  in 30 days the bug will be closed as RESOLVED > WORKSFORME

How does that work?  Works for WHO.  No one can even be arsed to look at their own icons instead of posting "needsinfo" BS.
Comment 14 David Edmundson 2023-02-01 15:54:15 UTC
No-one else things this is an issue. That's why it keeps getting auto closed. I shall make that more state more explicit.
Comment 15 David Edmundson 2023-02-01 15:55:50 UTC
Our default icon set (Breeze) does not use the shield icons.
Comment 16 kbugger 2023-02-01 15:59:52 UTC
many thanks David.  It only took FOURTEEN YEARS to get this far. I look forward to a slightly faster response next time I take the effort to open a bug report on KDE.   

on the other hand ....