compiz crashes with external monitor

Bug #575283 reported by Robert A. Kocis
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

Compiz works with laptop internal monitor on Asus 1000HE, lucid lynx. When I try switching to an external monitor (LG W2252TQ), screens blink several times, then come back on with both operative and without visual effects. Right clicking desktop and trying to reset visual effects is ineffective, leading to an incoherent and unpredictable desktop. When I tried metacity, it appeared to work but without any visual effects or compositing. When I tried to return to compiz, I got this screen:

bob@RAK1000Asus:~$ metacity --replace &
[1] 2263
bob@RAK1000Asus:~$ compiz --replace &
[2] 2300
bob@RAK1000Asus:~$ WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!

Launching fallback window manager
^C
[1]- Done metacity --replace
bob@RAK1000Asus:~$ Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200084 (Linux Blog)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200084 (Ubuntu One)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
^C
bob@RAK1000Asus:~$ Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200084 (Report a b)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: compiz 1:0.8.4-0ubuntu15
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
CompizPlugins: [core,ccp,dbus,place,mousepoll,gnomecompat,move,resize,decoration,png,svg,imgjpeg,text,commands,neg,wall,snap,animation,scale,scaleaddon,expo,staticswitcher,regex,resizeinfo,workarounds,ezoom,vpswitch,fade,session]
Date: Tue May 4 13:19:12 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer INC. 1000HE
PackageArchitecture: all
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=aa97dfb3-b9da-47cb-8eda-d2492eb3a48b ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions:
 xserver-xorg 1:7.5+5ubuntu1
 libgl1-mesa-glx 7.7.1-1ubuntu2
 libdrm2 2.4.18-1ubuntu3
 xserver-xorg-video-intel 2:2.9.1-3ubuntu5
 xserver-xorg-video-ati 1:6.13.0-1ubuntu5
SourcePackage: compiz
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 10/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000HE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd10/14/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000HE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
system: distro = Ubuntu, architecture = i686, kernel = 2.6.32-21-generic

Revision history for this message
Robert A. Kocis (kocisr1) wrote :
Revision history for this message
Герман-Евтушенко Екатерина (assoly) wrote :

I have the same problem.
Some people tried to decided this https://answers.launchpad.net/ubuntu/+question/63042
But I can't.
When I started Firefox metacity crashed.
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x70000b4 (Mozilla Fi)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

Revision history for this message
Robert A. Kocis (kocisr1) wrote : Re: [Bug 575283] Re: compiz crashes with external monitor

Metacity has been a stable, reliable substitute for me so far, but I do
want the attractive display that Compiz makes possible. Interestingly,
Compiz is working on my Asus 700, which is so much more primitive than
the 1000. So I'm using it now and planning to wait for the bug fix.

On 05/04/2010 02:04 PM, Герман-Евтушенко Екатерина wrote:
> I have the same problem.
> Some people tried to decided this https://answers.launchpad.net/ubuntu/+question/63042
> But I can't.
> When I started Firefox metacity crashed.
> Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x70000b4 (Mozilla Fi)
> Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
>
>

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. 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.

Changed in compiz (Ubuntu):
importance: Undecided → Medium
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.