After resuming from suspend, can't start any programs

Bug #75342 reported by John S
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Sometimes (maybe 20% of times) when resuming from suspend-to-RAM, I cannot start any more programs from within my current desktop session.

This applies to using the menu on gnome-panel, but also when using my "Start a terminal" keyboard shortcut (metacity's responsibility, I think). I get a busy mouse pointer, but the program never starts up. This applies equally to all applications, including the log-off dialog: to log off I have to use ctrl+alt+backspace.

I can, however, start a program by switching to another VT, logging in, doing "export DISPLAY=:0.0" and running it from there. Further, if I start a terminal this way then that terminal's children are fine too.

This is not happening only with GUI applications. If I have gnome-terminal already open when I resume, then I can't run vim inside it, it hangs while trying to start. I will attach the output of "strace vim" from this situation, as an example.

The only workaround I've found so far is to ctrl+alt+backspace and then log in again, after which everything is fine (but of course I've lost my session).

Revision history for this message
John S (jcspray) wrote :

strace output of vim hung after resume

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Might be similar to bug #49221

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you and if so with which version of Ubuntu? Thanks in advance.

Revision history for this message
John S (jcspray) wrote :

I am still experiencing this on a regular basis in Edgy on my Thinkpad R50e.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for reporting this bug in Ubuntu. Can you reproduce the behavior under Feisty or newer Ubuntu? If so, can you please attach your /etc/X11/xorg.conf and /var/log/Xorg.0.log files, and the output from lspci -vv?

Changed in xorg:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Changed in xorg:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.