Xorg freeze

[yogeshkumar v kapadia]

cannot launch libreoffice 3, it hang computer

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,debugspew,decor,copytex,commands,neg,dbus,compiztoolbox,kdecompat,colorfilter,scale,inotify,expo,resize,resizeinfo,regex,place,titleinfo,gnomecompat,imgpng,opacify,mousepoll,ezoom,grid,workarounds,wall,move,obs,mag,scaleaddon,staticswitcher,kde,session,unityshell,unitymtgrabhandles]
CompositorRunning: compiz
Date: Tue May 17 10:08:26 2011
DistUpgraded: Log time: 2011-04-29 18:36:33.221857
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 8.840, 2.6.38-8-generic, i686: installed
 fglrx, 8.840, 2.6.38-9-generic, i686: installed
GraphicsCard:
 ATI Technologies Inc M93 [Mobility Radeon HD 4500 Series] [1002:9555] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Device [1682:2465]
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
JockeyStatus: xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 LANGUAGE=en_IN:en
 LANG=en_IN
 LC_MESSAGES=en_IN.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-9-generic root=UUID=c011064a-b081-4f14-a288-71e0cb343ec7 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to natty on 2011-04-29 (17 days ago)
dmi.bios.date: 01/08/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG41RQ
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE54511-203
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr:
drirc:
 <driconf>
 </driconf>
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.23-1ubuntu6
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+4ubuntu3
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.14.0-4ubuntu7.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[penalvch (penalvch)]

yogeshkumar v kapadia, thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[penalvch (penalvch)]

yogeshkumar v kapadia, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.