[i3] layout file causes i3 to hang
I've got a layout file that cause i3 (version 4.8) to hang 100% consistently.
I use the i3-msg append_layout command to cause this. I've used it with other
layout files just fine.
What is it about this file that causes i3 to hang?
I've included the layout file below:
{
border: normal,
floating: auto_off,
floating_nodes: [
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29940496
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29940864,
last_split_layout: splith,
layout: splith,
name: #aa,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 170,
x: 0,
y: 0
},
id: 29940496,
last_split_layout: splith,
layout: splith,
name: Toolbox - Tool Options,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 164,
x: 753,
y: 95
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748871,
window_properties: {
class: Gimp,
instance: gimp,
title: Toolbox - Tool Options,
window_role: gimp-toolbox
},
window_rect: {
height: 820,
width: 160,
x: 2,
y: 0
},
workspace_layout: default
}
],
orientation: horizontal,
percent: null,
rect: {
height: 840,
width: 164,
x: 753,
y: 77
},
scratchpad_state: none,
swallows: [],
type: floating_con,
urgent: false,
window: null,
window_rect: {
height: 0,
width: 0,
x: 0,
y: 0
},
workspace_layout: default
},
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29637472
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29639104,
last_split_layout: splith,
layout: splith,
name: #ff,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 210,
x: 1679,
y: 0
},
id: 29637472,
last_split_layout: splith,
layout: splith,
name: Layers - Brushes,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 214,
x: 733,
y: 113
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748887,
window_properties: {
class: Gimp,
instance: gimp,
title: Layers - Brushes,
Re: [i3] layout file causes i3 to hang
Looking more closely. Its clear that the floating_nodes portion of my layout
is incorrect. Will fix by converting window_properties to swallows.
-Original Message-
From: Sargrad, Dave
Sent: Monday, September 29, 2014 9:01 AM
To: i3-discuss@i3.zekjur.net
Subject: layout file causes i3 to hang
I've got a layout file that cause i3 (version 4.8) to hang 100% consistently.
I use the i3-msg append_layout command to cause this. I've used it with other
layout files just fine.
What is it about this file that causes i3 to hang?
I've included the layout file below:
{
border: normal,
floating: auto_off,
floating_nodes: [
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29940496
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29940864,
last_split_layout: splith,
layout: splith,
name: #aa,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 170,
x: 0,
y: 0
},
id: 29940496,
last_split_layout: splith,
layout: splith,
name: Toolbox - Tool Options,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 164,
x: 753,
y: 95
},
scratchpad_state: none,
swallows: [],
type: con,
urgent: false,
window: 37748871,
window_properties: {
class: Gimp,
instance: gimp,
title: Toolbox - Tool Options,
window_role: gimp-toolbox
},
window_rect: {
height: 820,
width: 160,
x: 2,
y: 0
},
workspace_layout: default
}
],
orientation: horizontal,
percent: null,
rect: {
height: 840,
width: 164,
x: 753,
y: 77
},
scratchpad_state: none,
swallows: [],
type: floating_con,
urgent: false,
window: null,
window_rect: {
height: 0,
width: 0,
x: 0,
y: 0
},
workspace_layout: default
},
{
border: normal,
current_border_width: -1,
floating: auto_off,
floating_nodes: [],
focus: [
29637472
],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 0,
width: 0,
x: 0,
y: 0
},
id: 29639104,
last_split_layout: splith,
layout: splith,
name: #ff,
nodes: [
{
border: normal,
current_border_width: -1,
floating: user_on,
floating_nodes: [],
focus: [],
focused: false,
fullscreen_mode: 0,
geometry: {
height: 820,
width: 210,
x: 1679,
y: 0
},
id: 29637472,
last_split_layout: splith,
layout: splith,
name: Layers - Brushes,
nodes: [],
orientation: none,
percent: 1.0,
rect: {
height: 822,
width: 214,
x: 733,
y: 113
},
scratchpad_state: none,
swallows: [],
[i3] i3 does not swallow title correctly
I3 swallows the following just fine
class: ^Firefox$
But it wont swallow title as follows (notice in this case I don’t use anchors
since I want to match any title containing YouTube):
title: YouTube
I run firefox as follows
firefox -no-remote http://youtube.com
I've done other experiments with the title swallow spec, but I don’t have any
luck getting i3 to swallow the title.
The complete swallows spec that I'm using is:
swallows: [
{title: YouTube}
],
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
Re: [i3] i3 does not swallow title correctly
Xprop shows the following for the window that is not getting swallowed
correctly:
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x27b
bitmap id # of mask for icon: 0x27c
window id # of group leader: 0x201
WM_WINDOW_ROLE(STRING) = browser
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0x10, 0x0, 0x0, 0x0
_NET_WM_ICON(CARDINAL) =Icon (16 x 16):
âââ
ââ
ââ
â
âââ â
âââ â
âââ â
ââ
âââ
ââ
ââ
Icon (32 x 32):
ââ
â
â ââ â
ââ â
ââ
ââ
ââ
âââ
â
ââ
â
ââ
ââ
â
â â
âââ
âââ
ââ
â
âââ
ââ
ââ
Icon (48 x 48):
ââ
ââ
âââ â
âââ
â â ââ
ââ âââ â
â
ââ ââ ââ
âââ â
â
ââ
âââ
â ââ
âââ â ââ
âââ â ââ
âââ ââ
âââ ââ
âââ ââ
âââ ââ
ââ
ââ
âââ ââ
âââ â
ââ â
âââ
âââ
â
â
âââ
â
ââ
âââ
â
ââ
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 33554554
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x279
WM_CLIENT_LEADER(WINDOW): window id # 0x201
_NET_WM_PID(CARDINAL) = 8082
WM_LOCALE_NAME(STRING) = en_US.UTF-8
WM_CLIENT_MACHINE(STRING) = sensis-90025-2
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified minimum size: 300 by 71
program specified maximum size: 32767 by 32767
window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_N ET_WM_SYNC_REQUEST
Re: [i3] i3 does not swallow title correctly
Hi Dave,
Heuristic number one: If you have an issue with i3, and flash is
involved, it is not an issue with i3. Can you show the problem with
i3-sensible-terminal (specify which)?
Also, judging from your email address and disclaimer, you are probably
building some multimonitor drone control high precision WMD kill
interface. Just for your information, i3 is really not suited for
that. dwm is really more oriented towards those type of purposes.
Cheers,
Joep
On Mon, 29 Sep 2014 18:36:40 +
Sargrad, Dave dave.sarg...@saabsensis.com wrote:
Xprop shows the following for the window that is not getting
swallowed correctly:
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x27b
bitmap id # of mask for icon: 0x27c
window id # of group leader: 0x201
WM_WINDOW_ROLE(STRING) = browser
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0,
0x5, 0x0, 0x0, 0x0, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0, 0x0 _NET_WM_ICON(CARDINAL)
=Icon (16 x 16):
âââ
ââ
ââ
â
âââ â
âââ â
âââ â
ââ
âââ
ââ
ââ
Icon (32 x 32):
ââ
â
â ââ â
ââ â
ââ
ââ
ââ
âââ
â
ââ
â
ââ
ââ
â
â â
âââ
âââ
ââ
â
âââ
ââ
ââ
Icon (48 x 48):
ââ
ââ
âââ â
âââ
â â ââ
ââ âââ â
â
ââ ââ ââ
âââ â
â
ââ
âââ
â ââ
âââ â ââ
âââ â ââ
âââ ââ
âââ ââ
âââ ââ
âââ ââ
ââ
ââ
âââ ââ
âââ â
ââ â
âââ
âââ
â
â
âââ
â
ââ
âââ
â
ââ
Re: [i3] i3 swallows criteria
Hi Dave,
Heuristic number one: If you have an issue with i3, and flash is involved, it
is not an issue with i3. Can you show the problem with i3-sensible-terminal
(specify which)?
Also, judging from your email address and disclaimer, you are probably building
some multimonitor drone control high precision WMD kill interface. Just for
your information, i3 is really not suited for that. dwm is really more oriented
towards those type of purposes.
Cheers,
Joep
Joep,
Thanks for your response.
Relative to your thought about flash...
I am not using flash not sure how you came up with that. I am using i3 4.8
and trying to get it to swallow a firefox with a title spec. Having dug more, I
do think that this may be an issue with firefox (rather than i3). I've tried
the same with chromium-browser with greater success.
Relative to your second comment something about a WMD kill interface...
Huh?
-Original Message-
From: i3-discuss [mailto:i3-discuss-boun...@i3.zekjur.net] On Behalf Of
i3-discuss-requ...@i3.zekjur.net
Sent: Monday, September 29, 2014 3:44 PM
To: i3-discuss@i3.zekjur.net
Subject: i3-discuss Digest, Vol 53, Issue 17
Send i3-discuss mailing list submissions to
i3-discuss@i3.zekjur.net
To subscribe or unsubscribe via the World Wide Web, visit
http://infra.in.zekjur.net/cgi-bin/mailman/listinfo/i3-discuss
or, via email, send a message with subject or body 'help' to
i3-discuss-requ...@i3.zekjur.net
You can reach the person managing the list at
i3-discuss-ow...@i3.zekjur.net
When replying, please edit your Subject line so it is more specific than Re:
Contents of i3-discuss digest...
Today's Topics:
1. i3 does not swallow title correctly (Sargrad, Dave)
2. Re: i3 does not swallow title correctly (Sargrad, Dave)
3. Re: i3 does not swallow title correctly (Joep van Delft)
--
Message: 1
Date: Mon, 29 Sep 2014 18:24:11 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net
Subject: [i3] i3 does not swallow title correctly
Message-ID:
85ea6f68ac24da48b220ebea7a8c08b81b51a...@corpmail01.corp.sensis.com
Content-Type: text/plain; charset=utf-8
I3 swallows the following just fine
class: ^Firefox$
But it wont swallow title as follows (notice in this case I don’t use anchors
since I want to match any title containing YouTube):
title: YouTube
I run firefox as follows
firefox -no-remote http://youtube.com
I've done other experiments with the title swallow spec, but I don’t have any
luck getting i3 to swallow the title.
The complete swallows spec that I'm using is:
swallows: [
{title: YouTube}
],
-
This message is intended only for the addressee and may contain information
that is company confidential or privileged. Any technical data in this message
may be exported only in accordance with the U.S. International Traffic in Arms
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be
unlawful. If you are not the intended recipient, or the person responsible for
delivering to the intended recipient, you should not read, copy, disclose or
otherwise use this message. If you have received this email in error, please
delete it, and advise the sender immediately.
-
--
Message: 2
Date: Mon, 29 Sep 2014 18:36:40 +
From: Sargrad, Dave dave.sarg...@saabsensis.com
To: i3-discuss@i3.zekjur.net i3-discuss@i3.zekjur.net
Subject: Re: [i3] i3 does not swallow title correctly
Message-ID:
85ea6f68ac24da48b220ebea7a8c08b81b51a...@corpmail01.corp.sensis.com
Content-Type: text/plain; charset=utf-8
Xprop shows the following for the window that is not getting swallowed
correctly:
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x27b
bitmap id # of mask for icon: 0x27c
window id # of group leader: 0x201
WM_WINDOW_ROLE(STRING) = browser
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0x10, 0x0, 0x0, 0x0
_NET_WM_ICON(CARDINAL) =Icon (16 x 16):
âââ
ââ
ââ
â
âââ â
âââ â
âââ â
ââ
âââ
ââ
ââ
Icon (32 x 32):
Re: [i3] i3 does not swallow title correctly
Hi, you should really look at the i3 logs, as often windows change their titles and such *after* they are mapped and afaik firefox is a prime example of this. So the state of the window when you run Xprop is really no indication as to what you should put in your i3 config (as this is afaik applied during mapping, as this is the only sane thing to do). Best, Merovius PS: In the future, could you pretty please attach large logs as files, instead of pasting them inline?
Re: [i3] i3 swallows criteria
On 09/29, Sargrad, Dave wrote: Relative to your thought about flash... I am not using flash not sure how you came up with that. I am using i3 4.8 and trying to get it to swallow a firefox with a title spec. Having dug more, I do think that this may be an issue with firefox (rather than i3). I've tried the same with chromium-browser with greater success. You're trying to control a Firefox instance titled YouTube. Assuming Flash was involved wasn't much of a stretch. You say you've tried this with Chromium with greater succcess, which is to say incomplete success. What exactly are you trying to do? How has using Chromium gotten you close to that than using Firefox? It's always wise to explain what your end-goal is when asking someone for what you believe will be the answer. -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams
