Comment 6 for bug 265353

Is there any help in the fact that the FILEBASE in dbdump of
9bca74e3a154f8b1bbbe14f59e98937be8e23660.db
 (the file that did not get dequeued below)
is not the filebase for itself but for the other file in the queue?

Since it appears that the file was not modified after being enqueued via
administrator approval, is there maybe a bug somewhere in the enqueueing
routines that wrote the wrong filebase?