Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have a vague feeling that when you first launch xmonad, it uses one executable+configuration, and then when you recompile, it finds the "right" one. In xmonad.desktop, try changing the <code>Exec=</code> line to include a full path to your xmonad.start.</p> <pre><code>Exec=/full/path/to/xmonad.start </code></pre> <p>Or you might try changing the last line in xmonad.start to include the full path to your xmonad executable.</p> <pre><code>dbus-launch --exit-with-session /full/path/to/xmonad </code></pre> <p>Another thing to try is changing the last two lines to:</p> <pre><code>exec xmonad #dbus-launch --exit-with-session xmonad </code></pre> <p>If any of these options change the behaviour you're seeing, that might give us a clue. </p> <hr> <p>EDIT: Let's try a different way of launching it, to see if we can learn anything. Don't start any window manager, log into a plain terminal instead. Type the command <code>xinit -- xmonad</code> or <code>xinit -- /full/path/to/xmonad</code>.</p> <p>Alternatively, create the file <code>.xinitrc</code> with one line in it:</p> <pre><code>xmonad </code></pre> <p>Then type the command <code>startx</code>.</p> <p>I also found this on the Xmonad FAQ, which may help:</p> <blockquote> <p>2.6 not found errors or changes to xmonad.hs won't take effect</p> <p>Ensure that ghc, and the xmonad executable are both in the environment PATH from which you start X. Alternatively symlink them to locations already in the PATH. ghc-pkg list should show ghc, xmonad, X11, etc. without brackets, e.g. {xmonad} is bad. ghc-pkg check will tell you if you have inconsistent dependencies or other registration problems.</p> <p>The mod-q action calls the xmonad binary to recompile itself, so if your display manager is starting it with /path/to/xmonad you'll also have to edit your xmonad.hs mod-q binding to use the full path and restart X (or in newer versions use 'xmonad --restart') to restart xmonad with the new mod-q full path binding.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload