Comment 70 for bug 322202

Thanks for the tip George, that's actually the first thing I tried since I figured the script has got to "run" somehow. It didn't help though. I'll try again and see how it goes.

I did however play around with this fix and it behaves rather weird. This is what I did:
1) I turned on my laptop from a full shutdown, logged in and opened a nautilus window.
2) Issued the "/etc/init.d/bluetooth stop" command in the terminal and suspended the laptop with Fn+F4.
3) I then resumed it with Fn+F4 and it worked just fine - session was locked and I could go back to my desktop with the above mentioned nautilus window, just as I left it.
4) I then started bluetooth with "/etc/init.d/bluetooth start" and suspended the laptop again WITHOUT killing bluetooth.
5) When I woke up the laptop the session was active and locked just as if I killed the bluetooth service (which I didn't do).
6) When I tried to suspend the laptop for the third time the hotkey (Fn+F4) didn't work at all, so I just clicked on "Suspend" in the Menu.
7) Yet again it woke up just fine, without messing with bluetooth.

At this point I shut down the system and started it again to do more tests, as follows:
1) I logged in and without doing anything I suspended the machine. It resumed just fine! Previously I was kicked out to GDM _every_ single time.
2) I suspended and resumed again and again it worked just fine.
3) I started and stopped bluetooth and then suspended - I was kicked out to the GDM.
4) I logged back in and stopped bluetooth, suspended and on the resume I was back to the GDM.
5) Once I logged back in I could suspend/resume without messing around with bluetooth (tried two times in a row and it worked both times).

I really don't know what conclusions to draw from that apart from the fact that it has something to do with bluetooth but we're not quite there yet... Any ideas guys?