Support GNOME 40

[mrspikeroot]

GNOME put out this info for extension developers https://blogs.gnome.org/shell-dev/2021/03/20/extensions-rebooted-porting-your-existing-extensions-to-gnome-40/

[hedning]

Have` started working on support for gnome shell 40 here: https://github.com/paperwm/PaperWM/tree/next-release

Things should start and launching windows should work, but there's quite a few bugs (eg. scrolling the workspaces seems to crash the process, and dragging windows are broken).

[qwIvan]

Have` started working on support for gnome shell 40 here: https://github.com/paperwm/PaperWM/tree/next-release

Things should start and launching windows should work, but there's quite a few bugs (eg. scrolling the workspaces seems to crash the process, and dragging windows are broken).

The configuration panel doesn't works now. How can I modify the configuration manually?

[wbolster]

using dconf-editor, orn using the gsettings command line tool. you can check my wbolster/dotfiles repo (gnome subdirectory) for some examples

[qwIvan]

using dconf-editor, orn using the gsettings command line tool. you can check my wbolster/dotfiles repo (gnome subdirectory) for some examples

Animation of switch focus between two monitor is incorrect. How to disable animation?

[qwIvan]

using dconf-editor, orn using the gsettings command line tool. you can check my wbolster/dotfiles repo (gnome subdirectory) for some examples

The above command is refer from your dotfile, but it doesn't work.

[wbolster]

ah yes, this extension's name is problematic because it contains a : (colon), which the gsettings tool treats as a path separator (GSETTINGS_SCHEMA_DIR). i reported this before in #322.

i use an ugly symlink based hack to work around it:

    # HACK: The colon in the name confuses the GSETTINGS_SCHEMA_DIR
    # environment variable used by the ‘gsettings’ tool, so trick
    # it into picking up the right directory anyway.
    ln -s 'paperwm@hedning:matrix.org/schemas' 'paperwm@hedning'

see https://github.com/wbolster/dotfiles/blob/main/gnome/install-extensions#L39-L42

[qwIvan]

I found a solution to disable the incorrect animation. Just open gnome-teaks and disable the animation option.

[gavr123456789]

Cant enable now
UPD after alt + f2 -> r It started working

[KiaraGrouwstra]

after alt + f2 -> r It started working

this gives me: restart is not available on Wayland 😅 reboots have not fixed tho...

[nylki]

Btw. the Gnome Foundation put up a migration guide from GTK3->GTK4, if you haven't come across this one, this may be useful: https://developer.gnome.org/gtk4/4.0/gtk-migrating-3-to-4.html

[ludvigng]

Just a heads up, currently this extension breaks the overview, no windows will be shown. It's probably already known I'm guessing, but might as well mention it.

[Thesola10]

Just a heads up, currently this extension breaks the overview, no windows will be shown. It's probably already known I'm guessing, but might as well mention it.

To me it looks more like the "show only scratch windows in overview" setting working as intended but without the scratch windows :thinking:

[ludvigng]

Just a heads up, currently this extension breaks the overview, no windows will be shown. It's probably already known I'm guessing, but might as well mention it.

To me it looks more like the "show only scratch windows in overview" setting working as intended

Except I don't have that set. And scratch windows aren't shown either. I've attached an excerpt from the journal: overview-blank.txt

https://user-images.githubusercontent.com/50339757/116528427-1d227100-a8dc-11eb-98f4-7d245e4b1fc2.mp4

I did notice something else strange too. Moving the cursor between monitors makes for a really jarring animation (I set OBS to record half of each screen, the seam is in the middle between them):

https://user-images.githubusercontent.com/50339757/116528549-404d2080-a8dc-11eb-9bb0-4815951b2ad5.mp4

This is with "Workspaces span displays" set in gnome tweaks. This is the journal output from moving the mouse between a monitor and then back again:

apr 29 11:26:27 harman gnome-shell[1681]: LAYOUT apr 29 11:26:31 harman gnome-shell[1681]: switchWorkspace 0 1 apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:31 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: switchWorkspace 1 0 apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed apr 29 11:26:36 harman gnome-shell[1681]: setup_framebuffers: assertion 'width > 0' failed

E: I've attached log output for these two things. I managed to catch the third bug that was here originally, but it seems to be related to another extension. My bad!

[gcoda]

Just a heads up, currently this extension breaks the overview, no windows will be shown. It's probably already known I'm guessing, but might as well mention it.

for me, it magically got fixed with "Cleaner Overview" extension by gonza_11

[ludvigng]

Just a heads up, currently this extension breaks the overview, no windows will be shown. It's probably already known I'm guessing, but might as well mention it.

for me, it magically got fixed with "Cleaner Overview" extension by gonza_11

Oh wow, it does fix the problem. Thank you!

[nylki]

I was just testing the next-release branch of PaperWM with Gnome40 in Fedora 34.

I can confirm that using the mentioned Cleaner Overview does indeed fix the empty overview. Maybe some of that extensions logic can be adapted for PaperWM.

After that, there are still some gesture-related issue when using multi-finger gestures with a trackpad to control PaperWM: When switching windows with the 3-finger gesture as before with PaperWM now clashes with Gnome40's 3-finger workspace switching gesture. Both gestures are now fighting, resulting in a broken animation and UX in the current state. Using the Meta-left/right key-combo does work fine though.

[magthe]

I'm testing the next-release branch right now with Gnome40 on Arch.

I do have the Cleaner Overview plugin, but I still have an empty overview. Maybe there's some other extension I have that impacts my setup negatively.

The plugin ddterm still doesn't show its window, but it does take focus!

[randomvariable]

How have folk got around

Expected type string for argument 'property_name' but got type GObject_Object

[Pacman99]

Also enabling the built-in extension "Native Window Placement" fixes the empty overview.

Expected type string for argument 'property_name' but got type GObject_Object

I'm occasionally getting this too

I kind of like the diagonal animation for switching workspaces, it is wrong spatially but a very cool animation to see.

[Pacman99]

Overall release-next works pretty well thank you for all the work with that. The animations are definitely a bit odd with the switch to horizontal workspaces.

Also the paperwm settings gui doesn't open at all and changing some top-level settings in dconf seems to just crash gnome. But logging out and logging in seems to fix the crash. So applying paperwm settings requires a restart of gnome. Changing keybindings works fine.

[paradajz]

Some of my observations after trying next-release branch on GNOME 40 (openSUSE Tumbleweed, Wayland on a laptop)

1) Extension installs and loads fine, although settings can't the changed through GUI 2) Extension is fighting with the new, built in gestures. This makes it unusable on laptop unless the gestures are changed to 4-finger swipes. See https://github.com/icedman/gnome-shell-hammer 3) Resizing the windows works with keyboard shortcuts and with mouse, however windows can't be dragged at all. 4) Overview shows no windows unless Cleaner Overview is installed. https://extensions.gnome.org/extension/3759/cleaner-overview/ 5) Animations when switching from overview are kind of broken, but then again, they are kind of broken on 3.38 as well. See https://github.com/paperwm/PaperWM/issues/347

This is actually workable on a laptop, but still unusable for me on a desktop due to broken window movement. I really hope development of this extension isn't abandoned, I'd hate to switch to something else.

[tomkdale]

I have two machines running Fedora 34, I've installed the "Native Window Placement", and "Cleaner Overview" extensions on both. Yet when I go to install next-release paperwm on both, one works fine, but the other always gives me the Expected type string for argument 'property_name' but got type GObject_Object error.

[Tina-otoge]

I tried to use next-release on GNOME 40 but I had a lot of issue with my dual monitor setup. I wasn't able to get PaperWM to "snap" windows in the second display, I could only move and resize them the regular GNOME way, moving between windows on my first monitor using Super+arrow keys works fine but using Super+1,2,3,4 shortcuts made them overlap on the second monitor and breaking them out of PaperWM control Switching workspaces plays a vertical transition animation, and then when it ends perform the new GNOME 40 horizontal scrolling animation, making it very weird And generally same issues as mentioned by paradajz right above, with not being able to go in the extensions configuration GUI being a major pain.

[ludvigng]

You can "fix" the snapping by making workspaces span displays in gnome-tweaks in multi-monitor setup. It works a little funny, since the second monitor uses the second workspace, but it kinda works once you get used to it.

[cstich]

I can't seem to get the next-release branch to work at all. I am on Gnome 40 on Nixos 21.05. The error message I get when trying to use install.sh is this one:

Trying to load and enable extension:
something went wrong:
Missing metadata.json createExtensionObject@resource:///org/gnome/shell/ui/extensionSystem.js:283:19\
@resource:///org/gnome/shell/ui/shellDBus.js line 63 > eval:20:36\
Eval@resource:///org/gnome/shell/ui/shellDBus.js:63:42\
_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:310:38\
_wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34\
"')

Does anyone know how to fix this/a workaround?

Edit: The install script does not work but manually copying the repo into ~/.local/share/gnome-shell/extensions/paperwm@hedning:matrix.org/ seems to enable the extension as well. However, now I am stuck with the Expected type string for argument 'property_name' but got type GObject_Object error.

Edit 2: A quick and dirty workaround for the Expected type string for argument error is to comment out line 197 in extension.js.

[NelsonJeppesen]

I've been running PapperWM full-time on Gnome 40 (NixOS) for about a week now. Everything works as I expect, without any issues. No changes except switching PapperWM branches.

For anyone wanting to test this in NixOS, I added this overlay to home-manager to switch branch https://github.com/NelsonJeppesen/nix-lifestyle/blob/main/nixpkgs/overlays/paperwm.nix

[magthe]

Reading all of the above has prompted me to try the branch next-release a bit more seriously this time.

The one thing in my setup that doesn't work is ddterm. There are some visual cues making me think that the shortcut for it works, but the terminal window itself doesn't appear. I'm not sure where the issue is, and I don't know how to find out. Suggestions for how to track down the cause of this would be very welcome.

[rrrnld]

@NelsonJeppesen Thanks for creating the overlay! I just switched to NixOS 21.05 w/ Gnome 40. I'm unfortunately also getting

Expected type string for argument 'property_name' but got type GObject_Object

and can't enable PaperWM in Extensions.

I don't have any other extensions installed, the only other extension that I have enabled is the removable drive menu. This is the config I'm using in addition to the provided overlay:

{ config, pkgs, ... }:
{
  home.packages = with pkgs; [
    gnomeExtensions.paperwm
    gnome.gnome-tweak-tool
    gnome.sushi
    adapta-gtk-theme
    arc-theme
    paper-icon-theme
    papirus-icon-theme

    noto-fonts-cjk
  ];
}

Edit: I commented out everything in my ~/.config/paperwm/user.js and restarted, works fine now. :)

[KiaraGrouwstra]

Expected type string for argument 'property_name' but got type GObject_Object

I'm getting a similar error on Arch

[randomvariable]

For those getting the error

Expected type string for argument 'property_name' but got type GObject_Object

this is a complete hack, which is why I'm not PR'ing it, but you can change extension.js as follows

From 10d55747d353c9b2db4df46ded931718773a059f Mon Sep 17 00:00:00 2001
From: Naadir Jeewa <blah>
Date: Fri, 25 Jun 2021 10:40:12 +0100
Subject: [PATCH] This is a hack

---
 extension.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/extension.js b/extension.js
index ceda859..90da7bb 100644
--- a/extension.js
+++ b/extension.js
@@ -194,7 +194,7 @@ function notify(msg, details, params) {
     Main.messageTray.add(source);
     let notification = new MessageTray.Notification(source, msg, details, params);
     notification.setResident(true); // Usually more annoying that the notification disappear than not
-    source.notify(notification);
+    source.notify(msg);
     return notification;
 }

-- 
2.31.1

and that should let the extension load. After doing that, i've been using it for quite a while with an occasional crash of Gnome.

[magthe]

I'm seeing the occasional gnome crash/restart on starting a new app. So far it's been Zoom and Slack causing it. I'm not sure where I can catch some sort of error log to get some indication of what might cause it. Pointers are very welcome.

[cstich]

@magthe Have you had a look at journalctl yet? Something like journalctl _UID=1000 (your UID might be different though) should give you the log of the all processes you started.

[magthe]

@cstich no, didn't think of that. I'll make sure to keep it in mind the next time Gnome dies on me.

[magthe]

paperwm-crash.txt

This morning Zoom crashed Gnome for me again, actually several times and I ended up switching from PaperWM just to be able to work. I did catch the logs using journalctl _UID=1000 after the first time. The logs can be found in the attached file. I logged in 08:49:28 and the crash happened around 10:13.

Hopefully the logs can offer some indication of what the underlying issue is.

[magthe]

I decided to make one more attempt, but this time I turned off Wayland, and so far it's been more stable. No crash for the entire day so far. (I just hope I don't jinx it now :) )

[michaelhthomas]

Using the following array of extensions makes PaperWM much more usable on Gnome 40, and essentially brings back normal behavior:

• Cleaner Overview
• Vertical overview
• Disable Workspace Switch Animation for GNOME 40+

These extensions bring back proper vertical workspace navigation and also remove glitches in the overview and in navigation animations between workspaces. I'm currently using the overlay by @NelsonJeppesen on NixOS, thanks for that!

[gatlee]

gnomeExtensions.cleaner-overview
gnomeExtensions.vertical-overview
gnomeExtensions.disable-workspace-switch-animation-for-gnome-40

The packages @michaelhthomas mentioned, for the lazy :)

[raiguard]

Just wanted to pop in and say that PaperWM on Gnome 40 has worked pretty OK for me so far. I can't open the settings GUI, but luckily I already have it configured just how I want. The only other glitch I've been experiencing is that when switching workspaces, all of the workspaces are dimmed.

Unfortunately, I can't get a screenshot because it requires holding super.

I wish this project was more active, it's far and away the best tiling window manager I've ever seen.

[gcoda]

@raiguard its new gnome animation, they should fade from black, there is extension for disabling workspace switching animation but it did not work for me. i am just using using Workspace Switch Wraparound extension, and native gnome keybinding for workspace switching.

For some reason there is no Up and Down in Settings app. Manually editing switch-to-workspace-down in dconf-editor /org/gnome/desktop/wm/keybindings works.

There is also Vertical Overview extension for consistency in overview

And you could also edit PaperWM settings with dconf-editor /org/gnome/shell/extensions/paperwm/

[raiguard]

@gcoda Thanks for your tips. I was already using disable workspace switching animation, but as you said, it doesn't fix the dimming. It does fix the monitor seizure when moving windows between monitors though, which is much more important.

As for the activities overview, I avoid it entirely. I find it utterly useless for my workflow, so I actually completely avoid it and the app grid by using ArcMenu as a launcher. This way I don't have to worry about seeing the default background at any point in my workflow (I use different wallpapers per workspace).

Somewhat unrelated: Can I entirely hide PaperWM's activities button (the button that usually shows the workspace name)? I disabled the workspace names, but that changed the button to say Activities, and regular "hide activities button" extensions don't work here. I don't need workspace names because I identify them by the wallpaper I have set.

[adamlwgriffiths]

Just wanted to summarise the current state of this issue. Confirmed that this works in in Gnome 40 with the next-release branch (running NixOS 21.05).

Summary of changes required:

• use the next-release branch
  • using the nix configs provided above (my overlay),
• delete ~/.config/paperwm/user.js
  • without deleting this you cannot enable the plugin as you get the Expected type string for argument 'property_name' but got type GObject_Object error in Gnome Extensions.

The only functionality I've seen that isn't working:

• the paperwm settings dialog doesn't appear when clicked in tweaks (mentioned above).
• you cannot drag windows left or right, the mouse cursor changes but nothing happens (also mentioned above). specifically:
  • you can use the key commands to swap windows
  • you can click to change windows or click the edge to scroll
  • you cannot perform fine adjustment by dragging the title bar

There is another gnome-ism which deviates from the Gnome 39 behaviour, which im not sure is paperwm. When you login, you initially are presented with the zoomed out workspace switcher.

[magthe]

There's also something wonky with the scratch layer as opening applications configured to start on the scratch layer sometimes crashes the shell. When the shell restarts all applications are "tiled".

[paradajz]

Anyone tried PaperWM on GNOME 41?

@hedning is this extension abandoned?

[paradajz]

Was trying it out on GNOME 41. Works mostly the same as in GNOME 40, with the added annoyance that opening new windows sometimes results in glitchy animation. metadata.json needs to be modified by adding 41 to supported GNOME versions. Cleaner overview officially isn't compatible with GNOME 41 as well, meaning no windows in overview, but, same hack can be applied - just add 41 to its metadata.json file and it works

[randomvariable]

I've just done a fresh Fedora 35 beta install, and it looks like most of the dconf settings are missing, such that the keybindings can't be set.

[paven]

On Ubuntu 20.10, X, Gnome 40. PaperWM branch: next-release

Not sure if it is gnome 40 related. But it is PaperWM related.

• Overiew does not show any windows. (works if PaperWM, is disabled) work around install: https://extensions.gnome.org/extension/3759/cleaner-overview/
• PaperWM Settings does not open. Workaround: dconf-editor /org/gnome/shell/extensions/paperwm/

Update note: I found out workarounds in the thread above, so it looks like the problems was already reported.

Thank you and let me know if I can help out.

[rrrnld]

I have just updated nixos-unstable and I'm now using Gnome 41. I could get PaperWm to run using the following overlay:

            (self: super: {
              gnomeExtensions = super.gnomeExtensions // {
                paperwm = super.gnomeExtensions.paperwm.overrideDerivation (old: {
                  version = "pre-41.0";
                  src = super.fetchFromGitHub {
                    owner = "paperwm";
                    repo = "PaperWM";
                    rev = "e9f714846b9eac8bdd5b33c3d33f1a9d2fbdecd4";
                    sha256 = "0wdigmlw4nlm9i4vr24kvhpdbgc6381j6y9nrwgy82mygkcx55l1";
                  };
                  patches = old.patches ++ [
                    ./patches/paperwm-gnome-41.patch
                  ];
                });
              };
            })

paperwm-gnome-41.patch looks like this (it's only a change to announce that the extension supports Gnome 41):

diff --git a/metadata.json b/metadata.json
index cb126e9..6da2298 100644
--- a/metadata.json
+++ b/metadata.json
@@ -4,6 +4,6 @@
   "description": "Tiling window manager with a twist",
   "url": "https://github.com/paperwm/PaperWM",
   "settings-schema": "org.gnome.Shell.Extensions.PaperWM",
-  "shell-version": [ "3.28", "3.30", "3.32", "3.34", "3.36", "3.38", "40"],
-  "version": "40.0"
+  "shell-version": [ "3.28", "3.30", "3.32", "3.34", "3.36", "3.38", "40", "41"],
+  "version": "41.0"
 }

I have the same observations as @paradajz: The animations are a bit off. The windows spawn in the bottom left corner of the screen and then jankily get moved to the place where the usual PaperWM spawn animation starts. Cleaner overview isn't compatible so I'll patch that as well.

[soraxas]

Hi all! I'm not sure if this is common or not, but ever since switching to the GNOME 40 branch, the scratch layer had been a bit funky to me. It works well when manually switching a window with the key shortcut Super + Escape.

However, when using the pref file in ~/.config/paperwm/user.js to automatically place window to scratch (via matching wm_clas or wm_title), it sometimes crashes my window manager (and then after crashing gnome restarts the wm).

The journalctl log looks like:

Nov 08 10:12:03 manjaro audit[1299]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj==unconfined pid=1299 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Nov 08 10:12:03 manjaro kernel: traps: gnome-shell[1299] general protection fault ip:7f9beea7e5e7 sp:7ffd7e0bea50 error:0 in libmozjs-78.so[7f9bee6a1000+b4c000]
Nov 08 10:12:03 manjaro kernel: audit: type=1701 audit(1636326723.133:488): auid=1000 uid=1000 gid=1000 ses=1 subj==unconfined pid=1299 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Nov 08 10:12:03 manjaro audit: BPF prog-id=69 op=LOAD
Nov 08 10:12:03 manjaro audit: BPF prog-id=70 op=LOAD
Nov 08 10:12:03 manjaro audit: BPF prog-id=71 op=LOAD
Nov 08 10:12:03 manjaro systemd[1]: Started Process Core Dump (PID 238474/UID 0).
Nov 08 10:12:03 manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@10-238474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
Nov 08 10:12:03 manjaro kernel: audit: type=1334 audit(1636326723.147:489): prog-id=69 op=LOAD
Nov 08 10:12:03 manjaro kernel: audit: type=1334 audit(1636326723.147:490): prog-id=70 op=LOAD
Nov 08 10:12:03 manjaro kernel: audit: type=1334 audit(1636326723.147:491): prog-id=71 op=LOAD
Nov 08 10:12:03 manjaro kernel: audit: type=1130 audit(1636326723.147:492): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@10-238474-0 comm="systemd" exe="/usr/lib/s>
Nov 08 10:12:04 manjaro systemd-coredump[238475]: [🡕] Process 1299 (gnome-shell) of user 1000 dumped core.

                                                      Found module linux-vdso.so.1 with build-id: 22c299cd29a55a3d70d5abdd9c15cc65ec4fa843
                                                      Found module libnss_dns.so.2 with build-id: b0d90fd1794c177c70f1e457c11ec1a7f87a41ed
.....
.....
Nov 08 10:12:05 manjaro systemd[1]: systemd-coredump@10-238474-0.service: Deactivated successfully.
Nov 08 10:12:05 manjaro kernel: audit: type=1131 audit(1636326725.040:493): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@10-238474-0 comm="systemd" exe="/usr/lib/s>
Nov 08 10:12:05 manjaro audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@10-238474-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
Nov 08 10:12:05 manjaro systemd[1]: systemd-coredump@10-238474-0.service: Consumed 1.850s CPU time.

It is weird because it does not always crashes (sometimes it was able to place the matched window to scratch). But when it crashes, the window that is supposed to be matched will NOT be in the scratch layer (after the wm restarted). And the alternating in-between crash and no crash can happens in consecutive closing and relaunch the same window.

I suspect this is related to the weird window glitch in GNOME 40 when creating new window that wasn't present in the previous GNOME.

This is a shame because paperwm is such an amazing window manager that I absolutely love using.

[liquidev]

@soraxas I had the exact same issue on GNOME 3.38. Not sure why that was a thing, but the only solution I know of is to not automate putting windows into the scratch layer :/