When dragging icons around in KDE (tested with 3.4 and CVS builds), the server locks. The cursor can still move around but the rest of X is frozen. The only way to fix it after this is to ssh in and kill X. Running gdb and grabbing a backtrace when the system locks up produces the following: 0x10162774 in miPolyBuildPoly () (gdb) bt #0 0x10162774 in miPolyBuildPoly () #1 0x10165e64 in miWideDash () #2 0x10160a84 in miPolyRectangle () #3 0x10140a68 in damagePolyRectangle () #4 0x100862ac in ProcPolyRectangle () #5 0x1008aa80 in Dispatch () #6 0x10099fe4 in main () Disabling acceleration fully and DRI doesn't seem to stop the lockups. I've tried this with both the fbdev and radeon drivers, both producing the same results. This is on a PowerBook G4 with a Radeon 9600 Mobility (M10) graphics card and Gentoo Linux.
what happens if you disable the Damage extension? Section "Extensions" Option "DAMAGE" "disable" EndSection
Still locks up when dragging stuff around.
hm, so that looks like an infinite loop in miPolyBuildPoly then. when you say dragging around icons, that means konqueror icons, right? whatever process it is, it would help to see what the last request it sent to the server was.
george, as i'm unable to reproduce this here, you will need to supply more information if you want this fixed in 7.0.
irreproducible and no further info from reporter -> move out to 7.1. george, this is probably just a loop caused by precision problems somewhere along the line. please try building a debuggable X server and find out what line(s) this is stalling on.
(In reply to comment #5) > irreproducible and no further info from reporter -> move out to 7.1. > > george, this is probably just a loop caused by precision problems somewhere > along the line. please try building a debuggable X server and find out what > line(s) this is stalling on. Moving out to 7.2. Reporter, ping ping ping, either verify this is still an issue or risk a WORKSFORME.
Erk, just noticed this thread again in my email; the bug was resolved a while ago and I neglected to close this bug. Apologies.
Closing as submitter doesn't experience this issue any more.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.