I am well aware of what files are assigned to whom and when, and system
should NEVER! be a assigned to a "user" other than one that is a
ie. in Ubuntu, etc. one that is below 1000 gid/uid.
The user in question is a shell user account set up for SAMBA access to
my local printer "ONLY".
This permissions error happened during the initial install, outside of
the normal sudo or kdesu
used for package installation or system maintenance.
Outside of that, when you log in as sudo in a term, or kdesu for gui
the system should "NOT" reassign the permissions on files in the users
to root! or any other user for that matter.
This is a bug specific to this distro and needs to be looked at.
And during a boot-up fs check the lost inodes etc. end up in
/var/log/fsck after a brief visit to
"swap" if they are too large for the ram disk, and they are owned by root,
and "only" after fsck is finished and the volume mounted for read/write,
and "if" they are keep-able files. Because the volume in question is
not mounted and files cannot be written to it outside of repairs to the
Generally Lost+Found as you prefer is for intact files that the system
has no idea
where else they should go, either because their descriptor is messed up
or they are
configure incorrectly, ie. screwed up menu and *.directory files.
On 10/14/2010 06:37 AM, email@example.com wrote:
> > home directory and cache files in /var to root, this rendered my desktop
> > unusable until I logged out and reset the ownership to myself via the
> > recovery console.
> Are they files you created while sudo'd? Files are owned by whomever
> creates them, including root. And which was it, by the way? You just
> described the exact reason that one should NEVER use sudo with
> graphical apps.
> > It also assigned portions of the /home and /usr directory to another
> > such as lost&found and trash, and some of the other KDE files in
> > and /usr/share. (This is a BIG!! problem).
> lost+found you mean? That's where files move when your filesystem gets
> screwed up in a semi-recoverable way. For example, if you power off
> (not a prpoer shutdown) the machine while those files are in use, the
> filesyste becomes inconsistent. When you boot, a fsck will run and say
> it found orphaned inodes. That means it found remnants of files with
> no record of where they should be in the filesystem. It stores these
> in lost+found for you to sort through and put back where they belong.
> > Could this be associated with
> > the pulseaudio business?
> Doubt it.
> Mackenzie Morgan
kubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel