On 19 Jun, wrote:
> went under KDE and used "find files" to locate any other "lame*" files
> that may have been missed. This included Gnome desktop references and
> KDE desktop references. (I do not recall a menu entry for LAME, but
> "find files" had listed something to that effect.) I then crossed my
LAME isn't responsible for these files, they are part of your
distribution.
> fingers and rebooted the machine . . . . . . . . . . . all started
> almost okay, except my heart stopped when it forced a check of files and
> then reported a "0.3% non-contiguous" and proceeded to continue to
> start. My KDE desktop was fine, but my Gnome desktop crashed. I
Hmmm... this sounds like one of:
- bug in the filesystem code (depending on the type of the filesystem,
I assume you use ext2fs or ext3fs: unlikely)
- hardware problems (RAM or harddisk cables, or harddisk itself), you
may get other strange errors sooner or later...
> at me anymore.) Clearly this may be a very isolated incident, I wish I
> had had the presence of mind to write down all the files I removed to
> help analyze this problem, but I did not. Can I reproduce this problem
> (someone is sure to ask this question?) I might be able too, but I do
> not want too.
Come on... wait until your wife prints the letter and then reinstall
LAME. If it works this time (and I assume it will work): everything is
fine; if not: you know how to fix it now.
Bye,
Alexander.
--
0 and 1. Now what could be so hard about that?
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
