Closed nicjohnston closed 3 years ago
I experience the same problem, you can apply this patch to make the extension load:
The reason is this upstream commit that removed the _updateScrollAdjustment
function. There are other problems as well, but it seems to more or less work.
@uno20001 Thanks for the patch. Could you please elaborate what other problems you have?
It seems the flags
argument has been dropped from multiple functions, and that generates warnings:
this.set_allocation(box, flags);
children[i].allocate(childBox, flags);
vfunc_allocate(box, flags)
The _updateWorkspaceActors()
function has also been dropped, although I have not identified what the lack of this override manifests in.
In the pop-up with the thumbnails, the indicator is not visible in the first column. But even when it's visible, its position is not quite right, it's very close to the workspace thumbnail to the left - I guess this is why it cannot be seen in the first column.
In the overview, the indicator first jumps to its "original" position (where it would be if the extension wasn't used), and only then jumps to the correct position.
When the workspaces are displayed vertically in the overview ("Show workspace grid in the overview" is off), I cannot scroll with the mouse to the last two workspaces, I cannot scroll past the seventh one. (There are 3x3 workspaces.)
On some workspaces, the thumbnail-less pop-up ("Show workspace thumbnails" is off) is bigger on the first two workspaces than on the others for no apparent reason:
Thanks a lot! We'll need to have a look at these issues.
There is also this ( #124 ):
gnome-shell[2067]: JS WARNING: [/usr/share/gnome-shell/extensions/wsmatrix@martin.zurowietz.de/ThumbnailWsmatrixPopup.js 59]: Too many arguments to method Clutter.Actor.set_allocation: expected 1, got 2
@ebeem Do you remember why there is an override for the _updateScrollAdjustment
function? The only difference I can tell is that the override uses duration: 1
instead of duration: WORKSPACE_SWITCH_TIME
(250).
Edit: We talked about it here. I couldn't test it then (and now) because animations are disabled in my testing VM. So the override should probalby remain.
What do you suggest for people using gnome 3.38?
Upgrade to the new release v4.0.3 or do not upgrade and stick to v4.0.2?
Because aside from https://github.com/mzur/gnome-shell-wsmatrix/issues/124 I can't see any other problem at least on Arch.
I started work on a PR to fix the issues with GNOME 3.38 and will be published as a new major version of this extension ( #125 ).
@aminvakil You are welcome to use the gnome-3.38
branch and test the fixes. The issue you have reported should already be fixed there.
@uno20001 These two of you reported issues are unrelated to the switch to GNOME 3.38 and already present in earlier versions:
When the workspaces are displayed vertically in the overview ("Show workspace grid in the overview" is off), I cannot scroll with the mouse to the last two workspaces, I cannot scroll past the seventh one. (There are 3x3 workspaces.)
On some workspaces, the thumbnail-less pop-up ("Show workspace thumbnails" is off) is bigger on the first two workspaces than on the others for no apparent reason
I'll open separate issues for these (#126, #127).
Regarding the following issue, I'm not sure if this is related to the switch to GNOME 3.38:
In the overview, the indicator first jumps to its "original" position (where it would be if the extension wasn't used), and only then jumps to the correct position.
Maybe it is already resolved with the change to WorkspacesDisplayOverride in the gnome-3.38
branch. But maybe it is unrelated to GNOME 3.38 (@ebeem?).
Regarding the following issue, I'm not sure if this is related to the switch to GNOME 3.38::
- In the overview, the indicator first jumps to its "original" position (where it would be if the extension wasn't used), and only then jumps to the correct position.
@mzur I'm not sure either, but I don't recall having this behaviour on Gnome 3.36.1.
I have updated to https://github.com/mzur/gnome-shell-wsmatrix/releases/tag/v5.0.0-beta and the issue (#124) that I have been reported has been successfully fixed, also I can't see any other problem, please let me know if you wanted to test the extension in any specific circumstances.
@aminvakil There are still a few issues that should be sorted out in #125. Feel free to help there if you like.
Closing this in favor of #125.
I just updated to Gnome 3.38.0 on Debian Testing and this extension seems to be broken. After re-installing from the git repo, I have the following error in
$ journalctl /usr/bin/gnome-shell -b 0
:Thanks for creating this extension, it is a key part of my workflow.