Bug 140276
Summary: | Windows unmoveable sometimes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Carlos Rodrigues <cefrodrigues> |
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | david.balazic |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-01 07:44:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Carlos Rodrigues
2004-11-21 23:50:46 UTC
I guess I'm able to reproduce it after all. But it isn't easy to explain in writing. This happens when I click on the titlebar and move the mouse at the same time. If I click and the drag (even if the time between the two events is really small) it works. Never seen or heard of this on FC3. There was an old bug like this around fc1/RHEL3-ish Can you give more details: - exact metacity and X versions - WM config options - X drivers - are you sure your hardware isn't confused somehow - anything else unusual about your setup - hardware, configuration, custom install choices, 3rd-parth software click and drag will look exactly the same as click-while-moving to metacity, so I don't think it can be that, though maybe click-while-moving triggers a race condition and click and drag has enough pause in there to avoid the race. This is FC3 with all updates, so it's metacity-2.8.6-2 and xorg-x11-6.8.1-12.FC3.1. The configurations are the defaults for metacity. I first noticed this the first time I logged in as root, just after first boot (before doing any updates). I was using the "nv" driver then. I'm using the binary "nvidia" drivers now. I still have FC2 installed on this box and it doesn't exibit this behaviour. Don't know if there is anything else worth mentioning. My system is an athlon 2400, asus a7v8x (via kt400 motherboard) with a GeForce 4 Ti 4200 AGP-8x. I've never experienced this before, not even on FC1. Hmmm, I guess this isn't really a metacity bug. The same thing happens in KDE. It could be the mouse hardware or mouse drivers (in kernel or X), perhaps. I have a Logitech Wheel Mouse Optical USB, but this also happens when it is connected via the PS/2 adapter. I've also tried with my sister's Microsoft Intellimouse USB and the results were the same. Since my FC2 installation is fully updated (the kernels are similar), my totally uneducated guess would be X. I had the Emulate3Buttons option set to "yes" in xorg.conf. Turning it off made things much better. However, it still seems to happen. I will need more time before knowing if its still here or it's just me trying too hard to break it. But this happening with the Emulate3Buttons option is still a bug. BTW, this very same thing happens on FC2 with Emulate3Buttons. Unfortunately I don't have a 2 button mouse here to try this out. Maybe most people doesn't and so nobody noticed this before... Are you using Emulate3Buttons with a 3 or more button mouse? Or is it a 2 button mouse? Its a 3 button mouse + wheel (USB). Could you try to disable 3 button emulation? Look for a line like this in /etc/X11/xorg.conf: Option "Emulate3Buttons" "yes" and remove it and restart your X server. The 3 button emulation introduces a small delay between the mouse click and delivering the event, which could be what you are seeing. Thanks I already did that. It works fine without "Emulate3Buttons". If this is normal behaviour with "Emulate3Buttons", I guess it can be closed. I'm not sure, but that option was probably enabled by some mistake of mine during the installation. Emulate3Buttons should not be enabled if you're using a real 3 or more button mouse. It appears that this is just a misconfigured X server, and not really a bug. Setting status to "NOTABUG". This "non-bug" is also reported on upstream : https://bugs.freedesktop.org/show_bug.cgi?id=1752 |