xorg crashes 1 time in 5 when attempting to sleep

Bug #1027619 reported by Stephen Wilson
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I am running xubuntu 12.04 on a Thinkpad X301. Since I first installed 12.04 a few months ago, everything worked fine for a couple of months. But a few weeks ago (i.e. early July 2012), I started getting xorg crashes.

The crashes happen when the computer is attempting to sleep (suspend, not hibernate), either because I closed the lid or because I left it on long enough for sleep to kick in automatically. It happens about 1 time in 5 that sleep is attempted. I get returned to the login screen. Sleep does not complete. The flashing moon light continues to blink. I can log in again and continue, but nothing works properly... no wireless, docky will not launch, everything is very slow, etc.

These frequent crashes make xubuntu 12.04 completely unusable. I hope that a solution can be found soon.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Sun Jul 22 06:11:00 2012
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Package: xorg 1:7.6+12ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Tags: precise
Uname: Linux 3.2.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo

Revision history for this message
Stephen Wilson (smwilsonau) wrote :
Revision history for this message
Stephen Wilson (smwilsonau) wrote :

By the way, the title generated by apport is:

Xorg crashed with SIGABRT in XIChangeDeviceProperty()

tags: added: apport-collected
description: updated
Revision history for this message
Stephen Wilson (smwilsonau) wrote :

I have a crash report generated in /var/crash and various other log files which might be relevant. Please let me know what I should upload.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
joeaguy (joeaguy) wrote :

I have a ThinkPad t420s and have the same issue.

I can suspend to ram successfully several times, but under normal usage, after the 3rd or 4th time Xorg crashes and I am sent back to the login screen. The moon icon flashes and then stops. Once on the login screen, logging in does not work, control-alt-F1 (etc) do not get me to a login terminal. If I select shutdown, the computer goes to sleep during shutdown, and I have to wake it order to finish shutdown. The computer is generally not usable until I reboot.

I have tried booting and then putting my computer to sleep and waking it up repeatedly, running different programs in between each cycle, to try and find some trigger that reproduces the problem. I could not reproduce the problem this way. The crash has only happened for me after continuous normal usage. I have not been able to artificially create the conditions for the crash.

Let me know if there are any logs or other data I can provide to help diagnose.

Revision history for this message
Stephen Wilson (smwilsonau) wrote :

Yes, joeaguy, these symptoms sound identical to mine.

I also think this other bug is probably the same:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1026777

Revision history for this message
Rik Shaw (rik-shaw) wrote :

indeed I believe this bug seems identical to what I am experiencing and have reported on in bug 1026777 (as linked to above in comment #6).

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.