Alexandre Oliva wrote:
On Oct 7, 2003, "Mark Howell"
<mhowell(a)northlink.com> wrote:
>>I dont *think* I had this problem in beta1
I did, but I forgot to file it. I filed it for test2 the other day.
>If you don't see this in bugzilla and no one follows up saying "not a
bug"
>then by all means file it.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=106106
I had a problem with xterm being hosed awhile back. Uninstalling, then
reinstalling it did not do the trick. I found out that the error message
was correct and xterm was a directory, instead of an executable file. I
deleted the directory and was able to get the latest xterm rpm to install.
Additionally, there were a lot of files in the directory that were
executable, but had a . (dot) and number after them. I assume these were
filenames with the appended process id on them.
I don't know if the problem might be of similar origin. But it might be
caused by something along those lines.
Jim
--
Linux jcsevern 2.4.22-1.2087.nptl #1 Sat Oct 4 09:39:00 EDT 2003 i686
athlon i386 GNU/Linux