http://bugs.winehq.org/show_bug.cgi?id=58505 --- Comment #8 from Rémi Bernon <rbernon@codeweavers.com> --- Created attachment 79917 --> http://bugs.winehq.org/attachment.cgi?id=79917 Possible workaround Yes, I've been trying with GNOME and KDE and both seem to work fine to me. From the log it looks like that the WM doesn't offer focus to the window (which doesn't have any _NET_WM_USER_TIME set) after it's requested to be shown. This could be a bogus implementation of _NET_WM_USER_TIME by the WM as, from the it should only do that if _NET_WM_USER_TIME is set to 0, not when it's missing. EWMH specification (https://specifications.freedesktop.org/wm/latest/ar01s05.html#id-1.6.16) says: Clients can obtain the timestamp that caused its first window to appear from the DESKTOP_STARTUP_ID environment variable, if the app was launched with startup notification. If the client does not know the timestamp of the user interaction that caused the first window to appear (e.g. because it was not launched with startup notification), then it should not set the property for that window. The special value of zero on a newly mapped window can be used to request that the window not be initially focused when it is mapped. At least to confirm this, does the attached patch help? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.