it should also be possible to click on it to focus the topmost maximized window

Currently icons for every window regardless of current workspace are displayed in the applet.
This does not match the workflow people are used to when using the Window List applet.

System: Arch Linux 64bit, mate-netbook 1.18.0-1, marco 1.18.0-1

In mate-tweak, I have set the option "Undecorate maximized windows", so that the title bar is hidden when the window is maximized.
However, when trying to move the window by either shortcut, Alt-Space -> Move or Alt-Click + Dragging, the mouse cursor will change to the moving icon but the window will only be unmaximized. The mouse "loses control" over the window. This is for example contrary to the behaviour in XFCE, where a window with hidden title bar will be unmaximized and moved as expected.

Steps to reproduce:

1. Enable "Undecorate maximized windows" in mate-tweak or with gsettings set org.mate.maximus.undecorate true
2. Maximize a window
3. Alt-Click + Drag the window OR Alt-Space + Move OR use "Move Window"-Shortcut (Alt+F7 for me)

Expected results:
The window is unmaximized, gets its titlebar back and will be moved with the cursor.

Actual results:
The window is unmaximized and gets its titlebar back, but the cursor does not move the window.

I also checked the last releases of Ubuntu Mate from 16.04 to 17.04 and the issue is present there too.

Steps to reproduce:

1. Add Window Picker applet to the panel.
2. Open multiple windows.
3. See that only the first application button has icon, other buttons are just empty space.

Package versions:

• mate-netbook (gtk3) 1.12.0
• mate-panel (gtk3) 1.12.0
• gtk3 3.18.5

@flexiondotorg @monsta
New release at pre-release folder on server. It needs to be tested and tag.

The is a repetitive task of right clicking the icon and going to unmaximize would be much more intuitive with a button next to the title where the close button is.

Hi, I am not able to build this on Mint Olivia. Maybe a repository is missing.

Here the output of my attempts:

daniel@EeePc ~/workspace/mate-netbook-git $ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @file support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether NLS is requested... yes
checking for intltool >= 0.34... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.14.2
checking for XML::Parser... ok
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for MAXIMUS_DEPS... no
configure: error: Package requirements (gtk+-2.0
gio-2.0
libmatewnck
xtst
libfakekey
unique-1.0
) were not met:

No package 'xtst' found
No package 'libfakekey' found
No package 'unique-1.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables MAXIMUS_DEPS_CFLAGS
and MAXIMUS_DEPS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

daniel@EeePc ~/workspace $ sudo apt-get build-dep mate-netbook
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Quellpaket für mate-netbook kann nicht gefunden werden.

daniel@EeePc ~/workspace $ sudo apt-get install cdbs, debhelper, libgtk2.0-dev, libmatepanelapplet-dev, libmatewnck-dev, libfakekey-dev, libunique-dev, mate-doc-utils, mate-doc-utils-gnome, mate-common
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
E: Paket cdbs, kann nicht gefunden werden.
E: Paket debhelper, kann nicht gefunden werden.
E: Paket libgtk2.0-dev, kann nicht gefunden werden.
E: Mittels regulärem Ausdruck »libgtk2.0-dev,« konnte kein Paket gefunden werden.
E: Paket libmatepanelapplet-dev, kann nicht gefunden werden.
E: Paket libmatewnck-dev, kann nicht gefunden werden.
E: Paket libfakekey-dev, kann nicht gefunden werden.
E: Paket libunique-dev, kann nicht gefunden werden.
E: Paket mate-doc-utils, kann nicht gefunden werden.
E: Paket mate-doc-utils-gnome, kann nicht gefunden werden.

When closing KeePassX when it's not having focus mate-maximus will crash. It might crash with other programs as well, but this is easiest to reproduce.

$ gdb mate-maximus 
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mate-maximus...Reading symbols from /usr/lib/debug/usr/bin/mate-maximus...done.
done.
(gdb) run
Starting program: /usr/bin/mate-maximus 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef8fa700 (LWP 14553)]
no maximize: true
[New Thread 0x7fffef0f9700 (LWP 14554)]
The program 'mate-maximus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 1732 error_code 3 request_code 20 minor_code 0)
  (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 --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0x7fffef0f9700 (LWP 14554) exited]
[Thread 0x7fffef8fa700 (LWP 14553) exited]
[Inferior 1 (process 14550) exited with code 01]

Steps to reproduce:

1. Run any CSD app (e.g. gedit 3.14) while mate-maximus is running.
2. Maximize its window. If the "undecorate" option isn't set, you'll see this CSD window getting an additional window decoration, which is excessive for CSD windows. If the "undecorate" option is set, the decoration won't appear (which is normal).
3. Unmaximize its window. This time, the additional window decoration will appear for sure.

mate-netbook ships with it's own window list applet. It would be nice if that applet supported switching of windows by scrolling the mouse wheel on in by the title bar. The default window applet allows this by scrolling up to go left, and down to go right.

Debian has raised the following bug:

• mate-netbook - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827231

This MATE component needs migrating to GtkApplication:

• https://developer.gnome.org/gtk3/3.20/gtk-migrating-unique-GtkApplication.html

... See [1].

Mike

[1] http://anonscm.debian.org/gitweb/?p=pkg-mate/mate-netbook.git;a=blob;f=debian/man/mate-maximus.1;h=4ecee7fe40743e34088f22ad26009d0a86cd29d1;hb=aa3272a55294d911d50ba5e48c19907e75dfcdf7

When I use numix-gtk theme the applet turn grey instant of the numix color.

In Mate 1.12 the Applet does not undecorate the Windows anymore. On an maximized Window it provides a Close-Button. But without undecorating the Applet ist only a nice Window Picker.
Feel free to delete this Issue, if there is any workaround etc.

Mate 1.12.0 on Linux Mint 17.2 via Romeo

Expected behaviour

Setting org.mate.maximus no-maximize true and org.mate.maximus undecorate true should always undecorate windows that start maximized.

Actual behaviour

Windows that start maximized are not always undecorated. Depending on the window compositor, they're undecorated:

• around 9 out of 10 times when using Marco (Adaptive compositor)
• around 1 out of 10 times when using Marco (No compositor) or Marco + Compton

This only happens on windows that start already maximized.

Video:
https://user-images.githubusercontent.com/787075/122656302-a19cad80-d12f-11eb-81cc-b1b23fe727d5.mp4
(the extra window buttons is because I'm using window-buttons-applet, but it also happens with default mate-panel layout + applets)

Steps to reproduce the behaviour

1. Set org.mate.maximus no-maximize true and org.mate.maximus undecorate true
2. Choose Marco (No compositor) or Marco + Compton as window manager/compositor
3. Open a window that is supposed to start maximized
4. Close it
5. Repeat steps 3 and 4 multiple times

MATE general version

1.24.0

Package version

1.24.0-1

Linux Distribution

Ubuntu MATE 20.04.2

Link to bugreport of your Distribution (requirement)

none

I have a second computer with the same version of Ubuntu MATE and the issue happens there as well.

First reported here, found out to be a bug with mate-netbook rather than Marco

Expected behaviour

CSD apps stay with their own decoration upon unmaximizing.

Actual behaviour

mate-netbook decorates them twice upon unmaximizing.

Steps to reproduce the behaviour

Start any CSD application maximized, then unmaximize it.

MATE general version

1.20.1

Package version

1.20.1-2ubuntu1

Linux Distribution

Ubuntu MATE 18.04.1 amd64
Also confirmed on LiveCD of the same distro, ruling out a configuration issue

Link to downstream report of your Distribution

None

The decoration also seems to come with a new border that is wide and transparent. The app in the background for instance is Discord and not anything Firefox.

Most distributions allow moving the window buttons (close,minimize,maximize) to the left side of the window. By allowing the close button (and any future buttons) to be placed to the left of the applet's title area or to the far left, before the icons, will make it more consistent to those who are always moving to the left corner of the screen to manage open windows. It is non practical to go the opposite way with a maximized window (without window decoration).

(And thanks to the developer(s), this applet is very useful.)

If i use mate-maximus and compiz like default windows manager, i have ~10 seconds pause after login (WM not loading). After pause, i have this message in ~/.xsession-errors:
mate-session[7531]: WARNING: Application 'mate-maximus-autostart.desktop' failed
After this, desktop and compiz work normally.

Workaround:
in /etc/xdg/autostart/mate-maximus-autostart.desktop comment line

X-MATE-Autostart-Phase=Desktop

In next time desktop (and compiz) loaded immediately.

to indicate what application is selected just move the title next to the icon so that the other icons are right and left of the title

So, I finally found out why the maximized windows on my test VM with MATE 1.9 are often show up without window decoration. The culprit is mate-maximus, which often removes window decorations from the maximized windows, even though this option is disabled by default.

This is reproducible in about 50-70% of cases, in both GTK+2 and GTK+3 builds of MATE. I was able to reproduce it with mate-terminal (auto-started because of the saved session), pluma and firefox.

The only way to stop this madness was to uncheck mate-maximus in the autostart apps dialog.

The default settings of mate-maximus clearly show that this behavior shouldn't occur:

Arch has updated MATE from 1.26.x to 1.28.x ; performing a post-upgrade QC of my system packages I find this sub-project is missing from the master deployment folder at https://pub.mate-desktop.org/releases/1.28/ hence Arch has no upgrade for it available.

In Arch, mate-netbook is a member of a meta-group mate-extra so this package gets installed as a dep; as a disclaimer I don't much know what this is used for and I don't think I use it on my system, however after noticing that this project was built for the 1.27.x dev branch/releases it's probably expected this should have been upgraded/included in 1.28.x? (meaning it's not deprecated, still active / useful for users?)

If this sub-project is considered deprecated with 1.28.x I'll file an issue upstream in Arch for it's removal, just looking for the correct next steps. Thanks!

Hello there. I am getting a bit slightly confusing results, so let me start with
what seems to work properly first:

• When I issue:

  mate-maximus --help

I almost instantly get this text result on the commandline:

Usage:
mate-maximus [OPTION?] - Maximus

Help Options:
-h, --help Show help options
--help-all Show all help options
--help-gtk Show GTK+ Options

Application Options:
-v, --version Prints the version number
-m, --no-maximize Do not automatically maximize every window
--display=DISPLAY X display to use

So far so fine. That seems to work as intended.

So now to things that don't quite seem to work as well.

Then I try to get the version, and when I do so, I get:

mate-maximus --version

libmozjs185.so.1.0: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/gio/modules/libgiolibproxy.so
no maximize: true

I think the first two lines can be ignored, but I kept it anyway (I think this is
unrelated, just glib/gio and libmozjs being confused about one another).

What I get from the above --version flag is this strange line called
"no maximize: true"

I am not sure if this should occur? But anyway, the window stays
where it is and nothing else is printed. I don't get the version
information from the commandline.

I am not currently running mate-desktop as I write this, I run fluxbox,
but in my opinion, the behaviour is quite straneg; this "no maximize: true"
part should never appear, I think. I only asked to query the --version,
so I would expect a version string such as 1.20.1 or something like
that. Note that other mate-desktop components behave like this,
so without knowing the code of mate-netbook, I believe it behaves
slightly differently.

I am not sure why nothing shows afterwards but I think some kind of
invisible widget may be started or something, since I also don't see
the cursor or anything after doing "mate-maximus --version". Very
strange.

I also tried mate-netbook 1.21.0 but when I try to run mate-maximus
with any option I only get a segfault.

I compile everything from source so I expect problems to happen,
but the behaviour is pretty awkward to me, and the other mate-desktop
components behave more or less correct (at the least from what I
can see). I may have some version mish-mash due to having both
components from 1.21.0 and 1.20.0 available here, but I am not
sure this could explain why mate-maximus would behave so strangely.

I would suggest that the code leading up to --version may be investigated
when someone may have a bit of time - I assume that it may be branching
off somewhere into that strange "no maximize: true" which I don't think
should possibly be shown ever.

GCC is version 8.1.0, binutils is latest git checkout etc... most is quite recent here,
except for glibc which is 2.23 from the latest slackware release.