error starting up guile-wm
Closed this issue · 3 comments
olsonjeffery commented
jeff@mbp:~/src$ guile-wm
Backtrace:
In flow/event-loop.scm:
133: 19 [run-dispatch #<partial-continuation 2bb6900> (#)]
133: 18 [run-dispatch #<partial-continuation 2bbaae0> (#)]
133: 17 [run-dispatch #<partial-continuation 2bbec80> (#)]
133: 16 [run-dispatch #<partial-continuation 2bc5e20> (#)]
133: 15 [run-dispatch #<partial-continuation 2bc5100> (#)]
133: 14 [run-dispatch #<partial-continuation 2bca2c0> (#)]
133: 13 [run-dispatch #<partial-continuation 2bdb7c0> (#)]
133: 12 [run-dispatch #<partial-continuation 2be19c0> (#)]
133: 11 [run-dispatch #<partial-continuation 2be5cc0> (#)]
133: 10 [run-dispatch #<partial-continuation 2be9280> ((with-replies #))]
133: 9 [run-dispatch #<partial-continuation 2832700> ((with-replies #))]
133: 8 [run-dispatch #<partial-continuation 287e700> ((with-replies #))]
133: 7 [run-dispatch #<partial-continuation 2892ee0> (#)]
133: 6 [run-dispatch #<partial-continuation 289c5e0> ((with-replies #))]
In /usr/local/bin/guile-wm:
77: 5 [#<procedure 208c810 at /usr/local/bin/guile-wm:69:2 ()>]
In system/base/compile.scm:
252: 4 [compile (begin # #) #:from scheme ...]
180: 3 [lp (#<procedure objcode->value (x e opts)>) #<objcode 2af5020> ...]
In language/objcode/spec.scm:
31: 2 [objcode->value #<objcode 2af5020> #<directory (guile-wm user) 22201b0> ()]
In /home/jeff/.guile-wm:
42: 1 [#<procedure 2b07ea0 ()>]
In guile-wm/module/root-keymap.scm:
39: 0 [root-key-set! F20]
This appears to be the offending line in my .guile-wm
, as whenever i comment it out I can get guile-wm
to start up:
(set! (root-key) 'F20)
mwitmer commented
Have you mapped a key to F20 with xmodmap? This error would happen if X doesn't associate any key with F20.
shymega commented
@olsonjeffery - Did you manage to fix the backtrace with mapping the
key?
I found when I used guile-wm that I could comment out the line:
(set! (root-key) 'F20)
and use the C-t binding as the root key
instead. Perhaps that would work for you?
watkinsr commented
Perhaps we can close this issue?