GNOME Bugzilla – Bug 122896
Click focused titlebar does nothing until you click again which then moves window
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: Click on the window decoration then drag window. Window may ocassionally ignore drag or more frequently move after a lag or jump to the cursor some time afterthe click and drag has been completed. Steps to reproduce the problem: 1. Click 2. drag window 3. Actual Results: slow and laggy Expected Results: snappy response How often does this happen? This is a bit hard to pin down. I can click and drag a window and have poor performance, do it again and have a snappy response, do it again and its poor again. I am thying this on a redhat beta - serven + rawhide but i get somewhat similar results with my desktop at work running rh9. all the drags i am talking about are with xterms btw Additional Information: I have dual screen at home (radeon laptop) and work (dual xeon + nvidia)
This problem is sort of a recurring thing; we don't really think that it's metacity's fault, necessarily. It may have something to do with redrawing the desktop, or poor video driver performance, or maybe something else. It would be nice to really figure out what's going on here; there's a fair bit of discussion on this other bug over here: *** This bug has been marked as a duplicate of 95273 ***
I seem to have lost a comment, bugger! This is not a drag issue, it is the dely between the click and the drag. I have further narrowed it down to ckicl on the title bar and drag on the window that has the focus is slow to respond. Unfocused windows can be clicked and dragged at will. the issue is not the slow drag, but of the window manager not responding to clicks and drags in the focused window
I saw this happen on Fedora Core Test 2, it is not just slow performance but rather an initial click not registering. If it isn't happening to anyone not using the Fedora test releases, I'm kind of tempted to blame X/kernel drivers.
It actualy registers the first click, as the window jumps to wherever you click next.
Created attachment 22282 [details] Additional Observations about this bug
bizarre.
No activity here -- I'm going to go ahead and blame a weird X issue in Fedora Core 2 unless someone complains. Fedora users let us know if you still see this issue.