On Fri, Aug 30, 2013 at 11:13:32AM +0100, Stuart Henderson wrote: > On 2013/08/30 11:08, James Griffin wrote: > > I was just wondering if the Window Manager fvwm2 has been or is able to > > be used on the current snapshots post August 12, i.e. after the time_t > > changes. I tried it on a snapshot back on August 12/14 (something like > > that) and it crashed the X server. I haven't attempted it since. > > > > Would anyone happen to know if there is a problem with this particular > > Window Manager on the current snapshots? > > There hasn't been anything mentioned here yet, so it's probably not > known. Logs would be useful. Backtraces might be even better (if you > have X source installed, see /usr/xenocara/README's "How to get a > core file..." section). >
Well an X server built with 32 bits time_t would not start at all on a 64 bits time_t system. But 'fvwm2 crashes the X server' may be a wrong analysis. When the window manager itself crashes it's hard to tell the difference with a crash of the X server, especially if the window manager doesn't catch the signal. So if the fvwm2 package wasn't 64 bit time_t ready, it may be an explanation. But if a recent fvwm2 package really crashes the X server after a succesful start, it's probably another issue that definatly needs more attention : proper bug report with log files and such. -- Matthieu Herrb
