search

BurntSushi / wingo

A fully-featured window manager written in Go.
Do What The F*ck You Want To Public License
1k stars 86 forks source link

wingo --replace cannot replace 'awesome' wm #88

Open dlintw opened 11 years ago

dlintw commented 11 years ago

I was in awesome wm.

wingo --replace

shows it can not access the 'root window'

BurntSushi commented 11 years ago

Can you paste the full output of wingo --replace please?

dlintw commented 11 years ago

WINGO WARNING: config_theme_setters.go:167: Could not load './data/close.png' as a png image because: open ./data/close.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/close.png' as a png image because: open ./data/close.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/maximize.png' as a png image because: open ./data/maximize.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/maximize.png' as a png image because: open ./data/maximize.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/minimize.png' as a png image because: open ./data/minimize.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/minimize.png' as a png image because: open ./data/minimize.png: no such file or directory WINGO WARNING: config_theme_setters.go:167: Could not load './data/wingo.png' as a png image because: open ./data/wingo.png: no such file or directory WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-space': Got a bad access error when trying to bind 'Mod4-space'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-return': Got a bad access error when trying to bind 'Mod4-return'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-Shift-l': Got a bad access error when trying to bind 'Mod4-Shift-l'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-left': Got a bad access error when trying to bind 'Mod4-left'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-x': Got a bad access error when trying to bind 'Mod4-x'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-Shift-h': Got a bad access error when trying to bind 'Mod4-Shift-h'. This usually means another client has already grabbed this keybinding. WINGO WARNING: bindings_key.go:77: Could not bind 'Mod4-right': Got a bad access error when trying to bind 'Mod4-right'. This usually means another client has already grabbed this keybinding. WINGO ERROR: root.go:34: Could not listen to Root window events: BadAccess {NiceName: Access, Sequence: 766, BadValue: 143, MinorOpcode: 0, MajorOpcode: 2}

BurntSushi commented 11 years ago

OK. To me, that output means that awesome isn't giving up control. Which means either Wingo or awesome has a bug in adhering to the protocol governing WM ownership transfer. My guess is that the bug is in Wingo, but I'll need to spend time replicating first. Not sure when I'll get to it...