Re: FVWM: A problem in FVWM quit abnormally.
On Thu, Dec 01, 2011 at 12:55:53PM -0500, des...@verizon.net wrote: Thomas Adam tho...@fvwm.org writes: I wouldn't bother with the Xorg logs myself either -- just concentrate on getting a corefile if FVWM really is crashing, which from your description, suggests it is. I'm curious Tom, what makes you think it's Fvwm and not X? Doesn't KDM gain control with either type of crash? Maybe -- I think it depends how the window manager is started, but I took the description of the problem to be FVWM's fault rather than X, and I've seen the same symptoms before where FVWM was involved but couldn't track the problem down so I'm hoping it is FVWM and not X. Personally, I don't use any kind of DM and use Xlogout to hold the session so I can easily tell what crashed. Yes, which is why I still find xconsole invaluable. :) -- Thomas Adam
Re: FVWM: A problem in FVWM quit abnormally.
Yes, which is why I still find xconsole invaluable. :) could you explain this sentence a little bit? :), i mean, how invaluable. when with gdb, is that mean i should start fvwm with a console rather than kdm. and for expecting the crash, should i start fvwm with gdb every time as you metioned above? -- Thomas Adam -- Liu An Institution of modern physics, Shanghai, China
Re: FVWM: A problem in FVWM quit abnormally.
source liu sourceo...@gmail.com writes: Yes, which is why I still find xconsole invaluable. :) could you explain this sentence a little bit? :), i mean, how invaluable. In most set ups, it's not easy to tell whether X has crashed or the window manager has crashed. You can use an application like xconsole to hold the session instead of the window manager so that you can tell the difference. It's not something for a beginning user through. To figure out whether X has crashed, take a look at /var/log/Xorg.0.log. See if you can find anything that indicates that it crashed. -- Dan Espen
