Package Details: gnome-shell-extension-maximus-two-git 5-3

Git Clone URL: (read-only, click to copy)
Package Base: gnome-shell-extension-maximus-two-git
Description: Removes the title bar on maximised windows
Upstream URL:
Licenses: GPLv3
Conflicts: gnome-shell-extension-maximus-two
Provides: gnome-shell-extension-maximus-two=5
Submitter: XZS
Maintainer: XZS
Last Packager: XZS
Votes: 20
Popularity: 0.000000
First Submitted: 2015-04-16 12:46
Last Updated: 2016-11-03 13:52

Latest Comments

1 2 Next › Last »

kaptoxic commented on 2018-05-30 22:43

Is it possible to update this package (not sure if there is an upstream version that works with the newest version of Gnome)?

XZS commented on 2017-09-28 16:47

Now that we have Gnome shell 3.26, upstream finally declared it compatible with 3.24.

kaptoxic commented on 2017-05-01 02:01

Does not work with Gnome shell 3.24; not sure if the upstream has a compatible implementation.

XZS commented on 2016-06-13 15:28

As of now, it should finally work with gnome-shell 3.20.

hpstg commented on 2016-06-02 21:57

Even when the repo is updated, it won't work with gnome 3.20.

Asher256 commented on 2016-05-07 02:57

The PKGBUILD doesn't work anymore. You need to update the Github repository to:

XZS commented on 2016-04-18 23:39

I deleted my outdated fork on purpose and requested merge of an update. As soon as upstream processes this, the package will reflect a gnome-shell 3.20 compatible version.

Anonymous comment on 2016-03-23 21:10

Works wonderfully, along with the rest of your PKG files. Thanks a ton!

XZS commented on 2016-03-23 20:19

Yes, the grep script parses the JSON for compatible gnome-shell verions numbers to set up the depends array correctly. Surprisingly, also traditional tools like grep are regularly updated still today, find exactly the weird unintended behaviour I rely upon to do so and forbid it. The issue affected all my gnome-shell-extension-* packages and is fixed now.

More details can be found in the respective commit to the package collection <>.

XZS commented on 2016-03-19 22:52

Thanks for pointing out the change in metadata.json. It is indeed most probably the culprit. I will fix this in the next few days.