metacity issueshttps://gitlab.gnome.org/GNOME/metacity/-/issues2019-10-17T15:09:25Zhttps://gitlab.gnome.org/GNOME/metacity/-/issues/1Should present at-spi elements for the decorations2019-10-17T15:09:25ZSamuel ThibaultShould present at-spi elements for the decorationsHello,
While using a screen reader such as Orca in mouse review mode ("Speak object under mouse" option in its general preference panel), it would be useful to have it able to read the window decorations rendered by metacity. Basically,...Hello,
While using a screen reader such as Orca in mouse review mode ("Speak object under mouse" option in its general preference panel), it would be useful to have it able to read the window decorations rendered by metacity. Basically, it means metacity exposing to at-spi some Accessible objects corresponding to the different decoration elements (notably the title bar and the buttons), so that Orca can know where they are and their content.
Samuelhttps://gitlab.gnome.org/GNOME/metacity/-/issues/2Blurry titlebar font when window is not maximized2019-11-27T01:45:38ZGhost UserBlurry titlebar font when window is not maximizedMetacity window manager and Compiz window manager using gtk-window-decorator render slightly blurry titlebar fonts for windows that are not maximized. The fonts appear to lack sub-pixel hinting and/or anti-aliasing. Maximized windows ren...Metacity window manager and Compiz window manager using gtk-window-decorator render slightly blurry titlebar fonts for windows that are not maximized. The fonts appear to lack sub-pixel hinting and/or anti-aliasing. Maximized windows render sharp fonts.
The clip_to_rounded_corners() function in libmetacity is called to draw rounded corners for the un-maximized windows in my theme. It seems the call to draw rounded corners by cairo_arc() in that function somehow affects the font rendering. When windows are maximized, the drawing of rounded corners is not performed, hence the sharp font rendering.
More info about this issue is reported at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1780468https://gitlab.gnome.org/GNOME/metacity/-/issues/3Removed Crux theme2018-09-19T11:17:18ZStefan PöschelRemoved Crux themeAfter updating from Ubuntu MATE 16.04 LTS to 18.04 LTS I noticed that it is no longer possible to select the Crux theme for window decoration. It turns out that 16.04 used an older Metacity version (i.e. the then `metacity-common` packag...After updating from Ubuntu MATE 16.04 LTS to 18.04 LTS I noticed that it is no longer possible to select the Crux theme for window decoration. It turns out that 16.04 used an older Metacity version (i.e. the then `metacity-common` package, today `metacity-themes` package) that yet contained that theme. It seemed to have been removed in bbaf18a74a1877108b2033630a0eaf154c6af238.
When I copy the relevant folder (`/usr/share/themes/Crux/metacity-1`) from 16.04 to 18.04, I can again use the theme without issues. As far as I understand, the removal was not due to technical incompatibilites, but due to missing maintenance (commit message text). Is it possible to somehow engage in order to get this theme again into Metacity?https://gitlab.gnome.org/GNOME/metacity/-/issues/4Premature deiconify of Sugar Journal window2018-11-29T13:59:18ZGhost UserPremature deiconify of Sugar Journal windowA session manager application launches and iconifies a fullscreen window but the window is prematurely deiconified by Metacity, obscuring the fullscreen main window.
Metacity is run by the application with `--no-force-fullscreen` and `-...A session manager application launches and iconifies a fullscreen window but the window is prematurely deiconified by Metacity, obscuring the fullscreen main window.
Metacity is run by the application with `--no-force-fullscreen` and `--no-composite` options.
Bisection showed the problem began after 6875256 ("unminimize windows with initial IconicState if first known on MapRequest").
We have a [workaround](https://github.com/sugarlabs/sugar/pull/810/commits/9e7a93afba13470464700673dec6a3f9750cfd34) which detects the premature deiconify and calls `Gtk.Window.iconify()` once again. This works, but adds animation effects.
What further information do you need? Thanks.
References:
* https://github.com/sugarlabs/sugar/issues/769
* https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/368
* https://bugzilla.redhat.com/show_bug.cgi?id=1519042https://gitlab.gnome.org/GNOME/metacity/-/issues/5Metacity's context menu for CSD's titlebars2019-08-14T13:05:54ZTomasz GąsiorMetacity's context menu for CSD's titlebarsMetacity should show its own context menu when user clicks on GTK's client-side titlebar. Currently Metacity does not support it, so GTK fallbacks to its own simple menu. It's inconsistent especially with GNOME applications.
Please look...Metacity should show its own context menu when user clicks on GTK's client-side titlebar. Currently Metacity does not support it, so GTK fallbacks to its own simple menu. It's inconsistent especially with GNOME applications.
Please look at this to see how it's implemented in Marco, Metacity's fork: https://github.com/mate-desktop/marco/pull/370/commitshttps://gitlab.gnome.org/GNOME/metacity/-/issues/6Shortcuts does not work in 3.322019-05-06T09:25:28ZTomasz GąsiorShortcuts does not work in 3.32Arch Linux, gnome-flashback 3.30.0-1, metacity 3.30.1-2
All shortcuts except windows-related does not work in GNOME Flashback 3.32. Maybe related to this: https://gitlab.gnome.org/GNOME/gnome-shell/issues/988#note_444528Arch Linux, gnome-flashback 3.30.0-1, metacity 3.30.1-2
All shortcuts except windows-related does not work in GNOME Flashback 3.32. Maybe related to this: https://gitlab.gnome.org/GNOME/gnome-shell/issues/988#note_444528https://gitlab.gnome.org/GNOME/metacity/-/issues/7Metacity memory leak2019-09-13T13:27:12ZGhost UserMetacity memory leakI'm seeing a very large memory leak from Metacity. I'm running Mint 19.1 and Metacity. In one instance Metacity is using 997MB however, if I temporarily switch to Marco and then switch back, Metacity uses just 35.9MB -- evidence of a lea...I'm seeing a very large memory leak from Metacity. I'm running Mint 19.1 and Metacity. In one instance Metacity is using 997MB however, if I temporarily switch to Marco and then switch back, Metacity uses just 35.9MB -- evidence of a leak.
My on-line searches reveal that this leak has been reported many years ago but evidently remains. I do run an application that renders extensively to an X11 window is that the cause? Apart for restarting Metacity periodically. Is there a fix?
This is what TOP looks like for my OpenGL graphics intensive program. Xorg is at 90% of CPU use but Metacity has 11%. My own application (Electric) just 8.6%.
```
Tasks: 247 total, 2 running, 166 sleeping, 0 stopped, 1 zombie
%Cpu(s): 11.7 us, 6.9 sy, 0.0 ni, 81.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 16371884 total, 2977660 free, 3293108 used, 10101116 buff/cache
KiB Swap: 2097148 total, 2097148 free, 0 used. 12710320 avail Mem
```
```
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1020 root 20 0 428788 138832 61988 R 90.0 0.8 261:44.07 Xorg
1940 clive 20 0 509064 46616 34912 S 13.6 0.3 93:13.28 mate-system-mon
26303 clive 20 0 1055736 600152 25360 S 11.0 3.7 1:10.03 metacity
1653 clive 20 0 730712 219572 24788 S 10.0 1.3 28:57.65 wnck-applet
26383 clive 20 0 1335588 1.057g 30600 S 8.6 6.8 1:08.08 Electric
24328 clive 20 0 467604 31260 22676 S 5.0 0.2 1:35.75 gtk-window-deco
24881 clive 20 0 603136 38396 26436 S 4.3 0.2 0:33.84 mate-terminal
1610 clive 20 0 1256736 35496 26504 S 3.0 0.2 9:59.66 mate-settings-d
2109 clive 20 0 2490708 211236 85588 S 2.0 1.3 29:58.99 codelite
25114 clive 20 0 44424 4264 3288 R 0.3 0.0 0:03.03 top
1 root 20 0 225632 9452 6772 S 0.0 0.1 0:01.34 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
7 root 20 0 0 0 0 S 0.0 0.0 0:00.13 ksoftirqd/0
8 root 20 0 0 0 0 I 0.0 0.0 0:07.44 rcu_sched
9 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_bh
10 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/0
```https://gitlab.gnome.org/GNOME/metacity/-/issues/8Alt-tab misbehaves with fullscreen windows2020-03-06T17:06:29ZOri AvtalionAlt-tab misbehaves with fullscreen windowsTested with 3.34.1, and has always exhibited this behavior, as far as I can remember.
If I wish to alt-tab away from a full-screen program into a non-fullscreen window, the fullscreen window stays on screen (even though the focus is on ...Tested with 3.34.1, and has always exhibited this behavior, as far as I can remember.
If I wish to alt-tab away from a full-screen program into a non-fullscreen window, the fullscreen window stays on screen (even though the focus is on the non-fullscreen window). To properly see the non-fullscreen window, I need to alt-tab again to it.
The reverse is also an issue. If I wish to focus on the fullscreen window, alt-tabbing to it will show it, but will also show the gnome panels (the fullscreen window has focus). To make the panels disappear, I need to alt-tab again to the fullscreen window.
Sometimes when I launch fullscreen programs, they start with the gnome panel still visible.
To see an example of the first two issues, here's a [free game to test this with](https://ianmaclarty.itch.io/pointy-end). In the dialog that pops up, make sure you choose to start it in fullscreen (the default) and not windowed.
For comparison, I tested this with Gnome Classic and got a different behavior:
1. Alt-tabbing from and to fullscreen window works the first time - this is good!
2. Alt-tabbing away from fullscreen window shows the non-fullscreen window, but doesn't show the desktop panels - this is undesired.https://gitlab.gnome.org/GNOME/metacity/-/issues/9Flatpak apps running as root2020-05-01T14:54:25ZArtem PolishchukFlatpak apps running as rootHello everyone. Not sure is there a proper place for reporting this but this happens only in GNOME Flashback session with Metacity. Flatpak apps running as root in title bar. Weird thing that this happens with 50% chance.
**How to repro...Hello everyone. Not sure is there a proper place for reporting this but this happens only in GNOME Flashback session with Metacity. Flatpak apps running as root in title bar. Weird thing that this happens with 50% chance.
**How to reproduce:**
Run any flatpak app. Run twice or more if this not happened from first time.
**Actual results:**
See screenshot (1).
**Expected results:**
Title without "as administrator" title, as in GNOME session.
**Additional info:**
- OS: `Fedora 32`
- gnome-flashback: `3.36.1`
- metacity: `3.36.1`
- flatpak: `1.6.3`
---
(1): ![DeepinScreenshot_select-area_20200412094604](/uploads/926f1204e9bb99a7f2fa6faacd4baeb3/DeepinScreenshot_select-area_20200412094604.png)https://gitlab.gnome.org/GNOME/metacity/-/issues/10VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE has been removed from vulkan-headers-1.2.1402020-06-06T12:42:36ZRasmus Thomsenoss@cogitri.devVK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE has been removed from vulkan-headers-1.2.140Hello,
with vulkan-headers-1.2.140 the build breaks because `VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE` has been removed in that version. We've reverted back to 1.2.139 on Alpine Linux in the meantime since vulkan-headers upstream says that's ...Hello,
with vulkan-headers-1.2.140 the build breaks because `VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE` has been removed in that version. We've reverted back to 1.2.139 on Alpine Linux in the meantime since vulkan-headers upstream says that's by design[0], but I think the check for `VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE` can be removed from metacity's code anyway? The following shouldn't make a difference since it it'll end up in the `default` anyway, no?
```diff
diff --git a/src/compositor/meta-compositor-vulkan.c b/src/compositor/meta-compositor-vulkan.c
index b87b5194..b2c59419 100644
--- a/src/compositor/meta-compositor-vulkan.c
+++ b/src/compositor/meta-compositor-vulkan.c
@@ -810,7 +810,6 @@ device_type_to_string (VkPhysicalDeviceType type)
return "cpu";
break;
- case VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE:
case VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM:
default:
break;
```
0: https://github.com/KhronosGroup/Vulkan-Headers/issues/117https://gitlab.gnome.org/GNOME/metacity/-/issues/11SDL2 fullscreen apps w/ window decorations fight for mode change2023-03-09T21:00:31ZOXullo IntersecansSDL2 fullscreen apps w/ window decorations fight for mode changeGreetings,
when an SDL2 application with flags = SDL_WINDOW_FULLSCREEN (and in particular when the requested resolution != desktop resolution) is started, the desktop flickers.
Depending on how fast the application is able to react to e...Greetings,
when an SDL2 application with flags = SDL_WINDOW_FULLSCREEN (and in particular when the requested resolution != desktop resolution) is started, the desktop flickers.
Depending on how fast the application is able to react to events, two outcomes can follow:
1. the application and desktop keep changing video mode rapidly, back and forth. This situation can be recovered only by killing the application
1. the application flickers a random number of times until it settles
To be noted that the default initialization for the window in SDL2 sets it up decorated. By passing SDL_WINDOW_BORDERLESS to SDL_CreateWindow's flags, the issue doesn't reproduce. Eg:
```
SDL_CreateWindow("SDLTest", 0, 0, WIDTH, HEIGHT, SDL_WINDOW_FULLSCREEN | SDL_WINDOW_BORDERLESS );
```
Tested under ubuntu 20.04 x64 w/ gnome-flashback:
```
Package: metacity
Version: 1:3.36.1-1 (baseline focal pacakge, affected)
Version: 3.34.1 (compiled, working fine)
```
By bisecting the commits between the two versions, I ended up into this changeset, which is the root cause of the issue:
```
7a7aaa338b89c0c66122958e7c6cb56322e73371 is the first bad commit
commit 7a7aaa338b89c0c66122958e7c6cb56322e73371
Author: Alberts Muktupāvels <alberts.muktupavels@gmail.com>
Date: Fri Feb 28 19:35:32 2020 +0200
window: remove frame from fullscreen windows
src/core/window.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/src/core/window.c b/src/core/window.c
index b745cdd3..963e23a9 100644
--- a/src/core/window.c
+++ b/src/core/window.c
@@ -6963,16 +6963,14 @@ recalc_window_features (MetaWindow *window)
window->has_fullscreen_func = FALSE;
}
- /* We leave fullscreen windows decorated, just push the frame outside
- * the screen. This avoids flickering to unparent them.
- *
- * Note that setting has_resize_func = FALSE here must come after the
+ /* Note that setting has_resize_func = FALSE here must come after the
* above code that may disable fullscreen, because if the window
* is not resizable purely due to fullscreen, we don't want to
* disable fullscreen mode.
*/
if (window->fullscreen)
{
+ window->decorated = FALSE;
window->has_shade_func = FALSE;
window->has_move_func = FALSE;
window->has_resize_func = FALSE;
```
I'm not able to assess whether this should be fixed in SDL (either only or as well, since I fail to see the reason for decorated fullscreen windows), but I think this change introduces a regression (in particular with a conspicuous set of sdl-based games/apps). An ad-interim solution consists in removing the decorations when switching to fullscreen.
A minimal SDL2 fullscreen application is attached as test to reproduce the issue:
[sdltest.c](/uploads/e922a43ba101941efe0ecdb0b914d5c9/sdltest.c)
compile with:
```
clang $(sdl2-config --cflags) -c -o sdltest.o sdltest.c
clang -o sdltest sdltest.o $(sdl2-config --libs)
```https://gitlab.gnome.org/GNOME/metacity/-/issues/12segfault when META_DEBUG_NO_SHADOW=02020-07-13T17:29:18ZTomáš Bžateksegfault when META_DEBUG_NO_SHADOW=0Historically I've been setting `META_DEBUG_NO_SHADOW=0` env. var to disable window shadows. This is now causing issues.
```Thread 1 "metacity" received signal SIGSEGV, Segmentation fault.
0x0000555555568b98 in make_shadow (xrender=0x55...Historically I've been setting `META_DEBUG_NO_SHADOW=0` env. var to disable window shadows. This is now causing issues.
```Thread 1 "metacity" received signal SIGSEGV, Segmentation fault.
0x0000555555568b98 in make_shadow (xrender=0x5555558160d0, shadow_type=META_SHADOW_MEDIUM, opacity=0.66000000000000003, width=1, height=1) at compositor/meta-compositor-xrender.c:320
320 msize = shad->gaussian_map->size;
(gdb) print shad
$1 = (shadow *) 0x0
(gdb) t a a bt
...
Thread 1 (Thread 0x7ffff5d9e940 (LWP 24031)):
#0 0x0000555555568b98 in make_shadow (xrender=0x5555558160d0, shadow_type=META_SHADOW_MEDIUM, opacity=0.66000000000000003, width=1, height=1) at compositor/meta-compositor-xrender.c:320
#1 0x00005555555691a7 in shadow_picture (xrender=0x5555558160d0, shadow_type=META_SHADOW_MEDIUM, opacity=0.66000000000000003, width=1, height=1, wp=0x55555561e230, hp=0x55555561e234) at compositor/meta-compositor-xrender.c:471
#2 0x000055555556afc9 in meta_compositor_xrender_create_shadow (self=0x5555558160d0, surface=0x55555583a400) at compositor/meta-compositor-xrender.c:1233
#3 0x000055555556de0d in meta_surface_xrender_pre_paint (surface=0x55555583a400, damage=58720465) at compositor/meta-surface-xrender.c:510
#4 0x000055555556cd3b in meta_surface_pre_paint (self=0x55555583a400) at compositor/meta-surface.c:906
#5 0x0000555555566989 in meta_compositor_pre_paint (compositor=0x5555558160d0) at compositor/meta-compositor.c:351
#6 0x000055555556a93f in meta_compositor_xrender_pre_paint (compositor=0x5555558160d0) at compositor/meta-compositor-xrender.c:1098
#7 0x000055555556635d in redraw_idle_cb (user_data=0x5555558160d0) at compositor/meta-compositor.c:176
#8 0x00007ffff6f3a8d7 in g_idle_dispatch () at /usr/lib64/libglib-2.0.so.0
#9 0x00007ffff6f3feac in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#10 0x00007ffff6f40288 in g_main_context_iterate.constprop () at /usr/lib64/libglib-2.0.so.0
#11 0x00007ffff6f4061b in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#12 0x000055555558fc99 in main (argc=1, argv=0x7fffffffd4b8) at core/main.c:469
...
```https://gitlab.gnome.org/GNOME/metacity/-/issues/13VSync/tearing performance issues2021-10-26T05:30:51ZTomáš BžatekVSync/tearing performance issuesI thought I would give `metacity` a try given your recent Vulkan work. Stepping up from `marco` I'm seeing horizontal tearing, laggy rendering and overall poor performance when moving windows. Reminds me pre-XPresent era a little bit. Di...I thought I would give `metacity` a try given your recent Vulkan work. Stepping up from `marco` I'm seeing horizontal tearing, laggy rendering and overall poor performance when moving windows. Reminds me pre-XPresent era a little bit. Disabling Vulkan makes no difference. Compositing seems to be enabled:
```
$ gsettings get org.gnome.metacity 'compositing-manager'
true
```
My screen is tiled 5120x2880 with properly detected and assembled XRandr logical monitor:
```
$ xrandr --listmonitors
Monitors: 1
0: +Auto-Monitor-1 5120/600x2880/340+0+0 DP2 DP1
```
[xrandr-verbose.txt](/uploads/203624845c95fa9354306bfdb7bc1161/xrandr-verbose.txt)
Any advice for further debugging?https://gitlab.gnome.org/GNOME/metacity/-/issues/143.37.1: build fails with vulcan 1.2.148.02020-08-25T20:19:33ZTomasz Kłoczko3.37.1: build fails with vulcan 1.2.148.0```
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/metacity-3.37.1/src/tools'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/metacity-3.37.1/src'
gcc -DHAVE_CONFIG_H -I. -I.. -DMETACITY_LOCALEDIR=\""/usr/share/loc...```
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/metacity-3.37.1/src/tools'
make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/metacity-3.37.1/src'
gcc -DHAVE_CONFIG_H -I. -I.. -DMETACITY_LOCALEDIR=\""/usr/share/locale"\" -DG_LOG_DOMAIN=\"metacity\" -DG_LOG_USE_STRUCTURED=1 -DSN_API_NOT_YET_FROZEN=1 -I./core -I./include -I./core -I.. -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 -I/usr/include/gsettings-desktop-schemas -D_REENTRANT -I/usr/include/startup-notification-1.0 -I/usr/include/libgtop-2.0 -fno-strict-aliasing -Wnested-externs -Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement -Wimplicit-function-declaration -Wold-style-definition -Wjump-misses-init -Wall -Wextra -Wundef -Wwrite-strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline -Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wswitch-enum -Wswitch-default -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict -Wnull-dereference -Wdouble-promotion -Wno-error=unused-parameter -Wno-error=missing-field-initializers -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -flto=auto -flto-partition=none -c -o compositor/metacity-meta-compositor-vulkan.o `test -f 'compositor/meta-compositor-vulkan.c' || echo './'`compositor/meta-compositor-vulkan.c
compositor/meta-compositor-vulkan.c: In function ‘device_type_to_string’:
compositor/meta-compositor-vulkan.c:813:12: error: ‘VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE’ undeclared (first use in this function); did you mean ‘VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM’?
813 | case VK_PHYSICAL_DEVICE_TYPE_RANGE_SIZE:
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| VK_PHYSICAL_DEVICE_TYPE_MAX_ENUM
compositor/meta-compositor-vulkan.c:813:12: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [Makefile:1723: compositor/metacity-meta-compositor-vulkan.o] Error 1
make[4]: Leaving directory '/home/tkloczko/rpmbuild/BUILD/metacity-3.37.1/src'
```https://gitlab.gnome.org/GNOME/metacity/-/issues/15With META_COMPOSITOR=xpresent, sometimes there is flickering when hovering wi...2021-04-19T13:10:47ZDmitry ShachnevWith META_COMPOSITOR=xpresent, sometimes there is flickering when hovering windows in Window ListWhen hovering windows in Window List applet, there is sometimes very short flickering when parts of the hovered window (or something else?) are shown on top of the currently active window.
It is very short and happens randomly, in rando...When hovering windows in Window List applet, there is sometimes very short flickering when parts of the hovered window (or something else?) are shown on top of the currently active window.
It is very short and happens randomly, in random parts of the screen.
I reproduced it when the active window was telegram-desktop, and hovered window was evince.https://gitlab.gnome.org/GNOME/metacity/-/issues/16[Feature Request] Right clicking the scrollbars doesn't show quick scrolling ...2020-12-13T11:50:43ZYaron Shahrabani[Feature Request] Right clicking the scrollbars doesn't show quick scrolling menuTransferred from https://bugzilla.gnome.org/show_bug.cgi?id=619405
This is more like a feature request
I used to be a Windows user like some of the current GNOME and Linux users
One of the things I got used to is right clicking the scr...Transferred from https://bugzilla.gnome.org/show_bug.cgi?id=619405
This is more like a feature request
I used to be a Windows user like some of the current GNOME and Linux users
One of the things I got used to is right clicking the scrollbar and scrolling more precisely using a popup menu
The popup menu works like this:
If I right click on the bar itself the menu allows me the following:
Page Up
Page Down
Top
Bottom
If I right click somewhere else I get the same features plus "Scroll Here"
If a mockup is needed I'd love to provide one
I really miss this feature and I hope I reported it in the right place
Kind regards,
Yaron Shahrabani
I got used to not having this feature anymore but it could be beneficial to some users.https://gitlab.gnome.org/GNOME/metacity/-/issues/17[Feature Request] An explicit compositor bypass mechanism is lacking2021-04-19T13:10:47ZNovHak[Feature Request] An explicit compositor bypass mechanism is lackingIn current Metacity version, all application windows are composited.
However, some programs (games most notably) don't like having their window composited. Some WMs use heuristics to decide whether a window should be composited, such as...In current Metacity version, all application windows are composited.
However, some programs (games most notably) don't like having their window composited. Some WMs use heuristics to decide whether a window should be composited, such as unredirecting full screen windows ; but even that can be insufficient, e.g. when viewing a video full screen in a browser, VSync being then lost in some configurations.
In such cases, an explicit mechanism to tell whether a window shall be composited/not composited/left to the compositor's heuristics, seems a good thing.
Such a spec already exists, with the [`_NET_WM_BYPASS_COMPOSITOR`](https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm45693330279680) property. Implementing it enables application developers and even end users (via `xprop` for example) to explicitly specify that some of their application's windows should be composited/not composited.https://gitlab.gnome.org/GNOME/metacity/-/issues/18Metacity segfault on accepting Webex call2021-06-27T10:25:35ZStefanMetacity segfault on accepting Webex callWe are experiencing crashes with metacity 1:3.28.0-1ubuntu0.1 (Ubuntu 18.04, gnome-flashback) on incoming webex calls.
To check whether an update could solve the probem, I built metacity 1:3.38.0-1 (from groovy) on 18.04, but had the sam...We are experiencing crashes with metacity 1:3.28.0-1ubuntu0.1 (Ubuntu 18.04, gnome-flashback) on incoming webex calls.
To check whether an update could solve the probem, I built metacity 1:3.38.0-1 (from groovy) on 18.04, but had the same issue.
Reproduction: Install native Webex client (my version is 41.5.0.18911), wait for a call, accept this call *not* from the main window, but from the notification window. I'm not completely sure whether the webex client has to be in background or minimized to get this issue.
**syslog:**
```
...
May 26 15:52:13 atrala-stfe metacity[30300]: meta_window_unminimize: assertion '!window->override_redirect' failed
May 26 15:52:13 atrala-stfe metacity[30300]: meta_window_unstick: assertion '!window->override_redirect' failed
May 26 15:52:13 atrala-stfe kernel: [113138.913460] metacity[30300]: segfault at 8 ip 0000561c54c53a40 sp 00007ffdcfafb850 error 4 in metacity[561c54c08000+77000]
May 26 15:52:13 atrala-stfe kernel: [113138.913466] Code: 08 48 8d 15 62 9a 01 00 48 8d 35 1b a0 01 00 5b 5d 41 5c 41 5d 48 8d 3d 38 31 01 00 e9 d9 2e fc ff 66 0f 1f 84 00 00 00 00 00 <49> 8b 7d 08 48 89 f5 e8 94 3c fc ff 49 89 45 08 f6 85 48 01
May 26 15:52:14 atrala-stfe systemd[6761]: Starting Notification regarding a crash report...
May 26 15:52:14 atrala-stfe systemd[6761]: Started Notification regarding a crash report.
May 26 15:52:18 atrala-stfe kernel: [113143.644901] nouveau 0000:01:00.0: fb: VPR locked, but no scrubber binary!
May 26 15:52:19 atrala-stfe gnome-session[30032]: gnome-session-binary[30032]: WARNING: Application 'metacity.desktop' killed by signal 11
May 26 15:52:19 atrala-stfe gnome-session[30032]: gnome-session-binary[30032]: WARNING: App 'metacity.desktop' respawning too quickly
May 26 15:52:19 atrala-stfe gnome-session-binary[30032]: WARNING: Application 'metacity.desktop' killed by signal 11
May 26 15:52:19 atrala-stfe gnome-session-binary[30032]: Unrecoverable failure in required component metacity.desktop
May 26 15:52:19 atrala-stfe gnome-session[30032]: gnome-session-binary[30032]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May 26 15:52:19 atrala-stfe gnome-session-binary[30032]: WARNING: App 'metacity.desktop' respawning too quickly
May 26 15:52:19 atrala-stfe gnome-session-binary[30032]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May 26 15:52:19 atrala-stfe kdeconnectd.desktop[30361]: ICE default IO error handler doing an exit(), pid = 30361, errno = 11
May 26 15:52:19 atrala-stfe pasta.desktop[30346]: ICE default IO error handler doing an exit(), pid = 30346, errno = 11
May 26 15:52:19 atrala-stfe kernel: [113144.416686] rfkill: input handler enabled
May 26 15:52:19 atrala-stfe systemd[6761]: gnome-session.service: Main process exited, code=exited, status=1/FAILURE
...
```
**Crash log:**
[_usr_bin_metacity.1000621.crash](/uploads/cedfe26f5337e640b063f75977d5f773/_usr_bin_metacity.1000621.crash)
**Desktop, Session, Window Manager:**
```
$ printf 'Desktop: %s\nSession: %s\n' "$XDG_CURRENT_DESKTOP" "$GDMSESSION"
Desktop: GNOME-Flashback:GNOME
Session: gnome-flashback-metacity
$ wmctrl -m
Name: Metacity
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: N/A
$ dpkg -l | grep metacity
ii libmetacity3:amd64 1:3.38.0-1 amd64 library for the Metacity window manager
ii metacity 1:3.38.0-1 amd64 lightweight GTK+ window manager
ii metacity-common 1:3.38.0-1 all shared files for the Metacity window manager
```
**X11 version**
```
$ xdpyinfo | grep version
version number: 11.0
X.Org version: 1.20.8
$ dpkg -l | grep xserver-xorg-core-hwe
ii xserver-xorg-core-hwe-18.04 2:1.20.8-2ubuntu2.2~18.04.4 amd64 Xorg X server - core server
```
**Kernel**
```
$ uname -a
Linux atrala-stfe 5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
```
Any help is appreciated.https://gitlab.gnome.org/GNOME/metacity/-/issues/19Black compositor2021-06-17T20:06:57ZTrần Xuân ThanhBlack compositorThis problem occurs when using `xfce4-session-logout`, i tried with Mutter and it's totally normal so i think this is because of Metacity. Also, when I move the window too fast, screen tearing occurs (this is not so important)
https://s...This problem occurs when using `xfce4-session-logout`, i tried with Mutter and it's totally normal so i think this is because of Metacity. Also, when I move the window too fast, screen tearing occurs (this is not so important)
https://streamable.com/5t81n0https://gitlab.gnome.org/GNOME/metacity/-/issues/20Session management related issues2021-07-19T12:03:25ZTrần Xuân ThanhSession management related issuesA dialog box informing applications that do not support session saving will appear when logging out, if `canceling` or `closing` the window will cause an error `Session manager must be in idle state when requesting a shutdown`
https://s...A dialog box informing applications that do not support session saving will appear when logging out, if `canceling` or `closing` the window will cause an error `Session manager must be in idle state when requesting a shutdown`
https://streamable.com/i3lmqc
Also i hope you can lower the priority of metacity to 15 to avoid conflict with `xfsettingsd`https://gitlab.gnome.org/GNOME/metacity/-/issues/21Wrong position of the window2021-07-22T15:35:20ZTrần Xuân ThanhWrong position of the windowWindow position is wrong every metacity restart, it happens even during session restore.
Reproduce the error: https://streamable.com/1d94hmWindow position is wrong every metacity restart, it happens even during session restore.
Reproduce the error: https://streamable.com/1d94hmhttps://gitlab.gnome.org/GNOME/metacity/-/issues/22Metacity not displaying theme correctly2022-06-03T13:34:16ZTrần Xuân ThanhMetacity not displaying theme correctly`Metacity` shows incorrect theme when it starts at the same time as `xfsettingsd``Metacity` shows incorrect theme when it starts at the same time as `xfsettingsd`https://gitlab.gnome.org/GNOME/metacity/-/issues/23Remove rounded corners at the bottom edges of the window2021-10-22T17:04:40ZTrần Xuân ThanhRemove rounded corners at the bottom edges of the windowThere are several themes that are designed to create rounded corners in the corners of the windows. Metacity uses the GTK theme for decoration, but I think the rounded corners in the bottom corners of the window should be omitted.
Metac...There are several themes that are designed to create rounded corners in the corners of the windows. Metacity uses the GTK theme for decoration, but I think the rounded corners in the bottom corners of the window should be omitted.
Metacity:
![](https://imgur.com/u1gJStc.png)
Mutter:
![](https://imgur.com/xkKaKZc.png)https://gitlab.gnome.org/GNOME/metacity/-/issues/24Error displayed when opening the application2021-07-27T16:51:30ZTrần Xuân ThanhError displayed when opening the applicationIt seems that metacity has a display error when open an app that requires full screen.
https://streamable.com/040tw6
I got an error when opening this game: https://www.openra.net/It seems that metacity has a display error when open an app that requires full screen.
https://streamable.com/040tw6
I got an error when opening this game: https://www.openra.net/https://gitlab.gnome.org/GNOME/metacity/-/issues/25Opacity handling error2021-10-22T17:04:40ZTrần Xuân ThanhOpacity handling error`tooltip` appears black wrapper (Including SSD and CSD)
https://streamable.com/ki5gpp
Reproduce the problem:
```css
tooltip {
background-color: red;
border-radius: 15px;
}
```
OS: Ubuntu 20.04 / Metacity 3.36 - 3.40`tooltip` appears black wrapper (Including SSD and CSD)
https://streamable.com/ki5gpp
Reproduce the problem:
```css
tooltip {
background-color: red;
border-radius: 15px;
}
```
OS: Ubuntu 20.04 / Metacity 3.36 - 3.40https://gitlab.gnome.org/GNOME/metacity/-/issues/26issue switching between windows of the same application2022-10-22T11:51:49ZRiccardoissue switching between windows of the same applicationWhen I switch between windows of the same application, it doesn't work with _all_ applications:
- gnome terminal: OK
- gedit: OK
- chrome: KO
- emacs: KO
More specifically, for chrome and emacs it sees only one window while two are ope...When I switch between windows of the same application, it doesn't work with _all_ applications:
- gnome terminal: OK
- gedit: OK
- chrome: KO
- emacs: KO
More specifically, for chrome and emacs it sees only one window while two are open.
At the same time, the window grouping feature works very well in the bottom bar that shows all open windows and groups them by application.
In "preferences" -> "Keyboard Shortcuts", I customized "Switch windows of an application" with "Super+Tab" and disabled "Switch Applications".
Is this a known problem?
I'm on Ubuntu 20.04 running Gnome 3.36.8 flashback.
Thanks!https://gitlab.gnome.org/GNOME/metacity/-/issues/27How to get the exact size of the window2021-10-06T10:02:59ZTrần Xuân ThanhHow to get the exact size of the windowCurrently metacity uses the same decoration as CSD, however since Metacity doesn't provide anything related to `_GTK_FRAME_EXTENTS`, so screenshot apps can't get the exact window size.
I reported this issue to the developer of `xfce4-scr...Currently metacity uses the same decoration as CSD, however since Metacity doesn't provide anything related to `_GTK_FRAME_EXTENTS`, so screenshot apps can't get the exact window size.
I reported this issue to the developer of `xfce4-screenshooter`, have identified a [commit](https://gitlab.gnome.org/GNOME/gnome-screenshot/-/commit/6c1dc452) that solves this problem, however it is quite complicated to understand so would be glad if you could provide a simpler code, or something like `_GTK_FRAME_EXTENTS`https://gitlab.gnome.org/GNOME/metacity/-/issues/28Unity game engine player going fullscreen fights for mode change2023-03-09T21:00:31ZStrat agermUnity game engine player going fullscreen fights for mode changeMoving from Ubuntu 18.04 to 20.04 using GNOME Flashback and Metacity broke several of my games. They exhibit the same mode fighting behavior described in [issue #11](https://gitlab.gnome.org/GNOME/metacity/-/issues/11). Affected games in...Moving from Ubuntu 18.04 to 20.04 using GNOME Flashback and Metacity broke several of my games. They exhibit the same mode fighting behavior described in [issue #11](https://gitlab.gnome.org/GNOME/metacity/-/issues/11). Affected games include Kerbal Space Program, Valheim, and Rise of Industry. They fail to start 90 percent of the time, either exiting or hanging.
Commit 993b87455d2de3bdc42685d13bb9e555347aa7fa from Thu Mar 5 15:24:49 2020 fixed the regression introduced by the commit identified in issue #11 by waiting until idle to call check_decorated_cb. After observing that the games started more reliably with Metacity's logging enabled, I reasoned that a longer delay was needed.
The attached patch sets a 10ms delay instead of scheduling an event during the next idle time. In limited testing it has had good results.
[metacity_3.36.1_fix_for_unity_player_games.patch](/uploads/5978895af8dda79e5a7e4acfed2290ed/metacity_3.36.1_fix_for_unity_player_games.patch)https://gitlab.gnome.org/GNOME/metacity/-/issues/29building failed2021-12-15T08:40:13Zwangkerongbuilding failedWhen I buiding metacity it failed, the version of xorgproto I was using was xorgproto-2021.5
```shell
[ 420s] core/above-tab-keycode.c:52:10: fatal error: X11/extensions/XKBgeom.h: No such file or directory
[ 420s] 52 | #include <X1...When I buiding metacity it failed, the version of xorgproto I was using was xorgproto-2021.5
```shell
[ 420s] core/above-tab-keycode.c:52:10: fatal error: X11/extensions/XKBgeom.h: No such file or directory
[ 420s] 52 | #include <X11/extensions/XKBgeom.h>
[ 420s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~
[ 420s] compilation terminated.
[ 420s] make[4]: *** [Makefile:1183: core/metacity-above-tab-keycode.o] Error 1
[ 420s] make[4]: *** Waiting for unfinished jobs....
```https://gitlab.gnome.org/GNOME/metacity/-/issues/30[Feature request] Layering windows basing on a configuration file2022-03-05T18:37:40ZMathieu Viale[Feature request] Layering windows basing on a configuration fileThe windows could be dispatched in several layers according to a configuration file stored beside the metacity binary.
If no such file is present, metacity behaviour would be left unchanged.
A patch is going to be shared basing on a fil...The windows could be dispatched in several layers according to a configuration file stored beside the metacity binary.
If no such file is present, metacity behaviour would be left unchanged.
A patch is going to be shared basing on a file named ".metacity-layers" shaped like this:
#comment
[layer = 2 ]
window1
window2
[layer = 3 ]
window3
window4
In this example, all windows with a title including "window3" or "window4" should be set in the 3rd layer (first plan).
All windows with a title including "window1" or "window2" should be behind in layer 2.https://gitlab.gnome.org/GNOME/metacity/-/issues/31Metacity crashes when a child window is undocked and parent window is minimized2022-10-04T23:57:26ZMustafa Kemal GilorMetacity crashes when a child window is undocked and parent window is minimizedOS: Ubuntu 22.04, Metacity version: 3.44 (issue also confirmed in 3.37.1/3.36.1/3.38.0)
One of our customers encountered a Metacity crash when a docked QT window in their application is un-docked, and the owning parent window is minimi...OS: Ubuntu 22.04, Metacity version: 3.44 (issue also confirmed in 3.37.1/3.36.1/3.38.0)
One of our customers encountered a Metacity crash when a docked QT window in their application is un-docked, and the owning parent window is minimized. The crash output for metacity is as follows:
```bash
test@ubuntu-2204:~$ metacity --replace
**
metacity:ERROR:core/window.c:1114:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
Bail out! metacity:ERROR:core/window.c:1114:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
Aborted (core dumped)
test@ubuntu-2204:~$ metacity --version
metacity 3.44.0
Copyright (C) 2001-2009 Havoc Pennington, Red Hat, Inc., and others
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
The customer has also provided a minimal reproducer python code, which can be found in the attachment below:
[Untitled.py](/uploads/8d311b9e5702b46e7052d69d41d8f9c0/Untitled.py)
Steps for reproducing the issue:
1. Install gnome-session-flashback (metacity) and reproducer's dependencies
`sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets`
2. run python3 Untitled.py
3. Undock one of the application's child windows
4. Minimize main windowhttps://gitlab.gnome.org/GNOME/metacity/-/issues/32not able to alt-tab between windows of all workspaces2023-03-10T15:44:38ZJoel Ongnot able to alt-tab between windows of all workspacesThis bug (<https://bugzilla.gnome.org/show_bug.cgi?id=143511>) seems not to have been resolved, and remains an open issue in gnome-flashback.This bug (<https://bugzilla.gnome.org/show_bug.cgi?id=143511>) seems not to have been resolved, and remains an open issue in gnome-flashback.https://gitlab.gnome.org/GNOME/metacity/-/issues/33Fullscreen wine windows are now cropped2022-10-03T20:28:04ZAlkis GeorgopoulosFullscreen wine windows are now croppedUp to Ubuntu 20.04 / metacity 3.36.1 / wine 5 things were fine.
Now with Ubuntu 22.04 / metacity 3.44.0 / wine 6, fullscreen wine applications are cropped to e.g. 320x240 pixels and are completely unusable.
The same issue happens on ...Up to Ubuntu 20.04 / metacity 3.36.1 / wine 5 things were fine.
Now with Ubuntu 22.04 / metacity 3.44.0 / wine 6, fullscreen wine applications are cropped to e.g. 320x240 pixels and are completely unusable.
The same issue happens on Fedora 36 / wine 7.12.
Downgrading to previous metacity versions doesn't help.
Other window managers that were based on metacity, like gnome-shell (both on wayland and xorg) or marco, also have this issue.
All other window managers that I tried, like xfwm4, openbox or kwin, do **not** have this issue.
[Example application web site](https://www.geoguessr.com/seterra/en/p/sebran) and [direct link to setup-sebran.exe](https://www.geoguessr.com/seterra/download/sebran.exe).
The stderr message from metacity is:
> (metacity:11883): metacity-WARNING **: 10:08:00.041: Window 0x3200005 (Sebran) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Attaching two screenshots to demonstrate the issue.
This is the expected result, as produced with xfwm4:
![sebran-xfwm4](/uploads/2dced011e0cdd3cb3d074498178b8f21/sebran-xfwm4.png)
The is the bad result, as produced with metacity, marco, gnome-shell etc:
![sebran-metacity](/uploads/b7221918000a3fa9bcdc85a76ef64d5a/sebran-metacity.png)https://gitlab.gnome.org/GNOME/metacity/-/issues/34Crash on Ubuntu 22.102022-12-18T10:35:21ZTrần Xuân ThanhCrash on Ubuntu 22.10Reproduce:
Run `metacity --replace` in `xfce4-session`
```
(metacity:17258): Gdk-ERROR **: 17:54:30.409: The program 'metacity' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (inv...Reproduce:
Run `metacity --replace` in `xfce4-session`
```
(metacity:17258): Gdk-ERROR **: 17:54:30.409: The program 'metacity' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 4243 error_code 8 request_code 139 (RENDER) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
```
Metacity version: 3.46.0
Ubuntu 22.10https://gitlab.gnome.org/GNOME/metacity/-/issues/39metacity-3.44.0-1.fc36 crashes inside x2go session2022-11-28T16:58:34Zraveit65metacity-3.44.0-1.fc36 crashes inside x2go session```
metacity --replace
(metacity:60152): metacity-WARNING **: 21:19:54.390: Failed to create compositor: Missing composite extension required for compositing
(metacity:60152): Gdk-WARNING **: 21:19:54.513: The program 'metacity' receiv...```
metacity --replace
(metacity:60152): metacity-WARNING **: 21:19:54.390: Failed to create compositor: Missing composite extension required for compositing
(metacity:60152): Gdk-WARNING **: 21:19:54.513: The program 'metacity' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 1518 error_code 1 request_code 148 (X-Resource) minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
```
Well, normally i don't use metacity, it was only a test for fixing libwnck in a x2go session with MATE Desktop.
https://gitlab.gnome.org/GNOME/libwnck/-/issues/154
I suggest to reproduce the issue by yourself. Connecting to a qemu VM via x2go is very easy.
See https://www.addictivetips.com/ubuntu-linux-tips/set-up-x2go-on-linux/https://gitlab.gnome.org/GNOME/metacity/-/issues/40Workarea calcualtion error when monitors alligned vertically2023-11-10T08:43:29ZWalter SchneiderWorkarea calcualtion error when monitors alligned vertically# layout
```text
+-------------------------------+
| Monitor1 (1280x1024) |
| |
| |
| |
+-------------------------------+
+--------------...# layout
```text
+-------------------------------+
| Monitor1 (1280x1024) |
| |
| |
| |
+-------------------------------+
+-------------------------------+
| Monitor0 (1280x1024) |
| |
| |
|==== gnome-panel (1280x24) ====|
+-------------------------------+
```
# workarea (1)
In geometry-calculation, the gnome-panel is assumed at the upper monitor.
Maximized windows on monitor 1 are keeping an aspect at the bottom,
windows on monitor 0 are overlapped by the gnome-panel.
```text
WORKAREA: Computed work area for workspace 0: 0,0 1280 x 2048
WORKAREA: Computed work area for workspace 0 monitor 0: 0,1024 1280 x 1024
WORKAREA: Computed work area for workspace 0 monitor 1: 0,0 1280 x 1000
WORKAREA: Window 0x2200003 (Bottom Expanded Edge Panel) monitor 0 has work area 0,1024 1280 x 1024
GEOMETRY: Setting up constraint info:
orig: 0,2024 +1280,24
new : 0,2024 +1280,24
action_type : Move&Resize
is_user_action : false
resize_gravity : NorthWestGravity
fixed_directions: None
work_area_monitor: 0,1024 +1280,1024
entire_monitor : 0,1024 +1280,1024
```
# xprop (1)
```text
SM_CLIENT_ID(STRING) = "102fb320481f31264d169960163992152000000017660074"
WINDOW_ROLE(STRING) = "desktop"
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x800003
X11VNC_TICKER(STRING) = "2938/00000002/307033/1699601582.794757"
XFree86_DDC_EDID1_RAWDATA(INTEGER) = 0, -1, -1, -1, -1, -1, -1, 0, 16, -84, 38, 64, 72, 56, 72, 48, 51, 17, 1, 3, -128, 38, 30, 120, 46, -18, -91, -93, 84, 76, -103, 38, 20, 80, 84, -91, 75, 0, 113, 79, -127, -128, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 48, 42, 0, -104, 81, 0, 42, 64, 48, 112, 19, 0, 120, 45, 17, 0, 0, 30, 0, 0, 0, -1, 0, 85, 87, 53, 51, 56, 55, 67, 76, 48, 72, 56, 72, 10, 0, 0, 0, -4, 0, 68, 69, 76, 76, 32, 49, 57, 48, 56, 70, 80, 10, 32, 0, 0, 0, -3, 0, 56, 76, 31, 83, 14, 0, 10, 32, 32, 32, 32, 32, 32, 0, 79
_GNOME_BACKGROUND_REPRESENTATIVE_COLORS(STRING) = "rgb(234,244,238)"
_XROOTPMAP_ID(PIXMAP): pixmap id # 0x2c00001
ESETROOT_PMAP_ID(PIXMAP): pixmap id # 0x2c00001
_METACITY_SENTINEL(CARDINAL) = 0
_NET_WORKAREA(CARDINAL) = 0, 0, 1280, 2048
_GTK_WORKAREAS_D0(CARDINAL) = 0, 1024, 1280, 1024, 0, 0, 1280, 1000
```
# workarea (2)
Move the gnome panel to the right edge and back again to botten.
Geometry is correct:
```text
WORKAREA: Computed work area for workspace 0: 0,0 1280 x 2024
WORKAREA: Computed work area for workspace 0 monitor 0: 0,1024 1280 x 1000
WORKAREA: Computed work area for workspace 0 monitor 1: 0,0 1280 x 1024
WORKAREA: Window 0x2200003 (Bottom Expanded Edge Panel) monitor 0 has work area 0,1024 1280 x 1000
GEOMETRY: Setting up constraint info:
orig: 0,2024 +1280,24
new : 0,2024 +1280,24
action_type : Move&Resize
is_user_action : false
resize_gravity : NorthWestGravity
fixed_directions: None
work_area_monitor: 0,1024 +1280,1000
entire_monitor : 0,1024 +1280,1024
```
# xprop (2)
xprop's have been updated - as i understand this is dony by metacity.
```text
SM_CLIENT_ID(STRING) = "102fb320481f31264d169960163992152000000017660074"
WINDOW_ROLE(STRING) = "desktop"
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x800003
X11VNC_TICKER(STRING) = "2938/00000004/348510/1699601582.794611"
XFree86_DDC_EDID1_RAWDATA(INTEGER) = 0, -1, -1, -1, -1, -1, -1, 0, 16, -84, 38, 64, 72, 56, 72, 48, 51, 17, 1, 3, -128, 38, 30, 120, 46, -18, -91, -93, 84, 76, -103, 38, 20, 80, 84, -91, 75, 0, 113, 79, -127, -128, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 48, 42, 0, -104, 81, 0, 42, 64, 48, 112, 19, 0, 120, 45, 17, 0, 0, 30, 0, 0, 0, -1, 0, 85, 87, 53, 51, 56, 55, 67, 76, 48, 72, 56, 72, 10, 0, 0, 0, -4, 0, 68, 69, 76, 76, 32, 49, 57, 48, 56, 70, 80, 10, 32, 0, 0, 0, -3, 0, 56, 76, 31, 83, 14, 0, 10, 32, 32, 32, 32, 32, 32, 0, 79
_GNOME_BACKGROUND_REPRESENTATIVE_COLORS(STRING) = "rgb(234,244,238)"
_XROOTPMAP_ID(PIXMAP): pixmap id # 0x2c00001
ESETROOT_PMAP_ID(PIXMAP): pixmap id # 0x2c00001
_METACITY_SENTINEL(CARDINAL) = 0
_NET_WORKAREA(CARDINAL) = 0, 0, 1280, 2024
_GTK_WORKAREAS_D0(CARDINAL) = 0, 1024, 1280, 1000, 0, 0, 1280, 1024
```
# xwininfo
There was no change in xwininfo ouptut
```text
xwininfo: Window id: 0x75b (the root window) (has no name)
Root window id: 0x75b (the root window) (has no name)
Parent window id: 0x0 (none)
35 children:
0x1e0000c "metacity": ("metacity" "Metacity") 1x1+-200+-200 +-200+-200
1 child:
0x1e0000d (has no name): () 1x1+-1+-1 +-201+-201
0x2200003 "Bottom Expanded Edge Panel": ("gnome-panel" "Gnome-panel") 1280x24+0+2024 +0+2024
4 children:
0x2200172 (has no name): () 22x24+1212+0 +1212+2024
1 child:
0x260000d "trayapp": ("trayapp" "trayapp") 22x24+0+0 +1212+2024
0x220015f (has no name): () 22x24+1235+0 +1235+2024
1 child:
0x2600006 "trayapp": ("trayapp" "trayapp") 22x24+0+0 +1235+2024
0x2200153 (has no name): () 22x24+1258+0 +1258+2024
1 child:
0x2800006 (has no name): () 22x24+0+0 +1258+2024
0x2200004 (has no name): () 1x1+-1+-1 +-1+2023
0x1e0005c "metacity": ("metacity" "Metacity") 200x200+0+0 +0+0
1 child:
0x1e0005d (has no name): () 1x1+-1+-1 +-1+-1
0x2600008 "trayapp": () 1x1+0+0 +0+0
0x2800008 (has no name): () 1x1+0+0 +0+0
0x2800004 "Qt Selection Owner for ": () 3x3+0+0 +0+0
0x2600004 "Qt Selection Owner for trayapp": () 3x3+0+0 +0+0
0x2200016 "Panel": () 10x10+-100+-100 +-100+-100
0x2400008 (has no name): () 1x1+-1+-1 +-1+-1
0x2400001 "NetworkManager Applet": ("nm-applet" "Nm-applet") 10x10+10+10 +10+10
0x2200009 (has no name): () 1x1+-1+-1 +-1+-1
0x1e00014 (has no name): () 1x1+-1+-1 +-1+-1
0x2200001 "Panel": ("gnome-panel" "Gnome-panel") 10x10+10+10 +10+10
0x1e0000a (has no name): () 1x1+-100+-100 +-100+-100
0x1e00004 (has no name): () 1x1+-100+-100 +-100+-100
0x1e00003 (has no name): () 1x1+-100+-100 +-100+-100
0x1e00002 "Metacity": () 1x1+-100+-100 +-100+-100
0x2000001 "gsd-media-keys": ("gsd-media-keys" "Gsd-media-keys") 10x10+10+10 +10+10
0x1e00001 "metacity": ("metacity" "Metacity") 10x10+10+10 +10+10
0x1a00001 "gsd-color": ("gsd-color" "Gsd-color") 10x10+10+10 +10+10
0x1c00001 "gsd-power": ("gsd-power" "Gsd-power") 10x10+10+10 +10+10
0x1800001 "gsd-wacom": ("gsd-wacom" "Gsd-wacom") 10x10+10+10 +10+10
0x1600001 "gsd-keyboard": ("gsd-keyboard" "Gsd-keyboard") 10x10+10+10 +10+10
0x1200002 (has no name): () 10x10+0+0 +0+0
0x1200001 "gsd-xsettings": ("gsd-xsettings" "Gsd-xsettings") 10x10+10+10 +10+10
0x1000003 "ibus-xim": () 1x1+0+0 +0+0
1 child:
0x1000004 (has no name): () 1x1+-1+-1 +-1+-1
0x800016 (has no name): () 1x1+-1+-1 +-1+-1
0x1000001 "ibus-x11": ("ibus-x11" "Ibus-x11") 10x10+10+10 +10+10
0x800007 "gnome-flashback": () 10x10+-100+-100 +-100+-100
0xe00001 "ibus-extension-gtk3": ("ibus-extension-gtk3" "Ibus-extension-gtk3") 10x10+10+10 +10+10
0x800003 "Desktop": ("gnome-flashback" "Gnome-flashback") 1280x2048+0+0 +0+0
1 child:
0x800004 (has no name): () 1x1+-1+-1 +-1+-1
0x400002 (has no name): () 10x10+0+0 +0+0
0x400001 "gnome-flashback-clipboard": ("gnome-flashback-clipboard" "Gnome-flashback-clipboard") 10x10+10+10 +10+10
0x600001 "gnome-flashback-media-keys": ("gnome-flashback-media-keys" "Gnome-flashback-media-keys") 10x10+10+10 +10+10
0x800001 "gnome-flashback": ("gnome-flashback" "Gnome-flashback") 10x10+10+10 +10+10
```
# enviroment
Ubuntu 22.04 with gnome-session-flashback