compiz crashes when I try to run it in natty

Bug #745821 reported by Observer
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ibus

When I boot into Natty with Ubuntu Classic desktop, compiz windows decorator is either not loaded or has crashed quietly. No windows decorator is available.

Running "metacity --replace" restores the windows decoration and allows me to use the system.

When I try to run compiz with "compiz --replace &", the whole system get corrupted visually even though the system is still functioning and responding. The extent of functionality cannot be determined as the display is all messed up.

By killing compiz from another tty, the session was restored with the following error:

r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!

Revision history for this message
Observer (dbvweb) wrote :

$ glxinfo | grep Open
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RC410
OpenGL version string: 2.1 Mesa 7.10.1
OpenGL shading language version string: 1.20
OpenGL extensions:

Revision history for this message
Observer (dbvweb) wrote :

When I switch to a lower display res for both my notebook (1024x768) and lcd monitor (1024x768), compiz runs without error.

Increasing the resolution gradually, I managed to reproduce the display corruption which was automatically resolved when the display res change confirmation dialog time out.

Below is the error output when I increase the resolution to 1440 x 900 (ext LCD monitor) and 1280 x 1024 (notebook):

$ r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
compiz (core) - Warn: Couldn't bind background pixmap 0x2600001 to texture
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
compiz (core) - Warn: Couldn't bind background pixmap 0x2600001 to texture
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
compiz (core) - Warn: Couldn't bind background pixmap 0x2600001 to texture
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!

Revision history for this message
Observer (dbvweb) wrote :

$ dmesg | grep drm
[ 30.930770] [drm] Initialized drm 1.1.0 20060810
[ 31.409572] [drm] radeon defaulting to kernel modesetting.
[ 31.409578] [drm] radeon kernel modesetting enabled.
[ 31.415104] [drm] initializing kernel modesetting (RS400 0x1002:0x5A62).
[ 31.415149] [drm] register mmio base: 0xC0000000
[ 31.415151] [drm] register mmio size: 65536
[ 31.415342] [drm] Generation 2 PCI interface, using max accessible memory
[ 31.415372] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 31.415374] [drm] Driver supports precise vblank timestamp query.
[ 31.415387] [drm] radeon: irq initialized.
[ 31.415681] [drm] Detected VRAM RAM=128M, BAR=256M
[ 31.415685] [drm] RAM width 128bits DDR
[ 31.424607] [drm] radeon: 128M of VRAM memory ready
[ 31.424610] [drm] radeon: 512M of GTT memory ready.
[ 31.424638] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 31.456089] [drm] radeon: 3 quad pipes, 1 z pipes initialized.
[ 31.492259] [drm] Loading R300 Microcode
[ 31.537152] [drm] radeon: ring at 0x0000000080001000
[ 31.537176] [drm] ring test succeeded in 2 usecs
[ 31.537327] [drm] radeon: ib pool ready.
[ 31.537400] [drm] ib test succeeded in 0 usecs
[ 31.542558] [drm] Panel ID String: QDS
[ 31.542563] [drm] Panel Size 1280x800
[ 31.543782] [drm] Radeon Display Connectors
[ 31.543786] [drm] Connector 0:
[ 31.543789] [drm] VGA
[ 31.543792] [drm] DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68
[ 31.543794] [drm] Encoders:
[ 31.543796] [drm] CRT1: INTERNAL_DAC2
[ 31.543798] [drm] Connector 1:
[ 31.543799] [drm] LVDS
[ 31.543802] [drm] DDC: 0x198 0x198 0x19c 0x19c 0x1a0 0x1a0 0x1a4 0x1a4
[ 31.543805] [drm] Encoders:
[ 31.543806] [drm] LCD1: INTERNAL_LVDS
[ 32.020859] [drm] fb mappable at 0xD0040000
[ 32.020863] [drm] vram apper at 0xD0000000
[ 32.020865] [drm] size 5185536
[ 32.020867] [drm] fb depth is 24
[ 32.020869] [drm] pitch is 5760
[ 32.132044] fb0: radeondrmfb frame buffer device
[ 32.132046] drm: registered panic notifier
[ 32.132060] [drm] Initialized radeon 2.8.0 20080528 for 0000:01:05.0 on minor 0

Revision history for this message
Omer Akram (om26er) wrote :

you have already reported a similar, marking as duplicate.

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.