F12 KDE - slow response when clicking task bar items

[Craig White]

On Sat, 2009-11-28 at 04:43 -0600, Steven P. Ulrick wrote:
> Hello Everyone,
> 
> > On November 26, 2009, Craig White wrote:
> > > Since I upgraded to F12, I have noticed that it is very slow to respond
> > > to clicks in the task bar - i.e., a long delay if I click the 'fedora'
> > > start button or any of the applications in the 'Task Switcher' widget.
> > > 
> > > Discernibly slower than F11
> > > 
> > > FWIW, I am booting with nomodesetting option and using 'nv' driver with
> > > an xorg.conf setting (the same as I was using in F11) because I simply
> > > cannot get 1280x1024 with the nouveau driver, even with 'nomodesetting'
> > > boot option.
> > > 
> > > Anyone else notice this? Is there something I am doing wrong?
> > 
> > I've noticed exactly the same behaviour, and its driving me nuts... clicking 
> > on the "Start" Menu takes ~10-15s to pop up, but starting apps on my panel by 
> > clicking on the icon works nice and fast.  KRunner also takes ~10-15s to 
> > appear if I hit ALT-F2, and more often than not bringing up the desktop 
> > context menu is fast but it then stalls when trying to  disappear again.
> 
> First off, this bug specifically refers to the use of the binary NVidia driver, 
> which I know at least one of the posters on this thread says that they are not 
> using.  But, the manifestations described are just like what you all are 
> describing, and they are exactly what I WAS experiencing with Fedora 12:
> https://bugzilla.redhat.com/show_bug.cgi?id=533620
> 
> Also, check this out:
> https://fedoraproject.org/wiki/Common_F12_bugs#Problems_when_using_KDE_with_the_proprietary_NVIDIA_graphics_driver.2C_some_Radeon_dual-
> head_configurations.2C_or_nouveau_with_KMS_disabled
> 
> In addition, I needed to follow the steps that appear under the "Fedora 12 
> Special Notes" section on the below linked page:
> http://www.mjmwired.net/resources/mjm-fedora-nvidia.html
> 
> Applying the information contained in the above links fixed my problem, which at 
> least LOOKS exactly like what you are describing.
> 
> If you have any questions about the "various" test builds of xorg that are 
> involved in making all of this possible, I will get back to you after I get home 
> from work today...
----
I am using the free 'nv' driver as even with nomodesetting boot option,
I could not get 1280x1024 out of 'nouveau' - only a max of 1024x768
which just simply isn't enough.

I have changed my boot parameters so the next boot will be
nouveau.modeset=0 (I gather this to mean it will allow modesetting on
'nv' but not nouvea which if permitted, prevents me from using 'nv') and
I will see what happens but I have a lot of things going on that I don't
want to lose track of if I reboot now.

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.