New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

placement.lua "invalid object" #3

Open
stevenroose opened this Issue Nov 6, 2018 · 7 comments

Comments

Projects
None yet
2 participants
@stevenroose

stevenroose commented Nov 6, 2018

Yesterday I installed this plugin. (It's awesome, btw!!)

Today I got an error message an unexpected error occurred: [...]/awful/placement.lua: 119: [...?] invalid object

It's one of those red popups that go away when you click them (to try and select the text, f.e. :| ), so I don't remember it fully.

It happened when I move a fullscreen (Firefox) window from my larger external monitor to my smaller laptop monitor and back. But it's not reliably reproducable..

@Drauthius

This comment has been minimized.

Owner

Drauthius commented Nov 7, 2018

This plugin doesn't use the placement library directly, so I can't really say what's causing the error.

Which version of awesome are you using? Does it happen when you move the whole tag to another monitor, or when you move the window to another tag?

@stevenroose stevenroose changed the title from placement.lue "invalid object" to placement.lua "invalid object" Nov 8, 2018

@stevenroose

This comment has been minimized.

stevenroose commented Nov 8, 2018

When I move the tag to another monitor.

I also get the error consistently when I plug out a monitor and then go to a tag that was on the other monitor. The maximized windows will not be shown (even though the monitor is gone in xrandr as well), and when I unmax it, I get the error, remaxing bring the window in view.

@stevenroose

This comment has been minimized.

stevenroose commented Nov 8, 2018

It seems that maximized windows are not correctly moved when tag is moved to another monitor due to a monitor disconnecting.

@Drauthius

This comment has been minimized.

Owner

Drauthius commented Nov 13, 2018

I could (sort of) reproduce the problem you've seen. The error seems to come from within awesome, and seems to have been fixed in the master branch. But... even if the error has gone away, a maximized window isn't maximized correctly when a screen is unplugged and the tag is moved. I'm not sure why that is, and the things I've tried to do to get it to maximize properly haven't worked out. It seems like a maximized layout (instead of maximizing the program) doesn't have this problem.

So I think your best bet is to use a maximized layout instead, or try creating an issue in the awesome project: https://github.com/awesomeWM/awesome

@stevenroose

This comment has been minimized.

stevenroose commented Nov 13, 2018

@Drauthius what is a maximized layout? I use the default ones usually..

@Drauthius

This comment has been minimized.

Owner

Drauthius commented Nov 13, 2018

The maximized layout makes all the windows on that tag maximized. It should be part of the standard list of layouts that is cycled through when you press ModKey + Space. You can set it as the default for tags by adding layout = awful.layout.suit.max to your configuration when creating the tag list (as the example shows).

This is how I have my second tag set up (the one I called "www"). I then have a rule which places Firefox on that tag, but doesn't make it maximized since the tag layout will do that for me.

I'm not sure if this setup will work for you, but you could give it a try.

@stevenroose

This comment has been minimized.

stevenroose commented Nov 13, 2018

Hmm, well my workspace is a bit more complex. I have several tags with different layouts that hold a browser window either maximized or in a tile. But well, at least you're aware of it. I can just remaximize them when I unplug the screen :) Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment