A bug I've noticed with GNOME3 (GNOME-shell) is that the screensaver locking often hasn't taken effect when the machine suspends. So when the machine resumes, you are shown the desktop that was there before, and *then* (sometimes after seconds) it switches to the lock screen. This could be a problem if there was sensitive content on the desktop prior to suspending.
I guess the GNOME3 screen saver isn't synchronised with the suspend process, such that it ensures the screen locking code has run before suspend occurs.
I don't remember either way whether or not this occurred before GNOME3. Maybe it's a long-standing bug, maybe not. If a long-standing Linux suspend / screensaver bug, then I suspect it's more noticeable with GNOME3 because of some slowness somewhere or races that become more apparent with the heavier-weight nature of GNOME shell (RAM wise particularly) - resume takes a lot longer with GNOME shell.
On my multi-monitor, work desktop, I've noticed with GNOME3/Cinnamon the screensaver can sometimes kick in but still leave 1 desktop monitor setup visible - though you can't interact with it. You have to type the password blind to get in. Fun...