Hi, Am Sonntag, den 21.09.2014, 11:33 +0200 schrieb Joachim Breitner: > > To reproduce this you don't need to log out. Just switch to a tty and > > run: > > $ xinit xmonad -- :1 > > (If you have more than one xserver running you might need to change > > the :1 to some higher number) > > True... > > But: The same using an unpatched xmonad works: > $ cabal unpack xmonad > $ cd xmonad-0.11 > $ cabal build > $ xinit $PWD/dist/build/xmonad/xmonad -- :1 >
More information: Without ./xmonad/, xmonad starts properly in both cases: You can e.g. fire up a terminal with Shift-Alt-Enter. But the system-wide installed xmonad will display the execution error using "xmessage", while the cabal-installed xmonad will print the same error on stderr (visible if you use xinit to start it). This is weird, as xmessage is (as far as I can tell from the code) only used when compilation fails, not when executing the xmonad binary. All very strange; anyone interested in digging deeper? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
