Comment 35 for bug 149764

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote : Re: [Bug 149764] Re: [nvidia] slow gtk popup menus with gtk dual head

Let me know if I can haul out your trash or stash your mail...

larry.j

On Thu, Jul 31, 2008 at 1:17 AM, Timo Aaltonen <email address hidden>wrote:

> ** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
> Sourcepackagename: linux-restricted-modules-2.6.24 =>
> nvidia-graphics-drivers-173
>
> --
> [nvidia] slow gtk popup menus with gtk dual head
> https://bugs.launchpad.net/bugs/149764
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "compiz" source package in Ubuntu: Invalid
> Status in "nvidia-graphics-drivers-173" source package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: compiz
>
> When using compiz on dual head systems context/popup menus and maximising
> are delayed on the first screen by approximately 3 seconds.
>
> This seems to be a common problem :
> http://ubuntuforums.org/showthread.php?t=536045&highlight=compiz+slow+menus&page=2
> but I couldn't find it listed as a bug.
>
> I can confirm it isn't effected by changing the fade-menus delay in compiz
> (or even turning it off entirely,) and it's not altered by changing the
> gnome menu delay in gconf. It does not seem to be any thing to do with CPU
> usage / video memory as both stay quiet during the delay.
>
> It also only happens with GTK applications, KDE apps like amarok run
> without any delay on both heads.
>
> This used to happen with Beryl when you loaded it on a dual head setup
> using --no-context-share, and was solved by running two instances on beryl
> for each screen. However compiz appears to no longer has this option, nor
> does it seems to respect the -display :0 / -display :1 options.
>
> Thanks, and apologies if I have duplicated a bug.
>
> -
> My setup:
>
> Gutsy beta, last updated 6th October, bug still present.
> (Compiz 0.6.1)
> Using two nvidia cards with nvidia driver. (although from forum posts, this
> doesn't seem to be exclusively affect nvidia users.)
>
> -
>