> So, to add to the list of things that you can check: > > * Broken permissions (added or missing setuid or setgid) on any of > the CUPS binaries. > > * Invalid UID or GID of a named system account under which any of these > programs is executed, or a missing system account entry.
A comparison of the lists of setuid executables does not show any difference that is possibly relevant for cups ... > * Broken permissions on the /tmp directory (after mounting, if it's a > separate file system). > > * Invalid file system type or mount options on the /tmp file system, > if it's a separate file system. Both /tmp are tmpfs, owner root, group root, permissions drwxrwxrwt . Honestly, I am completely at my wit's end where this sh*t comes from ...
signature.asc
Description: This is a digitally signed message part
