wilfm / gnomeextensionmaximustwo Goto Github PK

I wrote on the website Gnome Extensions (in bugs and comments). For reliability I add and here.

Many windows demand additional click for the placement...

For example we open App Menu Gnome 3, and we start from it the Gnome 3 Settings... Or, from there - we start Web Apps from Google Chrome (or from Chromium). Or we start Web Apps, directly, from Google Chrome-Chromium.

The window begins to be started, and, then, the cursor of a mouse changes on a cross... And... Correctly. It is required to make additional click... For placement of a window...

And there is a lot of such windows.

Wildly inconveniently. And wildly irritates...

And if to speak about tablets, then such behavior at placement of windows, in general, of IMHO, inadmissibly.

The request to correct...

Best Regards.

Althought I can easily use meta+arrow keys to maximize or restore windows size, other users are "click-oriented" and may have difficulties using the changed pixeç-saver extension. Pixel saver keeps the buttons on the activities bar. Is it possible to somehow add these buttons/actions on the menu, so I can offer this extension to other users which are not keyboard oriented?

The title is shown on the panel for a maximized window:

However it not shown for a a half maximized window, though the removal of a titlebar and dragging the panel to move the window still works:

Gnome 3.14.2, Fedora 21 64bit

For some reason Version 4 of this extension is causing gnome-shell to run at a consistent 20-25% CPU. I've noticed similar complaints on Pixels Saver extension, so perhaps it's some shared code between the two extensions.

I've not seen any problems with Version 2 of Maximus Two, so the CPU eating bugs were introduced in Version 3 or 4.

I'm using Ubuntu Gnome 14.10 with GNOME Shell 3.12.2.
The extension works well if I maximize or minimize a running application window - but if an application starts maximized, the title bar remains visible (but you can't use the minimize/maximize/close buttons on it).
Minimizing and maximizing the window hides the title bar, but it's annoying to do that every time the application starts...

Each time I lock my GNOME session and log in again, the extension gets disabled. Looking at lg / Extensions / View Errors, I see:

TypeError: str.split(...)[1] is undefined

... which, after grepping the extension folder, suggest id = str.split(/child(?:ren)?:/)... in guessWindowXID sometimes has less than two elements.

Restarting Shell (Alt+F2, r) fixes the problem, but then at the next lock/login the extension will crash.

List of windows I have: [SublimeText, Eclipse, XChat, Firefox, Chrome, Thunderbird, Files, VirtualBox, Videos, Skype, Pidgin, Shutter]. Running GNOME 3.12 under Ubuntu GNOME.

When right-clicking or double-clicking in some applications (e.g. nautilus, dia), the mouse pointer becomes a cross and you must click anywhere on the screen to continue doing anything.

E.g.: nautilus

1. Right-click on a file or directory
2. Select Properties

I traced the problem back to a call to xwininfo in decoration.js (l. 50):

id = GLib.spawn_command_line_sync('xwininfo -children -id 0x%x'.format(act['x-window']));

I suspect that act['x-window'] might be empty or undefined, as in facts the same behavior happen when I execute xwininfo -id 0x in the terminal (i.e. the command that is executed from the extension if act['x-window'] is empty).
However I don't know how to properly debug Gnome extensions and inspect their state, so I won't be able to help much more here.

System info

• Distribution: Arch Linux
• Gnome Shell: 3.14.3
• xwininfo: 1.1.3 (from package xorg-xwininfo 1.1.3-1)

it's like the notification area grows to fill the gap of the title bar. Clicking on the notification area solves, but it's annoying.

I imagine xprop is installed by default in a lot of distros, but in Arch it's part of the xorg-utils package, which is not a dependency of xorg-server or gnome-shell. You should mention that some users will have to install this manually on your Gnome page.

Hello. I used to frequently reinstall this extension because sometimes I had some problems with it. Specifically, it reported an "error" on my Firefox browser so I found that method to be useful to get it working again without a GNOME reload. However, today I couldn't reinstall the extension again. Don't know if it was upgraded and now it is not compatible with my GNOME or distribution, I don't know.
I was trying to find some kind of release history to manually download an older version but every attempt failed.
I'm running Debian Jessie and my GNOME version is 3.14.4. I can provide any other information is needed. Thank oyou you so much in advance.

When I switch among different instances of sublime/firefox/whatever, the title is not refreshed, it keeps displaying the old title.

OS: Ubuntu 14.04

I really only want chrome and gnome-terminal to undecorate.

This is also a useful setting as an easy workaround for any future app that this doesn't play well with for whatever reason - just blacklist it.

It's really an awesome item!
But I found the problem just described in title. My system is UB15.10 shell version is 3.16.
When I click the folder to open it, mouse will change it sharp to a cross then I need one more click to open the window.
And it also happened on some pop-up window.
By the way, maxims can work fully on 3.16 and it don't have this problem.

When maximising a window using this plugin, the window icons disappear, which means that for most applications it is now impossible to unmaximise or otherwise resize the window.

One option (I don't know if this is possible) would be to add window icons to the right of the menu bar. This is what Firefox (which has its own built-in method of hiding the title bar) does.

Personally don't really see an use for it, I never care what the title is, it just makes the top bar look more crowded.

When enabling your extension on my soon to be coming RHEL-7.2 (that's Gnome 3.14 and gnome-shell 3.14.4) I get gnome-shell crashing. Not crashing like getting GDM login page, but getting just a black screen and computer not reacting on any other key than -- to get to the console. Complete journalctl output is on https://mcepl.fedorapeople.org/tmp/journal-log-2015-10-02_02.txt, but I think the relevant part is:

říj 02 16:14:01 mitmanek gnome-session[5843]: (gnome-shell:6079): Gjs-WARNING **: JS ERROR: TypeError: Shell.StageInputMode is undefined
říj 02 16:14:01 mitmanek gnome-session[5843]: onFocusChange@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:74

I don’t have a proper backtrace from crash, but the best I can get it is http://faf-report.itos.redhat.com/reports/11392/

Gnome 3.16 has been released

Mainstream support is currently not quite available (except on Arch),a Ubuntu PPA's on the development version need to be used, & for Fedora you need the 22 Alpha (or possibly backports to older versions).

If you are using 3.16 and want, add 3.16 to the metadata.json file (similar to the method here) and place the extension's files in ~/.local/share/gnome-shell/extensions/[email protected]. I will submit a update at a future date after testing it and attempting to fix existing issues.

decoration.js line 315

Ubuntu 14.04

WINE windows title bars are not hidden...

Black area when applications start full screen.

Hi

I am using this extension on a touch screen laptop (ASUS VivoBook S400ca). This helps a lot since this laptop has a pretty low resolution (1366x768). But I have one suggestion to improve this extension.

I use the gnome-tweak-tool to allows title bar to have all three buttons (maximize, minimize and close). It would be great to, when these buttons are active, to put these options on the drop down menu in the Top Bar (the menu that includes the application icon). It already includes an "Exit button" by default, and including maximize and minimize too it would give better integration with the desktop.

Thanks.

When i turn off one extension, it appear. I need switch tab to other windows, and switch back, black bar disappear.
I'm using Fedora 21, gnome 3.14.2

The extension stops working if the any theme other than default (Adwaita) is used. As a long-time Ambiance theme user, I would appreciate if you could fix the issue.

I am running Ubuntu Gnome 16.04 (Gnome 3.18).

I have tried to install extension from https://extensions.gnome.org/extension/844/maximus-two/ as described in readme. When prompted, choosen Install, but nothing happens. When I refresh https://extensions.gnome.org/extension/844/maximus-two/ I still see OFF.

I have xprop and xwininfo installed.

Thanks for this must have extension, keep up good work. 👍

Subj.

Sometimes works (cleaning a title bar (at Web Apps)), but doesn't work more often...

I wanted to use this extension for XBMC so that I could have it fullscreen on one monitor, but still use another monitor for other things. XBMC does not have a "windowed fullscreen" option on Linux, so MaximusTwo ought to be the solution, for Gnome.

But, when I maximise the XBMC window, the contents do not resize. It all works fine if I resize the window manually (well, XBMC has other issues there, but the contents fit the frame), or if I maximize without MaximusTwo (non-borderless). I just seems like MaximusTwo changes the window size in such a way that XBMC does not know the even has happened.

I don't have trouble with other windows, I've tried, just this one.

Perhaps, after maximising, MaximusTwo could do a little extra 'prodding' to make sure the window's owner gets the message?

Steps to reproduce:

1. Open Konsole in gnome-shell.
2. Fullscreen it with Meta+
3. Lock screen with Meta+L (or wait for screen to time out/suspend)
4. Wakeup machine

behavior: Konsole is full-screened, except where the title bar would be shows desktop

Expected behaviour: Konsole will stay full-screened

Gnome Shell Version 3.14.1
Debian Jessie

Any ideas why this is happening, or how I can go about debugging it?

When this extension is used in combination with hidetopbar, tabbed windows may cause the whole interface to be unreactive to any mouse action. More details can be found in issue mlutfy/hidetopbar#88.

I'm on Arch using gnome-shell 3.16.1. My metadata.json file looks like this:

{"shell-version": ["3.8", "3.10", "3.12", "3.14", "3.16"],"uuid": "[email protected]", "name": "Maximus Two", "description": "Removes the title bar on maximised windows.\n Based on Pixel Saver (use Window Buttons to get the buttons (you can configure them then)\n You should be albe to use the original Maximus extension if you have 3.4 or 3.6", "url": "https://github.com/wilfm/GnomeExtensionMaximusTwo", "version": 2}

Can't figure out why it does't appear. I have restarted.

When I start a programm full-sized, there is another black space below the normal black bar. When I turn it into an window and maximise it again, than the black space disapears and everything like it should be.

I use Debian 8 Jessie, with gnome 3.14

I'm really fond of the behaviour of AwesomeWM and bspwm (example config) where no windows have decorations and the title of the focused window is displayed in the panel, regardless of it being maximised/unmaximised. Would it be possible to have this behaviour as an option in MaximusTwo?

The extension does not work with Gnome 3.24. (On Arch Linux, package gnome-shell 3.24.1+2+g45c2627d4-1.) It seems that updating the version in metadata.json cannot help either. The extensions throws the following error:

gnome-shell[638]: JS ERROR: Exception in callback for signal: extension-found: TypeError: redeclaration of let i
                                                 @/usr/share/gnome-shell/extensions/[email protected]/extension.js:50:7
                                                 initExtension@resource:///org/gnome/shell/ui/extensionSystem.js:221:5
                                                 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:168:18
                                                 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:304:9
                                                 _emit@resource:///org/gnome/gjs/modules/signals.js:126:27
                                                 ExtensionFinder<._loadExtension@resource:///org/gnome/shell/misc/extensionUtils.js:184:9
                                                 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22
                                                 bind/<@resource:///org/gnome/gjs/modules/lang.js:95:16
                                                 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:1
                                                 ExtensionFinder<.scanExtensions@resource:///org/gnome/shell/misc/extensionUtils.js:189:9
                                                 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22
                                                 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:306:5
                                                 enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:314:9
                                                 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:345:9
                                                 init@resource:///org/gnome/shell/ui/extensionSystem.js:353:5
                                                 _initializeUI@resource:///org/gnome/shell/ui/main.js:219:5
                                                 start@resource:///org/gnome/shell/ui/main.js:127:5
                                                 @<main>:1:31

It seems GJS was updated, as reported here; gjs changelog.

Can the extension be easily fixed, i.e. modified to accommodate these changes? If not, is it possible for the author to describe how the extension works, so that the community (including myself) can step in and try to make the extension work?

It works like a charm but it's impossible to disable the fullscreen on a fullscreened app at the second monitor. There's simply is no button for it.

Having trouble with this on 3.18

Sometimes MaximusTwo stucks the poping-up window of some applictions. For example, when I try to open the gnome-control-center, the mouse-cursor turns into a cross weirdly, and the window of control center never shows up untill press the left mouse button.
After turn off MaximusTwo, everything is fine.

Hi.
Setting up Empathy, I coud see that opening one friend's window chat, all gnome-shell crashes. Deactivating the MaximusTwo plugin solves the problem.
Curiosly, that only happends with this ONE friend on they 3 different account that he has: over Outlook, Hangouts and Facebook, and I could talk with the other friends without problem.
Analyzing it, the only difference maybe is that his name contains de 'ñ' character (and this is the name of the new window).
It's the first time that I opened that window and use Empathy [on this machine], so the window is not maximize and the size and positions was the standard.

Analyzing the 5 differents logs that I had, I notice that messages from Maximus Two appeared after the crash, so a try to deactivate Maximus Two and that works.

PS: I post that crash here because Maximus Two is the direct responsible of that, but this could be a gnome-shell related bug.
PS2: Searching on Google I couldn't find something useful about the GTK Critical errors that I could see.

This shows in the journalctl output:

Nov 22 14:00:26 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41
Nov 22 14:00:30 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41
Nov 22 14:00:48 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41
                                            changeActiveWindow@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:65
                                            onFocusChange@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:81
                                            AppSwitcherPopup<._finish@resource:///org/gnome/shell/ui/altTab.js:252
                                            wrapper@resource:///org/gnome/gjs/modules/lang.js:178
                                            SwitcherPopup<._keyReleaseEvent@resource:///org/gnome/shell/ui/switcherPopup.js:199
                                            wrapper@resource:///org/gnome/gjs/modules/lang.js:178
Nov 22 14:00:49 mitmanek CROND[5290]: (pcp) CMD ( /usr/libexec/pcp/bin/pmlogger_check -C)
Nov 22 14:00:51 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41
                                            changeActiveWindow@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:65
                                            onFocusChange@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:81
                                            AppSwitcherPopup<._finish@resource:///org/gnome/shell/ui/altTab.js:252
                                            wrapper@resource:///org/gnome/gjs/modules/lang.js:178
                                            SwitcherPopup<._keyReleaseEvent@resource:///org/gnome/shell/ui/switcherPopup.js:199
                                            wrapper@resource:///org/gnome/gjs/modules/lang.js:178
Nov 22 14:00:57 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41
Nov 22 14:00:58 mitmanek gnome-shell[5053]: JS ERROR: TypeError: appMenu._label.setText is not a function
                                            updateAppMenu@/home/matej/.local/share/gnome-shell/extensions/[email protected]/app_menu.js:41

Using an experimental gnome-shell-3.22.2-1.el7.x86_64 on RHEL-7.

Hello. I used to frequently reinstall

ARch 64, just upgraded to gnome 3.18, extension didn't work.

I updated metadata.json from 3.16 to 3.18 and tried again, I got an error in lg of:

No signal 'maximize' on object 'ShellWM'

Sometimes, for some windows, they start with title bar visible and I have to minimize and maximize the window in order to get rid of the title bar...

Also, some Java apps (e.g. Freeplane, JEdit) behave strangely in fullscreen (when title bar is not visible)

Ubuntu-Gnome 15.04
gnome-shell 3.14.4

This extension crashes, causing the giant ugly title bars in gnome to take over. When I look at the extensions list in Tweak Tool, there is an Exclamation next to Maximus Two

I have to restart gnome shell, Alt+F2, then 'r' then 'Enter' in order to restore normal functionality

Can anything be done to fix this?

Also, when I switch focus from a Maximus Two maximized window, to a different window, and return to a maximized window, the window is never showing the full window. I have to 'Unmaximize' then 'Maximize' again to get it to display normally. This is more an inconvenience and is not as annoying as the extension crashing all the time. If this offers some insight as to why the extension keeps crashing, great.

I’m using Fedora 25 and after installing the extension, my operation system simply FREEZED!!
No operation works and even I CANNOT enter any other tty after reboot.
No error info in the only tty. The last info in the only ttf is “Started GNOME Display Manager. Dispatcher Service...t.-8ac8-4539-88f6-51cae1b087d6”
Can anyone help me since I REALLY don’t want to reinstall my os again?