Bug 27947

Created attachment 35388 [details]
Screenshot showing the Celestia main window appearing on top of a focused application

Created attachment 35389 [details]
Screenshot showing menu item drawn below main content window in Celestia

See bug 8732.

Thanks, Michel, this is a dupe. I was actually surprised that I did not find a previous report when I searched.

*** This bug has been marked as a duplicate of bug 8732 ***

I am sorry, this is actually not a dupe! (of bug 8732, at least)

This bug can be summarized as a request to enable DRI2 (and possibly uxa) in radeonhd. The user can apparently enable it manually.

Thanks.

(In reply to comment #5)
> I am sorry, this is actually not a dupe! (of bug 8732, at least)
> 
> This bug can be summarized as a request to enable DRI2 (and possibly uxa) in
> radeonhd. The user can apparently enable it manually.

radeonhd does not support dri2.  You'd have to add kms (kernel modesetting) support to radeonhd to support dri2 which is a fairly major amount of work.  If you want dri2 support, use radeon (xf86-video-ati).  Note that kms support requires a recent kernel that includes a kms enabled drm (2.6.33 or newer).

In fact, the driver being used is in fact radeon, not radeonhd. Changing Component.

$ lspci -v 
[snip]
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400
        Subsystem: Dell Device 2003
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        I/O ports at ee00 [size=256]
        Memory at efdf0000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at efd00000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel modules: radeon

$ cat /var/log/Xorg.0.log | grep LoadModule
(II) LoadModule: "extmod"
(II) LoadModule: "dbe"
(II) LoadModule: "glx"
(II) LoadModule: "record"
(II) LoadModule: "dri"
(II) LoadModule: "dri2"
(II) LoadModule: "ati"
(II) LoadModule: "radeon"
(II) LoadModule: "vesa"
(II) LoadModule: "fbdev"
(II) LoadModule: "fbdevhw"
(II) LoadModule: "vgahw"
(II) LoadModule: "int10"
(II) LoadModule: "ddc"
(II) LoadModule: "i2c"
(II) LoadModule: "fb"
(II) LoadModule: "ramdac"
(II) LoadModule: "exa"
(II) LoadModule: "evdev"
(II) LoadModule: "synaptics"

$ lsmod | grep radeon
radeon                636000  2 
ttm                    36212  1 radeon
drm                   160032  4 radeon,ttm
i2c_algo_bit            5760  1 radeon

> Note that kms support requires a recent kernel that
> includes a kms enabled drm (2.6.33 or newer)
>

I see, then the issue might be my kernel:
$ uname -r
2.6.31-20-generic

I will try to get a .33 kernel installed and see how that runs. Thanks.

I can confirm this problem. It happens when running the radeon X.org driver with UMS. Using KMS works fine. I have radeon HD 4350.
But it seems to be an architectural problem, as described also in the linked bug.

Are you not able to use radeon driver with KMS? Please comment if you already fixed it.

Dotan Cohen, Kubuntu 9.10 reached EOL on April 30, 2011. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.