"Timeout has expired" error on resume from hibernate

I can confirm this.

I can confirm this too. It also occurs after resuming from suspend.

Setting package temporarily from (undefined) to gnome-screensaver.
Can you confirm this bug still happens in edgy/feisty?

Thank you.

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further and it has been outstanding for a very long period of time. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

This is happening for me as a new regression after upgrading to Karmic. It happens 100% of the time coming back from suspend, and I think also from hibernate.

What seems to be happening is this: the unlock dialog appears on the screen just before the machine suspends, so that dialog thinks too much wall time has expired when the machine wakes up.

A few seconds after the "timeout has expired" message comes up the unlock dialog disappears, leaving the screen blonk, so people may think the machine has failed to resume.

Confirmed to be still present in package version gnome-screensaver 2.28.0-0ubuntu3 (Karmic).

My error is similar to this behavior, only not precisely this. My screen says "Time has expired" above the password prompt, and then goes blank. Karmic, current.

This bug appears to be present in Lucid Lynx alpha 2. (gnome-screensaver 2.28.0-1ubuntu5)

happens 100% of the time for me, i concur with #5; this makes the process feel very flaky; and the mouse cursor does disappear when the screen is blanked again after the dialogue "times out" the first time, further, it makes resuming from hibernation all the more chunky. it would be preferable if there were some resume feedback until it tries to show the cursor or the dialogue, because both are very very chunky until the machine stops swapping in pages some seconds later

if i were taking a stab at fixing this i would make sure i'd be sure the screen was blanked before resume before starting feedback throbbers or whatever, then do the dialogue completely after resume (and in the case of hibernate, until paging io has calmed down a bit so the mouse cursor doesn't jump around and the machine interactivity is actually tenable for entering your credentials)

if still present, I haven't seen it in ages. (lucid lynx beta 2)

If it helps, I'm still reliably seeing it in Lucid, on every resume from suspend.

Running 10.04 and it happens to me almost every time

10.04 and also happens to me on 50% resumes from suspend (I don't use hibernate).

If you use a laptop, and close the screen, and require a password to be entered to return to the desktop, the text box sometimes shows with this message. it then closes and a fresh dialog shows.

Presumably the dialog was triggered before sleep and it has a lifespan set which will be expired when when you return to the laptop later.

It wastes about 5 seconds every time you open your laptop - so whilst the bug might be minor in that it doesn't affect functionality, I am tired of seeing it, and I suspect I am a fairly forgiving user.

This is currently occurring on about 40% of resumes for me (ubuntu 10.04), on a Dell Inspiron 1420N (sold with ubuntu). Just to clarify, for me, I always see either behavior (a), or I see (b) followed by (c).

Over several ubuntu releases, it seems like this problem has disappeared and reappeared, perhaps multiple times. Although it's fairly easy to work around once you realize what's happening, for me it's probably ubuntu's most obvious flaky behavior. Perhaps the importance of this bug should be increased.

Does this bug really deserve Importance=low? At least my wife complains about this every time, also I see this as really annoying making Ubuntu look "unready".

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...

Log from correct behaviour

Some of you may want to check this out.
http://ubuntuforums.org/showthread.php?t=263356

Just mentioning that this bug still happens in Maverick

I also think this bug should receive a higher priority. After suspend I usually have the "Time has expired" message. Normally this isn't a problem but recently I had a complete freeze of the system and I couldn't enter my password at all. I couldn't reproduce this on a subsequent test though. Even if this bug is unrelated to my freeze up, I think the "Time has expired" message is something that many Ubuntu users have encountered and gives a bad impression....

This bug should definitely receive a higher priority. Faster resume times are one of the big focuses of the latest computers and OSs like the Air and Google's Chrome OS netbook. Not being able to type in your information for 4 or 5 seconds and having to hit several keys to get the prompt to come up is a big pain by comparison.

I should also probably mention that of the four laptops I work with, this error only occurs on the one which doesn't automatically resume upon the lid being opened. On the machine with the error, my Asus 1015PEM netbook, it won't resume unless I press a button after opening the lid. My other three machines resume simply by the lid being opened.

Could the error be related to resetting a timer based on a lid-open event that doesn't occur when a key-press is used like with my 1015PEM netbook?

Hi,

On Sun, Dec 12, 2010 at 05:46:38AM -0000, CTenorman wrote:
> I should also probably mention that of the four laptops I work with,
> this error only occurs on the one which doesn't automatically resume
> upon the lid being opened. On the machine with the error, my Asus
> 1015PEM netbook, it won't resume unless I press a button after opening
> the lid. My other three machines resume simply by the lid being opened.
>
> Could the error be related to resetting a timer based on a lid-open
> event that doesn't occur when a key-press is used like with my 1015PEM
> netbook?

No, I see this problem on my HP Mini 110, which properly resumes on lid open.

-Forest

Could the people affected by this bug please state what make and model of laptop it appears on? Since it doesn't seem to be appearing on every laptop, I'm lead to believe it may be a hardware issue. I've noticed two netbooks in the comments above. What everyone else got?

Hp Compaq nx7300
Hp Compaq nx7400 x3
Asus Eee PC 901 x2
Acer mumblemumble (3 different models that I havn't got in front of me)

I've also seen it on various desktop's that I have suspended, but I rarely suspend them it's just for testing.

I don't think I've personally seen a computer where it doesn't happen, although it does not seem to occur if you resume immediately, it needs a few minutes.

HTH

lilphil

Mine is a FSC Amilo Pi 1536 (not a netbook). I need to press the power button in order to resume (does not resume on lid-open or on ordinary key press). I think I haven't seen the problem on this laptop in the releases before Maverick.

Apple MacBook4,1. Happens intermittently (about once every 30~40 wakeups) after opening the lid.

Sony Z21 MN, running lucid lynx.
Last time this happened I could not even do the "alt + SysRq + REISUB" trick to gently reboot the system, it was a complete freeze!

I'm going to invalidate this as a paper cut since the problem isn't apparent on every computer, which leads me to the conclusion that this is a hardware issue. A paper cut should be a small usability flaw that is present in all default installations of Ubuntu.

Happens most of the time when resuming from standby on my Asus X58L laptop running Ubuntu 10.04 (Lucid Lynx) x86_64.

I can see it on a Dell Inspiron N5010 using Lucid (10.04).

The laptop resumes on opening the lid and then the dialog momentarily appears, the "Time has expired" message shows for a few seconds and then the dialog disappears. I can start entering characters once the unlock dialog reappears.

This bug happens everytime I open my netbook from suspend. Even though suspend works everytime, the brief flashing of the "Time has expired" message makes it look glitchy.

I have an Asus 1015PEM.

this happens to me all the time in oneiric. even when simply locking with cntrl+alt+L

I get this in oneric with after I haven't used the computer in a few hours (like overnight). It happens every time. I have gnome3 installed.

I'm getting this in onieric as well. For me at least, I can't do anything other than force a reboot. This should have a higher priority, IMO.

I have had this same problem since at least Maverick Meerkat. It always happens, and my wakeup is always slower than it ought to be. Once the screen has gone black, it will 'come back' normally and everything works, but it's a ridiculous situation.

I'm no longer affected in Ubuntu 11.10 regular Unity (not Unity 2D).

And I see the problem on a Lenovo 3000 n500 with integrated video using i915 driver.

Is there anywhere we can compile this whole list of hardware and work out the commonalities with the hardware? We've listed quite a few systems here, but I fear everyone's waiting for someone else to look into it.

I'm running a Dell Inspiron N5010. I encountered this problem consistently with Ubuntu 10.04 (a few times a day) and have not encountered it in Ubuntu 11.10 yet. I have been running 11.10 for more than a week without problem.