[SOLVED]Windows not maximising with dual-monitors

NigelGreenway · 2016-02-24 14:48:24

I have recently moved to the bunsonlabs distro. I am really liking it apart from one issue...

I have an external monitor external monitor attached to my laptop (MacBook pro [2011 or 2013]) an when I try to toggle full screen on the top display.

Any ideas of what I need to do so I can fullscreen apps on either screen?

[solution]

It seems that tint2 caused the issues. After messing with the config, the main setting value that got it working was this part of the config:

# Panel
panel_monitor = 2 # this was originally set as `all`
panel_position = bottom center horizontal
panel_size = 100% 30
panel_margin = 0 0
panel_padding = 0 0 0
panel_dock = 0
wm_menu = 1
panel_layer = bottom
panel_background_id = 1

----------------
Moved from Help & Support (Other)

Last edited by damo (2016-02-25 16:11:00)

nobody · 2016-02-24 15:14:31

I'm not sure if I'm clear about what exactly the issue you're having is: Are you saying that when maximizing any application, regardless of whether that application's window was previously on the external or internal display, it will always be maximized on monitor HDMI1?

Also, please clarify if this is about maximizing the window -- that is, window decorations stay visible -- or entering fullscreen mode for the given application? That distinction is important because fullscreen is very different from just maximizing a window in X11. -- In this case, the problem would be that it is not possible to have two applications in fullscreen mode on each display?

NigelGreenway · 2016-02-24 15:47:46

Hi nobody,

sorry, not great at explaining things

So, I have an app, in this case it is terminal. Whilst that app is inside the HDMI1 output I click on `maximize`. Instead of maximizing to the full resolution of HDMI1, the application maximizes, but only within a certain height yet full width, inside HDMI1. (See image provided previously).

If I drag terminal to my laptop display LVDS1 and click on maximize, it will do so perfectly.

The bottom output is actually maximized without issues. (Chromium is maximized edge2edge on the bottom screen, the top screen starts from the bottom of the terminal upwards).

Does this help any further?

damo · 2016-02-24 17:10:47

@OP Can you confirm that you are using BunsenLabs - you have posted in Help&Support(Other)

Can you manually resize a window to full height and width?

If you add the following keybind (or whatever keys you want to try) to `rc.xml`, then do Openbox -> Reconfigure, does it work?

    <keybind key="C-A-m">
      <action name="ToggleMaximize"/>
    </keybind>

pvsage · 2016-02-24 23:54:41

@OP: You might also want to have a look at the Windows tab in OBConf.

NigelGreenway · 2016-02-25 08:46:01

Morning all,

So, I already have the following in my rc.xml, but as suggested by @damo I added the different keybinding but it still does the same, it maximizes to the bottom of that screen?

<keybind key="A-F6">
    <action name="ToggleMaximize"/>
</keybind>

@pvsage; my obconf looks like this. I will get a video showing what it does...

NigelGreenway · 2016-02-25 10:38:03

More tests reveal that it seems to be setting some sort of margin?

See here.

NigelGreenway · 2016-02-25 10:59:29

Could this be that the window manager is not dual screen aware?

xaos52 · 2016-02-25 11:06:29

See this thread for some options to try out.

NigelGreenway · 2016-02-25 11:31:10

Thank you, will have further play. I seem to have got it working where I use the following config:

xrandr \
	--output DP3 --off \
	--output DP2 --off \
	--output DP1 --off \
	--output HDMI3 --off \
	--output HDMI2 --off \
	--output HDMI1 --mode 1920x1080 --pos 0x0 --above LVDS1 \
	--output LVDS1 --mode 1280x800  --pos 344x1133 --below HDMI1 \
	--output VGA1 --off

But my ext monitor is above my laptop

NigelGreenway · 2016-02-25 11:38:04

It seems that if I use --output HDMI1 --mode 1920x1080 --pos 0x0 --right-of LVDS1, maximize works fine...

iMBeCil · 2016-02-25 11:49:20

^Could you please post output of

$ xrandr -q

with both monitors attached (and preferably switched on)?

Not that I guarantee the I will solve your problem, but I have certain ideas ...

xaos52 · 2016-02-25 12:41:23

In that case your xrandr should specify

	--output HDMI1 --mode 1920x1080 --pos 0x0 \
	--output LVDS1 --mode 1280x800  --below HDMI1\

NigelGreenway · 2016-02-25 13:58:59

Ok, so I have messed around with the settings you have provided. Here are some videos which *should* help get my issue across?

My screens with left:right as the setup:

My screens with top:bottom as the setup

It is when I open a new window or maximize a window that the issue presents itself.

Last edited by NigelGreenway (2016-02-25 13:59:44)

o9000 · 2016-02-25 14:31:58

Never use a panel (nor tint2, nor others) in the middle of the extended desktop. This is not supported by the WM specification (NetWM/EWMH); the behavior is undefined, which means that it might work partially, but with all kinds of strange side effects.

For one monitor on top of the other, your options are:
* use a vertical panel
* use a single horizontal instance of tint2 on the top edge of the top monitor
* use a single horizontal instance of tint2 on the bottom edge of the bottom monitor
* run 2 different instances of tint2, each with its own config file:
* one horizontal on the top edge of the top monitor
* the other horizontal on the bottom edge of the bottom monitor

xaos52 · 2016-02-25 14:48:54

Thank you, o9000.
@OP
I do get acceptable behaviour when using the window resize icon in the title bar in stead of double clicking on the title bar.

NigelGreenway · 2016-02-25 15:16:27

@o9000, thank you. If I could buy you a drink, I would.

That has solved the problem. I downloaded tint2wizard which is good too.

It has now been fixed and I can do some actual work

Again, a thousand thanks.

It has also opened up another thing to learn too.

damo · 2016-02-25 15:28:39

^ Good news

If you could edit the title of your first post and add [SOLVED]?

o9000 · 2016-02-25 16:21:38

You're welcome, Nigel.

Some further documentation on this issue:

* Related config option from tint2 (strut_policy): https://gitlab.com/o9000/tint2/wikis/Configure#panel
* Older bug report for tint2: https://gitlab.com/o9000/tint2/issues/481
* Bug report for KDE, active 2008-2012: https://bugs.kde.org/show_bug.cgi?id=167852 with a patch that was ignored https://bugs.kde.org/show_bug.cgi?id=167852#c55 because KDE5 was coming
* Bug report for KDE, active 2004-2012: https://bugs.kde.org/show_bug.cgi?id=94470 with comments from the devs that there are no plans to fix the spec since Wayland is coming https://bugs.kde.org/show_bug.cgi?id=94470#c57

The right thing to do here is change the WM so that it detects when space is reserved at the edge of a monitor but not at the edge of the extended desktop, and handle that corner case using the intuitive behavior instead of following the spec blindly.

I am planning to report a bug for Openbox soon.

Edit: I see that xfwm4 version 4.12.3 works fine.

Last edited by o9000 (2016-02-25 16:28:45)

o9000 · 2016-02-25 17:26:00

Follow-up: there is already a bug report for Openbox from 2009: https://bugzilla.icculus.org/show_bug.cgi?id=4332

It mentions a discussion on the WM specification mailing list https://www.freedesktop.org/wiki/Specif … s/wm-spec/

The discussion spans over several years and I could not find reliably all messages. Here is what I got:

I didn't go through all the material, but the most interesting message appears to be https://mail.gnome.org/archives/wm-spec … 00005.html
quote:

I have attached a suggested patch to the wm-spec to improve its
relation to multi-monitor environments.
...
I have extended the STRUT property to
allow for placing struts on boundaries between monitors. This
addresses the use case presented by Tomáš. To keep the property
similar to what has been done in the past, my proposed property looks
like this:
_NET_WM_STRUT_AREAS
...

The message was written by one of the openbox devs, suggesting fixing the specification. Unfortunately the latest specification still does not include this option.

#1 2016-02-24 14:48:24

[SOLVED]Windows not maximising with dual-monitors

#2 2016-02-24 15:14:31

Re: [SOLVED]Windows not maximising with dual-monitors

#3 2016-02-24 15:47:46

Re: [SOLVED]Windows not maximising with dual-monitors

#4 2016-02-24 17:10:47

Re: [SOLVED]Windows not maximising with dual-monitors

#5 2016-02-24 23:54:41

Re: [SOLVED]Windows not maximising with dual-monitors

#6 2016-02-25 08:46:01

Re: [SOLVED]Windows not maximising with dual-monitors

#7 2016-02-25 10:38:03

Re: [SOLVED]Windows not maximising with dual-monitors

#8 2016-02-25 10:59:29

Re: [SOLVED]Windows not maximising with dual-monitors

#9 2016-02-25 11:06:29

Re: [SOLVED]Windows not maximising with dual-monitors

#10 2016-02-25 11:31:10

Re: [SOLVED]Windows not maximising with dual-monitors

#11 2016-02-25 11:38:04

Re: [SOLVED]Windows not maximising with dual-monitors

#12 2016-02-25 11:49:20

Re: [SOLVED]Windows not maximising with dual-monitors

#13 2016-02-25 12:41:23

Re: [SOLVED]Windows not maximising with dual-monitors

#14 2016-02-25 13:58:59

Re: [SOLVED]Windows not maximising with dual-monitors

#15 2016-02-25 14:31:58

Re: [SOLVED]Windows not maximising with dual-monitors

#16 2016-02-25 14:48:54

Re: [SOLVED]Windows not maximising with dual-monitors

#17 2016-02-25 15:16:27

Re: [SOLVED]Windows not maximising with dual-monitors

#18 2016-02-25 15:28:39

Re: [SOLVED]Windows not maximising with dual-monitors

#19 2016-02-25 16:21:38

Re: [SOLVED]Windows not maximising with dual-monitors

#20 2016-02-25 17:26:00

Re: [SOLVED]Windows not maximising with dual-monitors

Board footer