HELP!!!!!

[gene heskett]

On Monday, November 22, 2010 12:34:36 pm Jon Piper did opine:

> Hi Everyone,
> 
> I'll jump in here eventhough I haven't followed the problem all the way
> through.  I have had this same problem many times. Every time I have
> changed distributions from SUSE, Mandrake, Mandriva, Fedora and some
> others to Kubuntu. Everytime it has not been a problem with the upgrade
> but with user permissions; the distributions listed above and some
> others start user ID at 1000 - Kubuntu begins at 500 so all of the
> permissions in the home directory are assigned to the root user. Of
> course that doesn't exist in Kubuntu (unless you change it).
> 
> The solution to the problem is to change all of the files in Home
> partition or folder to the user name.  This can be done entirely from
> Dolphin.
> This is how:
> 1) select the View menu,
> 2) Select "Adjust View Properties"
> 3) change View Mode to "Details", check "Show Hidden Files" then click
> "Additional Information",
> 4) check Permissions, Owner, and Groups and anything else you need (I
> mark them all). click "OK".
> 
> Now you can see what the situation is and correct it by Right clicking
> on a file or directory (folder).  Click the permissions tab. The user
> should be set to "Can View and Modify Content" and the group should be
> set to "Can View Content". Un-check "Executable" and change the User and
> Group to the name of the user and group who will be using the files. If
> you have checked a directory, check the box at the bottom, "Apply
> changes to all sub-folders and their contents". You are done if
> everything works correctly; sometimes you have to do this to directories
> that didn't change - that little problem has existed for 10 years that I
> can attest to in every KDE distribution I have used. You can do the same
> thing from the command line, but its more trouble.
> 
> Have good fun -- its a great adventure.
> 
> Blessing,
> 
> Jon Piper
> ***************
> 
> On 11/21/2010 09:16 PM, Doug wrote:
> > On 11/21/2010 08:08 PM, Jason E. High wrote:
> >> On 11/21/2010 07:57 PM, Bill vance wrote:
> >>> Howdy folks;
> >>> 
> >>> Having a few minor problems. I saw something yesterday that looked
> >>> like it might
> >>> 
> >>> work on the list, so I typed in:
> >>>      aptitrude update
> >>>      aptitude safe-upgrade
> >>> 
> >>> thinking that it hjad been long enough that various bug fixes etc.,
> >>> would have been
> >>> implemented.  While that seems to be the case with a couple things,
> >>> some things still didn't seem to want to install corectly.
> >>> 
> >>> Now however, kde is sending me numerous popup messages saying that
> >>> various of its config files are not writable.  trying, "chmod
> >>> a+rwxrwxrwx .kde/config/*", didn't work, and returned a message
> >>> that said It was a, "readonly file system".
> >>> 
> >>> Apparently something did that to all my hard drives, so now I have
> >>> to post from the Public Library.  The last time anything like this
> >>> happened, I wound up losing a
> >>> bunch of stuff for having to re-install the whole shebang.
> >>> 
> >>> So how do I cure my drives of this unasked for disease?
> >>> 
> >>> Bill
> >> 
> >> Check /etc/fstab to see if it's mounting your filesystem as
> >> read-only.
> > 
> > If you can't boot into the system, start a live disk and work from
> > there. --doug

Maybe I'm just a wee teeny bit old school here, but why use a file manager 
that was broken the last time I looked, when a calling up a terminal shell 
and "sudo chown thatuser:thatuser *" will do exactly the same?

Please don't make the 2 second job into half an hour's fiddling, its not a 
productive use of anyones time.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
polygon:
	Dead parrot.