GNOME Bugzilla – Bug 624563
Got a request to focus 0x240decc (dg@major: ) with a timestamp of 0. This shouldn't happen
Last modified: 2020-11-06 20:09:37 UTC
This started out as Ubuntu bug 605829: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/605829 In the latest Ubuntu Maverick testing a few of us are getting logs full of errors similar to: Window manager warning: Got a request to focus 0x240decc (dg@major: ) with a timestamp of 0. This shouldn't happen! It doesn't look like it's just the terminal; I've seen it from a few apps. The related symptom is the mouse cursor flicking very quickly. It's not clear to me if this is metacity but the 'This shouldn't happen' seems to be an indication metacity isn't expecting it to happen. I've also tried it with an apparently unpatched 2.30.1 (I built from source) and am getting the same errors, so I don't think it's Ubuntu's tweaks to Metacity itself. Dave
I think this happens when unclutter is running; as soon as you kill unclutter the behaviour stops. I'm not sure if this means it's a bug in metacity or unclutter, but I suspect the latter.
I don't see an input focus in unclutter but it does send an EnterNotify with timestamp of 0, and in some cases (probably if you're using mouse focus?) metacity would use that timestamp to move the focus. See http://unclutter.cvs.sourceforge.net/viewvc/unclutter/unclutter/unclutter.c?view=markup It looks like unclutter has a real EnterNotify already right there that it could use the time from, instead of CurrentTime. Also, metacity might want to ignore EnterNotify if send_event=True unclutter has a command line option "-noevents" that looks like it would avoid sending the bogus EnterNotify... if that command line option fixes this then the theory may be correct. I guess if using mouse focus, apps would then lose focus on uncluttering, but that's probably correct anyhow.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.