[Klug-general] Locked out!

[richarda]

Sorry Karl,
Trying to rely on my memory ( always a mistake) The message Actually
reads " (process: 5755): Gtk WARNING ** This process is currently
running setuid or setgid this is not a supported use of GTK*.
You must create a helper program instead
for further details http://www.gtk.org./setuid.html."
I looked at this page but could not see how it was relevant as it
discusses security issues
 Only noticed your solution after I started this email.
Have Regained Entry! but have also LEARNED a bit more not least the
importance of reporting  error messages accurately.
 Thanks for taking the time to explain a) how I broke it and b) how the
instructions to fix it operate.
Thanks too to Martin for rushing to my assistance on such feeble info.
 I really must stop experimenting on my "Best Machine" though Ididn't
think I was this time!
	Thanks again hope to see you at the ashford meet
regards R.
 
On Tue, 2008-04-15 at 10:09 -0400, Karl Lattimer wrote:
> 
> 
> On Tue, 15 Apr 2008 13:44:17 +0100, richarda <rich-ayres at tiscali.co.uk>
> wrote:
> > Hope there is some-out there who can help me, I have done something
> > really stupid. I was trying to save my 4 accounts to the same DVD.
> >  In order to do this I made the home directory root-owned with all
> > subdirecties likewise using -R option. Similarly changed all files and
> > folders to rw using chmod. When I loaded the files ready to burn the DVD
> > only the accounts were there. Returned each account to chmod 644 as
> > requested by log-in but still cannot log in. I can access all files and
> > folders from command line as root. The Desk top log tells me that gdk
> 
> gdk doesn't "start", it is a library for drawing graphics (gimp drawing
> kit). You're mis interpreting the error message here.
> 
> > refuses to start. Is this because home has the wrong permisions set?
> > If so could someone tell me the default values, or at worst how I can
> > save each account to a separate CD, preserving the current file
> > hierarchy ( the only instruction in my little book strings everything
> > out as individual files.
> >  Only I could cock up while making a backup. In case you're wondering
> > this message comes courtesy of my old pentium III
> >  Rich
> 
> OK this is how you broke it
> 
> 644 on a directory makes the directory useless, as it requires execute
> perms.
> 
> Instead try the following two commands,
> 
> find /home -type f -exec chmod 644 \{\} \;
> find /home -type d -exec chmod 755 \{\} \;
> 
> That will give all files 644 perms, and directories 755 perms.
> 
> This _should_ make it useful again.
> 
> K,
> 
> 
> > 
> > 
> > _______________________________________________
> > Kent mailing list
> > Kent at mailman.lug.org.uk
> > https://mailman.lug.org.uk/mailman/listinfo/kent
> 
> 
> _______________________________________________
> Kent mailing list
> Kent at mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/kent