Unity randomly freezes after 11.10 upgrade

Bug #929655 reported by Sonia Ouarti
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned
Oneiric
Won't Fix
Undecided
Unassigned

Bug Description

Unity has been randomly freezing since I upgraded to 11.10.

Going to tty1 and running:

$ sudo pkill -9 compiz

...beings the system back into action.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic i686
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu4
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,compiztoolbox,resize,unitymtgrabhandles,gnomecompat,snap,place,regex,mousepoll,vpswitch,move,session,wall,animation,fade,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Thu Feb 9 17:08:58 2012
DistUpgraded: Log time: 2012-02-02 13:59:22.906750
DistroCodename: oneiric
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
   Subsystem: Lenovo ThinkPad T60/R60 series [17aa:201a]
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: LENOVO 1707Y8F
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic root=UUID=e1159779-184a-4ec8-b6af-c6839bfe9554 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to oneiric on 2012-02-03 (6 days ago)
XorgConf:
 Section "Device"
     Identifier "Configured Device"
     Driver "intel"
     Option "Tiling" "false"
 EndSection
dmi.bios.date: 05/16/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7BETD0WW (2.11 )
dmi.board.name: 1707Y8F
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7BETD0WW(2.11):bd05/16/2007:svnLENOVO:pn1707Y8F:pvrThinkPadX60:rvnLENOVO:rn1707Y8F:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1707Y8F
dmi.product.version: ThinkPad X60
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

Revision history for this message
Sonia Ouarti (sonia-ouarti) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

There are errors about invalid framebuffers:

Xorg.0.log:
(EE) intel(0): Couldn't create pixmap for fbcon

dmesg:
[11678.477663] init: tty1 main process ended, respawning
[11680.331193] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

However these are not likely to be the cause of your issue.

Given that killing compiz restores the system to functionality, this tends to suggest a bug in compiz, unity, or one of the compiz plugins.

Reproduce the bug and capture your ~/.xsession-errors while the system is frozen, and attach that here. Hopefully the tail end of that will contain a pertinent error message.

You may also want to review what compiz plugins you have enabled or any compiz settings you may have made. Or, try logging into a guest session and see if the error reproduces there.

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

jpds posted me the pertinent bits from the .xsession-errors:

** (gnome-fallback-mount-helper:1522): DEBUG: ConsoleKit session is active 0
gnome-session[1430]: WARNING: Application 'compiz.desktop' killed by signal
gnome-session[1430]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[1430]: CRITICAL: We failed, but the fail whale is dead. Sorry....

So, compiz is definitely getting stuck in a loop. gnome-session notices it's failing and (I guess) restarts the session.

I'd follow the usual compiz troubleshooting steps from here. Enable debugging; test a guest session; run compiz through gdb; disable compiz plugins one by one, etc.

affects: xserver-xorg-video-intel (Ubuntu) → compiz (Ubuntu)
Revision history for this message
Jonathan Davies (jpds) wrote :

To make it clear, compiz appears to have hung; killing compiz caused it to restart without any loss of applications.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If compiz/unity is hanging then next time it happens, please switch to tty1 (Ctrl+Alt+F1) and run this:
  gdb /usr/bin/compiz `pidof compiz` | tee ~/gdblog.txt

Then in gdb, do this:
  thread 1
  bt

Now kill/restart compiz as before and attach the resulting file "gdblog.txt" (in your home directory) to this bug.

Thanks in advance.

Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jonathan Davies (jpds) wrote :

Please find attached the requested gdb log.

Changed in compiz (Ubuntu):
status: Incomplete → Confirmed
Jonathan Davies (jpds)
tags: added: rls-mgr-o-tracking
Revision history for this message
Rolf Leggewie (r0lf) wrote :

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".

Changed in compiz (Ubuntu Oneiric):
status: New → Won't Fix
Revision history for this message
dino99 (9d9) wrote :

That version has reached EOL since a while, so it will not receive update. If that issue still exist, report again using ubuntu-bug.

Changed in compiz (Ubuntu):
status: Confirmed → 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.