On Sun, 21 Sep 2014 12:29:33 +0200 Joachim Breitner <nome...@debian.org> wrote:
> 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). That's strange. Today I tried to reproduce this. It's now starting, but still showing the error message in xmessage. It behaves that way, no matter if .xmonad exists or not. I didn't try the unpatched version though. > 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? I guess I will have a look at in in the next days. But I'm not even sure what the problem really is. Jörg: Can you still reproduce this? If yes, how exactly? Do you start xmonad from a tty? Do you use startx or xinit? Do you use a login manager? Where is the resulting error message shown? Regards Sven
signature.asc
Description: PGP signature