FS#3623 - KDE 3.5 delays screen when drawing/undrawing new windows

Attached to Project: Arch Linux
Opened by Mick (amdviaman) - Thursday, 15 December 2005, 06:16 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to KDE 3.5, I've noticed screen delays lasting up to 3 seconds which only occur when drawing/undrawing windows. During these delays the screen is completely frozen (including the mouse cursor.) Occasionally, a window will be partially drawn/undrawn before the delay occurs. About one in every 3-4 windows drawn/undrawn is affected. I have tested this with vesa, nv and nvidia X drivers and all experience the same delays so this is not hardware related. The bug does not seem to affect any other part of the system and is easilly reproducable. I am not able to test other distros for similar defects, so it is unclear whether or not this is an upstream problem.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 16 December 2005, 15:22 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Thursday, 15 December 2005, 08:14 GMT
i don't understand the problem what are you doing?
just minimize window and then maximize it again?
Comment by Mick (amdviaman) - Thursday, 15 December 2005, 11:16 GMT
Whenever a new window is opened, maximized, or closed, the screen will freeze for about 3 seconds, including the mouse cursor, then functionality returns
Comment by Tobias Powalowski (tpowa) - Thursday, 15 December 2005, 17:31 GMT
Please disable REnderAccel it sounds much like a problem there. /etc/X11/xorg.conf
Option "RenderAccel" "false"
Comment by Mick (amdviaman) - Thursday, 15 December 2005, 20:54 GMT
Set RenderAccel to false, the problem persists. I just tested for this problem on another machine with a clean arch install and it does the same thing. I tried fluxbox and it is not affected, I would've tried gnome, but gnome dosen't work at all for some reason .......... The problem might be in the kde/qt libraries. I also tried a distro called arklinux to see if it's a direct kde 3.5 problem, it appears unaffected. I'm going to try compiling kde from source, if I succeed in compiling it I will post the results.
Comment by Mick (amdviaman) - Thursday, 15 December 2005, 20:56 GMT
In the mean time, if there's anything you'd like me to do to possibly obtain more technical information, I am willing to do so.
Comment by Tobias Powalowski (tpowa) - Thursday, 15 December 2005, 21:21 GMT
ok now you said that gnome shows the same effect, i bet it's a network problem, check your network settings and that your loopback device is setup correct, that you have a localhost in /etc/hosts and a entry for your network card.
when kde/qt and gnome show same behaviour it' s pretty obvious a network problem.
flux box and other DE's don'T have as much stuff as the big players, so they might be not affected.
Comment by Jan de Groot (JGC) - Thursday, 15 December 2005, 22:24 GMT
On the mailinglist I've read something about ipv6. Arch comes with a stock kernel that has ipv6 enabled as module. Whenever you request ipv6'ish stuff, ipv6-capable programs will try to use it. Guess what? We don't have the ipv6 notation for localhost notated in /etc/hosts, so every ipv6 query for localhost will go to your DNS server, resulting in huge slowdowns (some of them may return a record, most of them will either timeout or give a SERVFAIL)

Edit:
put this in /etc/hosts:
::1 localhost
Comment by Mick (amdviaman) - Friday, 16 December 2005, 01:12 GMT
maybe a network problem, but what I meant was gnome dosen't load at all, just sits at a black screen with no related X shell output (sorry for my bad wording.)
Comment by Mick (amdviaman) - Friday, 16 December 2005, 11:00 GMT
Ok, just finished compiling. The compiled version does not seem to be experiencing any of the problems i've reported, except for kicker crashing on exit (which also happens in the packaged version), but that's a job for the kde people. Something must be wrong in the binary package(s) i'm guessing.
Comment by Tobias Powalowski (tpowa) - Friday, 16 December 2005, 14:07 GMT
short question, what did you recompile?
thanks

EDIT:
do you have some extra kde stuff installed, that is not part of the standard kde packages?
Comment by Mick (amdviaman) - Friday, 16 December 2005, 14:57 GMT
"short question, what did you recompile?"
I recompiled the entire kde package with konstruct http://developer.kde.org/build/konstruct/

"do you have some extra kde stuff installed, that is not part of the standard kde packages?"
nope, just issued pacman -S kde.

btw, I just refreshed my package database and upgraded kdelibs-3.5-3 to kdelibs-3.5-4, same for kdepim-3.5-3 and I no longer have the problem, except for kicker crashing on exit, which i'm filing with the kde devs later.

Loading...