Bug 345309

Summary:	Locking with widgets still allows intruder to explore disk
Product:	[Unmaintained] plasma4	Reporter:	Ofnuts <ofnuts>
Component:	screensaver overlay	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	chanika
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ofnuts 2015-03-18 15:27:11 UTC

In the "widgets" screen locker, after hitting Alt-Control-L, it is still possible to explore the user's directories.

Reproducible: Always

Steps to Reproduce:
- Set screenlocker to the "widgets" version.
- Lock the screen, in top right corner you get a small menu with amont others, "settings"
- Click "settings", which lets you change the background image, then click "Open" at the bottom
- You can now navigate the users directories with a file explorer
- You can even hit the "erase field" icon in the filename filter to remove the filtering on image types.


Expected Results:  
After Alt-Ctrl-L, the system should be locked up tight. Of course there is the "Lock screen" menu for a complete lock but this makes the lock a two-step operation. The "leaky" state remains the default when the screen locks automatically (delay, lid closed...).

Running Kubuntu 14.04 with KDE 4.13.3 (and I don't undertand why the versions selector above limits me to 4.11).

Comment 1 Ofnuts 2015-03-18 16:42:18 UTC

With some more experimentation I find that in some cases the "tight" state occurs at once. But the "leaky" state also happens consistenly. I have not been able to relate this to some screensaver setting such as the lock delays or password delays or the method to enter the lock (time out, Altr-Ctr-L, Kshutdown menu>Lock or Launcher>Leave>Lock).

Comment 2 Nate Graham 2018-06-08 18:23:25 UTC

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham