OK this is interesting and frustrating and the problem has been persistent for 6 or so months which lead me to roam a bit but I found out a bit more this morning.

Dell Latitude E6420
NVS 4200
i7 2820QM
16GB
/boot 512M
Swap 16G
/ 30G
/home the rest
Gnome (but happens in Mate and KDE also)
Bumblebee
XFS
system up-to-date as of this morning
No indicator of the problem in the logs

If I close the lid the computer suspends like it's supposed to but when I open the lid X locks. If I use the SW suspend button let it sleep then close the lid everything is fine (which I figured out this morning). When the problem first started happening I assumed it was a BB issue so I went from current nVidia to 340, and no love. I tried nouveau, no love. So I then disabled TLP, no love then I tried LMT both on and off no love.

Where do I look next? Pm-utils is not installed so there is no pm-suspend from the command line and my googling isn't telling me how gnome suspends without pm-utils.

To suspend using systemd via CLI, use
This wiki page may be helpful to you

https://wiki.archlinux.org/index.php...t_with_systemd

1 members found this post helpful.

I can't access the Arch Wiki at work so I'll read through when home.

I don't really want to suspend from the CLI I just want it to suspend when I close the lid and work when I open it. I'll assume then that gnome uses systemd PM which I've not looked at...Thanks

NVM I'd tested the new method a couple times I just let it sleep for an hour or so with the new method, it woke up then locked.

This reads like a graphics driver issue and related to bumblebee somehow. Examine the logs using journalctl. Since you report that the X-server crashes following resume, it might be necessary to reboot and examine the previous boot log using

FWIW, a thread I stimbles across while researching

https://bbs.archlinux.org/viewtopic.php?id=157583

If you can disable the NVIDIA graphics in the BIOS, then I would recommend doing that for diagnostic purposes and try a suspend/resume cycle again.

1 members found this post helpful.

Update I think the issue is time it seems to be fine if I don't let it sleep for a long time. Last night it was working again after some futzing in bb.conf so I put it to sleep and went to bed this morning it locked again. So I masked hybrid sleep about 5:30 this morning rebooted and put it to sleep. It's 9:20 right now and it woke up with out issue, so if hybrid sleep is the issue I'll have something new to look at.