[Ubuntu-x-swat] [Bug 429251] Re: [RV200] ATI graphics corruption with compiz on XAA

2010-04-12 Thread jtniehof
I agree with Gary13579 that "use EXA" is not a fit for "XAA doesn't work". Upstream has decided XAA is a WONTFIX (http://bugs.freedesktop.org/show_bug.cgi?id=22055), so I suggest someone from Bug Control mark this (and bug #426582) as WONTFIX as well. EXA performance problems should probably be an

Re: [Ubuntu-x-swat] [Bug 429251] Re: ATI graphics corruption with compiz on XAA

2010-03-24 Thread jtniehof
On Sun, Mar 7, 2010 at 12:19 PM, Randall Ross (rrnwexec) wrote: > Good news. Lucid Lynx Alpha 3 does not exhibit this behaviour on the Radeon > Mobility M6 LY > (Neither does Alpha1 or Alpha2). Randall, can you confirm that you have no corruption using XAA? (Check /var/log/Xorg.0.log for mention

[Ubuntu-x-swat] [Bug 426582] Re: (32MB) certain windows drawn garbled when XAA is used

2010-03-06 Thread jtniehof
Lucid alpha 2 and 3 display the notifcation windows fine on what lspci identifies as "Radeon Mobility M7 LW [Radeon Mobility 7500]" (ThinkPad T30). However, checking X.0.log shows that the X server is using EXA, not XAA. This may explain the slow performance some people are noting. I was unable to

[Ubuntu-x-swat] [Bug 429251] Re: ATI graphics corruption with compiz on XAA

2010-03-06 Thread jtniehof
Lucid alpha 2 and 3 do not show corruption on what lspci identifies as "Radeon Mobility M7 LW [Radeon Mobility 7500]" (ThinkPad T30). However, checking X.0.log shows that the X server is using EXA, not XAA. I was unable to force XAA using an xorg.conf. Bug #513956 suggests that XAA still exists, ho

[Ubuntu-x-swat] [Bug 426582] Re: (32MB) certain windows drawn garbled when XAA is used

2010-01-03 Thread jtniehof
I misspoke (too many windows open). Bug #416001 is related but not the same, unmarked. Bug #429251 is essentially the same but, as I mentioned, there's no clear distinguishing whether it or this should be marked dupe (and each links the other in comments) -- (32MB) certain windows drawn garbled w

[Ubuntu-x-swat] [Bug 416001] Re: Notification and similar dialogs are displaying corrupted after update on Karmic

2010-01-03 Thread jtniehof
** This bug is no longer a duplicate of bug 426582 (32MB) certain windows drawn garbled when XAA is used -- Notification and similar dialogs are displaying corrupted after update on Karmic https://bugs.launchpad.net/bugs/416001 You received this bug notification because you are a member of Ubu

[Ubuntu-x-swat] [Bug 426582] Re: (32MB) certain windows drawn garbled when XAA is used

2010-01-02 Thread jtniehof
This is still present in Lucid Alpha 1. Bug #416001 appears to be the same; unfortunately both it and this bug have significant activity so neither one is easily marked duplicate. See also bug #429251, which seems to be related. -- (32MB) certain windows drawn garbled when XAA is used https://bug

[Ubuntu-x-swat] [Bug 460055] Re: with visual effects disabled, notifications and system->admistration->system monitor cannot be seen

2010-01-02 Thread jtniehof
*** This bug is a duplicate of bug 426582 *** https://bugs.launchpad.net/bugs/426582 This appears to be a duplicate of bug #426582, so I am marking it as such. There are some workarounds in that bug discussion which may help. ** This bug has been marked a duplicate of bug 426582 (32MB) cer

[Ubuntu-x-swat] [Bug 429251] Re: ATI graphics corruption with compiz on XAA

2010-01-02 Thread jtniehof
Still exists in Lucid alpha 1. For those who haven't seen it yet, bug #426582 is also related. -- ATI graphics corruption with compiz on XAA https://bugs.launchpad.net/bugs/429251 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-dri

[Ubuntu-x-swat] [Bug 441814] Re: Karmic Beta: Visual Effects not usable

2010-01-02 Thread jtniehof
*** This bug is a duplicate of bug 429251 *** https://bugs.launchpad.net/bugs/429251 This appears to be essentially the same as bug #429251 although the hardware is not identical. Marking it as such to try and keep all this in one place. ** This bug has been marked a duplicate of bug 429251

[Ubuntu-x-swat] [Bug 478685] Re: [M6] broken compiz / graphics stack / ati drivers (128MB)

2010-01-02 Thread jtniehof
*** This bug is a duplicate of bug 429251 *** https://bugs.launchpad.net/bugs/429251 Although the hardware is not identical, this looks to me like a duplicate of bug #429251 (see also bug #426582). ** This bug has been marked a duplicate of bug 429251 ATI graphics corruption with compiz on

[Ubuntu-x-swat] [Bug 474264] Re: Compositing in karmic fails with Ati Mobility M6 16 MB on Dell C610

2010-01-02 Thread jtniehof
*** This bug is a duplicate of bug 429251 *** https://bugs.launchpad.net/bugs/429251 ** This bug has been marked a duplicate of bug 429251 ATI graphics corruption with compiz on XAA -- Compositing in karmic fails with Ati Mobility M6 16 MB on Dell C610 https://bugs.launchpad.net/bugs/474

[Ubuntu-x-swat] [Bug 382301] Re: capslock additional control

2009-12-14 Thread jtniehof
*** This bug is a duplicate of bug 488532 *** https://bugs.launchpad.net/bugs/488532 ** This bug has been marked a duplicate of bug 488532 "Make CapsLock an additional Ctrl" should be under "CapsLock key behavior," not "Ctrl key position." -- capslock additional control https://bugs.laun

[Ubuntu-x-swat] [Bug 488532] Re: "Make CapsLock an additional Ctrl" should be under "CapsLock key behavior, " not "Ctrl key position."

2009-12-14 Thread jtniehof
Thanks Thomas; I should have caught that. Since this is triaged I'm marking bug 382301 as the duplicate, even though it came earlier (per https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate) -- "Make CapsLock an additional Ctrl" should be under "CapsLock key behavior," not "Ctrl key pos

[Ubuntu-x-swat] [Bug 488532] Re: "Make CapsLock an additional Ctrl" should be under "CapsLock key behavior, " not "Ctrl key position."

2009-11-27 Thread jtniehof
Per comments on Gnome bug 602991. ** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config (Ubuntu) -- "Make CapsLock an additional Ctrl" should be under "CapsLock key behavior," not "Ctrl key position." https://bugs.launchpad.net/bugs/488532 You received this bug notification beca