Hi,
Am Sonntag, den 21.09.2014, 00:31 +0200 schrieb Sven Bartscher: > On Sun, 21 Sep 2014 00:19:42 +0200 > Joachim Breitner <nome...@debian.org> wrote: > > Am Samstag, den 20.09.2014, 22:35 +0200 schrieb Sven Bartscher: > > > To me this seems much like an upstream problem, since the problem just > > > seems to be that xmonad isn't prepared to run without > > > ~/.xmonad/xmonad.hs. I guess a proper fix would be to either let xmonad > > > create (and compile) a default configuration if it's missing or to run > > > with such a default configuration without writing it to a file, but > > > that's up to upstream. > > > > well, it used to be the case that xmonad would run happily without > > ~/.xmonad/xmonad.hs, and I’m surprised that it is not the case any more. > > Sven, did you reproduce the problem already? I didn’t find the time > > (which involves things like logging out :-)) yet. > > Yes I reproduced this (that's why I started to care about this bug). great, I wasn’t sure. > 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 So it must be one of our patches... Unfortunately, none of them look suspicious. Any ideas? Weird. 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
