FVWM: [FVWM THEMES] Configuration Problem?
I use Debian Sarge as my OS and fvwm2 themes from fvwm-themes_0.7.0-1 as my XWindows Manager. Most of the time, my setup works very well. However there something very wrong with my fvwm2 configuration. Although fvwm2 offers both the Gnome Session Manager and the Gnome file manager (Nautilus) as options (which I used), at present: - fvwm2 + Nautilus causes a lock-up; - fvwm2 + Nautilus + Gnome Session Manager causes an unrecoverable crash. All will be gratefully received. Felix Karpfen -- Felix Karpfen
Re: FVWM: [FVWM THEMES] Configuration Problem?
On Mon, Nov 21, 2005 at 07:46:53AM +1100, Felix Karpfen wrote: > Most of the time, my setup works very well. I recall helping you set it up. :) > - fvwm2 + Nautilus causes a lock-up; > - fvwm2 + Nautilus + Gnome > Session Manager causes an unrecoverable crash. If it dumps a corefile, can you send us a backtrace via gdb? It ought to probably be sent to fvwm-workers. % gdb fvwm core (gdb) bt -- Thomas Adam -- I don't want to stay. I want to go home.
Re: FVWM: [FVWM THEMES] Configuration Problem?
On Wed, Nov 23, 2005 at 07:24:52AM +1100, Felix Karpfen wrote: > On Sun, 20 Nov 2005 21:13:09 +, Thomas Adam wrote > The root directory switched to "read-only" mode and the computer > could not be shut down cleanly. In fact it could only be shut down by > switching off the power. This is symptomatic of a much larger problem. Typically if this happens, it's because there's been a disk error, and that mount has remounted the partition in RO mode -- most recent distributions employ this methodology, that I have seen. > And after switching the power back, I had to run fsck manually to let > the computer clean up the mess - which took quite a time. And I lost > several of my few remaining hairs while biting my fingernails and > wondering whether the crash was beyond fsck's ability to fix. Fsck is very good at what it does, Felix. I usually find that running it four times consecutively helps. It really will try its best -- and if it can't fix your partition, you can generally be assured your hard disk is on the way out. Indeed, if you: tail -f /var/log/messages ... do you see any I/O errors? > I have never attempted to use a "corefile" but, from a very distant > memory, I believe it sits in /var/log/wtmp. Is that correct? Not necessarily. Usually corefiles are dumped in the CWD at the time of the crash. > While running fvwm2 with the Gnome Session Manager opened up > attractive new routines and possibilities, I think the price is too > high. In 5 years of Linux, I have never encountered crashes such as > the two crashes that I have managed to survive in the past few weeks. Check your logs -- these symptoms, as I say, sound like something on a much larger scale than just a software glitch in this instance. Session management within FVWM is very good. I've used it. I don't like it, but it works. :) -- Thomas Adam -- I'm brutal, honest, and afraid of you.
Re: FVWM: [FVWM THEMES] Configuration Problem?
On Sun, 20 Nov 2005 21:13:09 +, Thomas Adam wrote (<[EMAIL PROTECTED]>): > On Mon, Nov 21, 2005 at 07:46:53AM +1100, Felix Karpfen wrote: >> Most of the time, my setup works very well. > > I recall helping you set it up. :) > >> - fvwm2 + Nautilus causes a lock-up; >> - fvwm2 + Nautilus + Gnome >> Session Manager causes an unrecoverable crash. > > If it dumps a corefile, can you send us a backtrace via gdb? It ought > to probably be sent to fvwm-workers. The crash was really _very_ serious and I am not eager to repeat it. The root directory switched to "read-only" mode and the computer could not be shut down cleanly. In fact it could only be shut down by switching off the power. And after switching the power back, I had to run fsck manually to let the computer clean up the mess - which took quite a time. And I lost several of my few remaining hairs while biting my fingernails and wondering whether the crash was beyond fsck's ability to fix. I have never attempted to use a "corefile" but, from a very distant memory, I believe it sits in /var/log/wtmp. Is that correct? While running fvwm2 with the Gnome Session Manager opened up attractive new routines and possibilities, I think the price is too high. In 5 years of Linux, I have never encountered crashes such as the two crashes that I have managed to survive in the past few weeks. If there is no simple tweak to my existing fvwm2 configuration then then I would prefer to live without "session management" (as I did successfully for several years). To make my query more : "fvwm2 offers two "Theme Settings Screens" called "Theme Settings (form)" and "Themes Settings (gtk)". What documentation should I read to use these two screens intelligntly - assuming that the defaults need changing if I choose to use Nautilus and/or the Gnome session Manager. Felix Karpfen -- Felix Karpfen
Re: FVWM: [FVWM THEMES] Configuration Problem?
On 23 Nov 2005 07:24:52 +1100, Felix Karpfen wrote: > > The crash was really _very_ serious and I am not eager to repeat it. > > The root directory switched to "read-only" mode and the computer could > not be shut down cleanly. In fact it could only be shut down by > switching off the power. I can confirm, this usually means disk hardware error, unfortunately. > "fvwm-themes offers two "Theme Settings Screens" called "Theme Settings > (form)" and "Themes Settings (gtk)". Everything you may do using these forms may be also done from the menu. It is just faster when all options are concentrated in one place. > What documentation should I read to use these two screens intelligntly > - assuming that the defaults need changing if I choose to use Nautilus > and/or the Gnome session Manager. I am not sure whether you need this, but fvwm-themes FAQ discusses it. Regards, Mikhael.
Re: FVWM: [FVWM THEMES] Configuration Problem?
On Tue, 22 Nov 2005 20:46:16 +, Thomas Adam wrote (<[EMAIL PROTECTED]>): > On Wed, Nov 23, 2005 at 07:24:52AM +1100, Felix Karpfen wrote: >> The root directory switched to "read-only" mode and the computer could >> not be shut down cleanly. In fact it could only be shut down by >> switching off the power. > > Check your logs -- these symptoms, as I say, sound like something on a > much larger scale than just a software glitch in this instance. Firstly, my thanks for both responses. And, I fear, the (consensus) diagnosis is probably spot-on. I recently purchased a new computer and installed Linux myself (The vendor offered to install Windows - which I declined). Right at the start of the install Linux (Debian) asked if I wanted to check the HD for faulty Sectors. To which I foolishly said "No". It appears that I have maligned both fvwm2 and Gnome. And, if the problem is greater than faulty Sectors and cannot be fixed by fsck, then I had better invest in a second HD. The advice in the replies has helped to avoid total disaster. I am fairly conscientious about making backups. But I usually leave them on a separate partition of the HD; once every 3 months or so, I burn the backups onto a CD. It looks as though I need to do that much more frequently - while awaiting the arrival of the next crash. Felix Karpfen -- Felix Karpfen
Re: FVWM: [FVWM THEMES] Configuration Problem?
(Apologies for the OT nature, but for completness' sake, it should stay on-list) On Fri, Nov 25, 2005 at 07:29:05AM +1100, Felix Karpfen wrote: > Right at the start of the install Linux (Debian) asked if I wanted to > check the HD for faulty Sectors. To which I foolishly said "No". That's not necessarily a mistake per se, Felix. It's also conceivable these errors were realised sometime after install. But, in general, running badblocks (which is what that question was essentially asking) is the more prudent course of action. > It appears that I have maligned both fvwm2 and Gnome. And, if the > problem is greater than faulty Sectors and cannot be fixed by fsck, > then I had better invest in a second HD. Indeed. Given the HW symptoms, I'm more likely to make the assumption that these played a part in the errors you were receiving with FVWM and GNOME in this instance. If it does crash again, however, I would be very interested in seeing a backtrace from a corefile. > The advice in the replies has helped to avoid total disaster. I am > fairly conscientious about making backups. But I usually leave them > on a separate partition of the HD; once every 3 months or so, I burn This is perhaps OK in the short-term, but no so good in the long-term. What happens if one critical partition goes -- or a specific sector is beyond repair? That could have a knock-on effect in accessing the other partitions on that drive. > the backups onto a CD. It looks as though I need to do that much more > frequently - while awaiting the arrival of the next crash. *nods*. I also tend to (if you have the options) scp some of my important files as well, as a backup. As well as a CD backup, both locally stored here, and one remotely --- just in case. :) -- Thomas Adam -- I'm brutal, honest, and afraid of you.
