The function compositorCheckCMSelection() would use the atom index in
our table of atoms, instead of the actual atom, so this is unlikely to
work as expected.

Fix the code to use the appropriate atom as it should.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Prefer using memory allocation functions which initialize the memory
with 0's to be on the safe side.

No functional change.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

This is a development preview release.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

A pid is not necessarily a long on all systems, so casting the value of
NET_WM_PID directly into a GPid may cause a stack overflow.

Fixes: 49c1a33a
Closes: #411


Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Dridi Boukelmoune authored 5 years ago and Olivier Fourdan committed 4 years ago

If the user selected a primary monitor, the Alt+Tab window will only
appear on that monitor, otherwise on all of them.

To quote the GDK documentation for gdk_display_get_primary_monitor:

> [...], specialized desktop applications such as panels should place
> themselves on the primary monitor.

It is however not possible to use gdk_display_get_primary_monitor and
also respect the user's setting. Despite what the online documentation
says, recent versions of GTK+3 may no longer return a null value and
will instead pick one monitor as the primary if there isn't already one
defined. The nullable marker [1] for the return value was eventually
dropped.

In other words, whether the user selected a primary monitor or not
gdk_display_get_primary_monitor will always return one.

Signed-off-by: Dridi Boukelmoune <dridi@fedoraproject.org>

[1] https://gitlab.gnome.org/GNOME/gtk/commit/76d95c312dde

Dridi Boukelmoune authored 4 years ago and Olivier Fourdan committed 4 years ago

Signed-off-by: Dridi Boukelmoune <dridi@fedoraproject.org>

Dridi Boukelmoune authored 5 years ago and Olivier Fourdan committed 4 years ago

It's a shorthand for gdk_monitor_is_primary when working from a screen.

Signed-off-by: Dridi Boukelmoune <dridi@fedoraproject.org>

Add more XError traps related to XConfigureWindow requests.

#405


Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

To be on the safe side.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

The gvalues strings were considered statics, hence not duplicated.

As the caller frees the strings after setting the gvalue, the actual
content would end up pointing at free data.

Consider string gvalues as regular strings, meaning that the given
string value is duplicated as a gvalue.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>
Closes: #406

Commit 821ee7cc would not actually send the synthetic configure notify
events anymore. That obviously breaks plenty of applications…

While the logic of the commit itself is sound, the problem is that it
bases the descision to send the configure notify event by comparing
against the current window size and location.

The problem is that the current window size and location is modified in
various places, defeating the logic.

Add an “applied_geometry” rectangle that we update only in a single
place in the code, so that we know exactly when to send a synthetic
configure notify event.

Closes: #403


Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

The size and position of the client are stored at multiple occasions.

But the naming of the variables used is a bit confusing, rename the
variables and use GdkRectangles instead.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

171 translated messages, 2 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

xfwm4 would send a synthetic configure event while resizing the client
window, which is not what the ICCCM states.

Fix this by sending the synthetic configure event only when necessary,
as per the ICCCM specification.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Avoid setting the same flag twice in a row, we already set the
CFG_REQUEST just a few line above.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Some client do not process events on their temporary windows, causing
the client unresponsive dialog to show up.

Avoid pinging the client on focus in, even though this is clearly a
client bug.

This reverts commit 637d70b2.

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

170 translated messages, 3 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

164 translated messages, 9 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

124 translated messages, 49 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

170 translated messages, 3 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

171 translated messages, 2 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

96 translated messages, 77 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

93 translated messages, 80 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

To make sure that they are still alive and detect hung clients.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

When xfwm4 needs to kill an unresponsive client, it will use the its PID
is known.

However, the _NET_WM_PID as defined in the extended window manager hint
mechanism is unreliable when the client runs within a sandbox, as it is
the client itself who sets that property using its own view of the PID.

The Xserver can provide a more accurate value of the client PID using
the XRes X11 extension, so use that protocol if available.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

The X-Resource extension client library (XRes) allows a client to query
the Xserver for various resources associated with an X11 client,
including its PID.

Add (optional) support for XRes in xfwm4 and use it for getting the
client's PID instead of relying on _NET_WM_PID.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>