On Sun, 21 Sep 2014 00:19:42 +0200
Joachim Breitner <nome...@debian.org> wrote:

> Hi,
> 
> 
> 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).
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)

> > We still need to keep in mind that, if upstream chooses to create a
> > standard configuration, xmonad needs to depend on libghc-xmonad-dev.
> > (Currently it just recommends it).
> 
> Upstream provides a standard configuration, it’s what’s compiled
> into /usr/bin/xmonad.
>
> > Joachim: Do you still think there is more info needed, or is the tag
> > just not removed?
> 
> We need to reproduce the problem first, and be sure that it is not
> Debian specific in any way.

Attachment: signature.asc
Description: PGP signature

Reply via email to