Comment 17 for bug 50198

Hello,

I ran gnome-screensaver in foreground with --debug flag to see what is different when the timeout message occurs. Attached to this comment is the log from the case where I got the timeout message. As there is only one attachment per comment then I with the next comment I will include the log from a case where everything was fine - i.e. the password dialog didn't disappear immediately.

I will try to dig in the code to understand from the log why this happens but any help from someone who is more familiar with the source would be most welcome. Right now it looks like the message "Request unlock but dialog is already up" might point to the right direction - maybe the dialog is sometimes kept open from before the suspend and therefore receives the timeout...