On Sun, 2013-06-30 at 11:06 +0200, Michael Stapelberg wrote: > Hi Ian, > > Just FYI: > > I cannot act on the updated information you provided, since there still > is no log.
Understood. I figured it was better to give whatever information I had than nothing, I quite understand if this bug languishes until I manage to get some better logging. BTW I tried enabling logging but it failed (for reasons I can't recall) and since this is my work machine I didn't have much time to poke at it so ended up reverting the command line. I'm in the middle of setting up a fresh machine, so I will try again on that one. > Debugging an i3 problem without a log is a super-tedious thing which I > am not willing to do. Especially if it’s for an ancient version, such as > 4.2. Ancient or not it is the version in Wheezy, although I mostly track testing so I'm quite happy to upgrade. > Could you upgrade to 4.5.1? You can do that without logging out. Sure. > If you are willing to use the git version (see > http://i3wm.org/docs/repositories.html), you can even enable shared > memory logging without logging it (debug level will soon be adjustable > at run time, too). I think I'll wait for 4.6 for that functionality. Ian.
signature.asc
Description: This is a digitally signed message part
