On Thu, Jun 17, 2010 at 06:13:25PM +0200, Uli Schlachter wrote:
> > My config isn't super-elaborate, but it does have a bunch of includes
> > including some bits of my personal lua libraries. I doubt any of you want to
> > trace through all of that. So I'll pass this info on in the hopes it
> > might help. If you still need me to find a minimal change to the default
> > config which produces the problem, I'll try to track that down when I
> > have some free minutes.
>
> You are only having a single screen? If there are more than one, do they have
> the same size?
> Perhaps awesome is confused about what the actual screen size is (but I'd have
> expected more problems from that)...
Yes, single screen. Awesome correctly detects its size (geometry is
{x=0, y=0, height=768, width=1366}).
Funnily enough, running "client.focus:geometry(screen[1].geometry)" from
my Lua promptbox when the window is in the funny looks-like-floating state
makes it expand
to fullscreen, as it's supposed to.
> Also, which size is the trying-to-be-fullscreen terminal and how far off of
> the
> screen size is it? (xwininfo in a terminal and clicking on the window gets you
> accurate size information)
It doesn't seem to matter. I normally use the first .tile layout, and I
get this funny behavior regardless of whether the window in question is
the only client on the showing tag, or whether its a master or slave
when there are 2 or 3 clients showing... For example, here's the
xwininfo output when it's the master with 2 clients showing:
> xwininfo: Window id: 0x800009 "j...@vaio: ~/.awesome"
> Absolute upper-left X: 0
> Absolute upper-left Y: 24
> Relative upper-left X: 0
> Relative upper-left Y: 24
> Width: 676
> Height: 732
> Depth: 16
> Visual: 0x21
> Visual Class: TrueColor
> Border width: 2
> Class: InputOutput
> Colormap: 0x20 (installed)
> Bit Gravity State: ForgetGravity
> Window Gravity State: NorthWestGravity
> Backing Store State: NotUseful
> Save Under State: no
> Map State: IsViewable
> Override Redirect State: no
> Corners: +0+24 -686+24 -686-8 +0-8
> -geometry 84x52+0-8
I did manage to get a minimal rc.lua that will generate the error. With
the first bad commit I reported yesterday, apply this patch to the
default rc.lua and restart awesome, then try to fullscreen your window.
On my setup, it will behave in the funny way I'm describing.
--- rc.lua 2010-06-17 13:21:21.380339051 -0400
+++ rc-bad.lua 2010-06-17 13:31:59.399907687 -0400
@@ -26,7 +26,6 @@
-- Table of layouts to cover with awful.layout.inc, order matters.
layouts =
{
- awful.layout.suit.floating,
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
@@ -37,7 +36,8 @@
awful.layout.suit.spiral.dwindle,
awful.layout.suit.max,
awful.layout.suit.max.fullscreen,
- awful.layout.suit.magnifier
+ awful.layout.suit.magnifier,
+ awful.layout.suit.floating
}
-- }}}
Here are some details about my setup:
Linux vaio 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 11:32:37 CEST 2010 x86_64
Intel(R) Core(TM)2 Duo CPU U9600 @ 1.60GHz GenuineIntel GNU/Linux
X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH x86_64
Current Operating System: Linux vaio 2.6.33-ARCH #1 SMP PREEMPT Thu May 13
11:32:37 CEST 2010 x86_64
Kernel command line: root=/dev/group3/root
cryptdevices=/dev/md4:ext2,/dev/md3:crypt3,/dev/md2:crypt2 ro
resume=/dev/group2/swap 3
Build Date: 01 April 2010 05:28:33PM
Current version of pixman: 0.18.2
--
Jim Pryor
[email protected]
--
To unsubscribe, send mail to [email protected].
