This happened just recently because it worked perfectly a month ago.
Now a whole series of files come up and then it says permissions
fixed. After a while I went back to see if everything was corrected but
all the previous files appeared again. I also used cocktail with the same results. Should I ignore for the computer is working just fine

Post the log. Undoubtedly, someone here will be able to help. Depending upon the specific files, it may not be anything to worry about.

First take a look at this thread on the same subject and see if these aren't the same files you are having permissions issues with.

since I do not know how to show what was up in permissions. I just will tell you what I got; First there are 15 files listed, most of the is in system/library coreservices/front row (9) back row (1) raw camera(1)
applicatioms/itunes.app/contents/codeResources and itunes/framworks and resources
system/library/privateframeworks/ilifeMediaBrowser

I have the same thing happening. Joe suggested the right thread and I can confirm a similar behavior on my machine (MBP 17" 2.66 GHz, 4 GB RAM, OS 10.5.6). I never even opened any of these apps. Looks like Hal's suggestion about 10.5.7 is right...
Alex

A diagnosis backed up by biovizier @macosxhints as well.

It gets windozer and windozer...

This is a behavior that has recurred several times in OS X since the very beginning. There have been lots of explanations about what is actually going on but the solution in every case has been to wait until Apple fixes this in the next release and in the meantime don't worry about it. AFIK most of Apple's fixes have involved modifying either the GUI or the underlying Unix command to suppress reporting the particular "messages". In other words the condition is still there and it is still meaningless and unimportant so we simply won't tell you about it any more. In some cases it is a result of errors in the Receipt package for the particular application or update but to the best of my knowledge the major problem created by any or all of these has been the inevitable spate of anxious inquiries on this and other Apple oriented forums asking what to do.

Hal's link is very informative showing some haste from Apple without due diligence; on the other hand the problem is not critical. I agree with you that we have to wait for an update and in the meantime not get alarmed at all these repairs. I also noticed that, compared to Tiger, DU in 10.5 reads from permissions database (this step in Tiger was not shown) and this read is very long even on very fast machines. Is that because the OS is more complex?
Alex

> I also noticed that, compared to Tiger, DU in 10.5 reads from permissions database (this step in Tiger was not shown) and this read is very long even on very fast machines.

I'm not certain what "very long" means to you; by way of example, my 1.33GHz iBook took 21 minutes to repair Leopard perms, and my 2.0GHz Macbook has gotten that down to about 5 minutes.

> Is that because the OS is more complex?

Again, I'm not certain, but it may have something to do with the new "boms" receipts format.