After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 481090 - "Pictures folder" shows all pictures in $HOME
"Pictures folder" shows all pictures in $HOME
Status: RESOLVED INVALID
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.20.x
Other Linux
: Normal major
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-27 20:39 UTC by Pedro Villavicencio
Modified: 2008-11-13 15:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Pedro Villavicencio 2007-09-27 20:39:26 UTC
This bug has been filled here:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/145152

"I noticed that the "Pictures folder" screensaver shows all pictures out of $HOME instead of only $HOME/Pictures. Even pictures with sensible information out of my projects or pictures out of the cache of my web browser - ~/.mozilla/firefox/<random>.default/Cache - will be displayed. This might lead into showing pictures which you don't want to display in public.

I've got a folder called "Pictures" inside my home dir.

# ls -al ~/Pictures/
insgesamt 880
drwxr-xr-x 2 toff toff 120 2007-09-26 11:53 .
drwxr-xr-x 102 toff toff 4168 2007-09-26 12:00 ..
-rw-r--r-- 1 toff toff 252369 1999-11-20 00:00 1.jpg
-rw-r--r-- 1 toff toff 248626 1999-11-20 00:00 2.jpg
-rw-r--r-- 1 toff toff 390383 1999-11-26 00:00 3.jpg

But these pictures don't get displayed. Instead of those three pictures, gnome-screensaver looks in my whole $HOME for pictures.

This is not a real security threat. But since there is a option for a random screensaver. Users might find this "feature" quite unpleasent, when co-workers find out what the boss is doing late at night only by watching the screensaver..."
Comment 1 Pedro Villavicencio 2007-11-05 16:47:14 UTC
*** Bug 492949 has been marked as a duplicate of this bug. ***
Comment 2 Sebastian Breier 2008-10-03 22:59:49 UTC
Can anybody confirm that this is still happening? Doesn't for me.
Comment 3 Christoph Langner 2008-10-23 19:04:39 UTC
I also think that this bug is fixed. Something like this never happend again inside hardy or intrepid. Marking this bug as "fix released"...