Xorg freeze

[Michael Harden]

Binary package hint: xorg

information prior to the lockup......
...I was doing a search with update manager, to get any updates for the system, under the 2d environment. It reported that some of the repositories could not be downloaded. I went to the settings, to temporarily take out those repositories it could not download at that time, and was planning to run another search. .....// the lockup occured after it reloaded the repositories. it closed the reloading repositories window, but never got back to the synaptic screen. I then found out, the mouse was moving, but nothing else responds, this also seems to have locked up the main machine, or at least interfeared with vmware to switch to the main OS.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu1
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic i686
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
CurrentDmesg:
 [ 76.797783] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
 [ 106.974694] show_signal_msg: 6 callbacks suppressed
 [ 106.975559] nm-applet[1330]: segfault at 6 ip 0074c429 sp bf84c3c0 error 4 in libgtk-3.so.0.106.0[61d000+47f000]
Date: Fri Jun 17 12:33:45 2011
DistUpgraded: Log time: 2011-06-10 21:55:23.843971
DistroCodename: oneiric
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0-0-generic root=UUID=f4182b17-5455-4f0d-816f-c883cc141ce9 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to oneiric on 2011-06-11 (6 days ago)
dmi.bios.date: 12/31/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/31/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu3
version.libdrm2: libdrm2 2.4.25-2ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Bryce Harrington (bryce)]

Xorg freeze bugs need to have /sys/kernel/debug/dri/0/i915_error_state included.

[Bryce Harrington (bryce)]

Typically apport should capture this information automatically; I don't know why it didn't in this case. If it does in the future, report that bug and close this one. Otherwise, you'll need to manually collect that file (and dmesg) next time the freeze occurs.

[Bryce Harrington (bryce)]

Oh, you're on vmware. Nevermind.

[Bryce Harrington (bryce)]

Unfortunately there are no freeze analysis tools for vmware that I know of, so I can't advise on how to further debug this issue.

Since we're in the middle of development, there have been a few transitions outside of X which could have caused some disruption. E.g. kernel driver conflicts or some such. There's no error messages in any of your logs though, so impossible to say for sure.

Are you able to reproduce this bug?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.