Quote:
Originally Posted by cre84j
Have i been hacked?
|
(..)
Quote:
Originally Posted by cre84j
did my flatmate try and get my password when i was not around and my computer was on.
|
While a healthy dose of paranoia can be a Good Thing a warning like this does not automagically imply your machine was breached. So unless you're already suspicious of your flatmate because of earlier situations I would suggest you investigate and exhaust the purely technical side of things first.
Quote:
Originally Posted by cre84j
At boot this message came up and my system would not boot and also when i tried to boot through the grub in another safe mode option i could not log in and got the message wrong password or password not valid something like that.
|
Only exact error messages are useful. Jot it down, take a screen shot or use a (or your phone?) cam. In short:
be verbose and be specific. Also putting it like that it seems you system does boot further at times and this has not happened before you started "editing" your system from a different OS?
Quote:
Originally Posted by cre84j
I opened up a txt file yesterday
|
What text file? Be verbose and be specific as "
that txt file" can point to anything from "/etc/passwd" to "/home/cre84j/script.sh". The first one may cause trouble if lines are edited or removed
or saved with the wrong line-endings and the latter should not harm the system in a way it won't boot unless you execute it with elevated privileges.
If you search the 'net for this "GLib-WARNING **:getpwuid_r():failed due to unknown userid(0)" warning you will find several bugs related to Ubuntu. [
531027|
572279|
532984]. It does not seem to be hardware-related, for some people the system boots and for other it doesn't, it seems to be tied to the 10.x releases (some having no problem with the previous 9.x release), upgrading from 10.04 to 10.10 does not seem to work for some, some EeePC users report that rebooting helps to make it boot again and some
unconfirmed reports suggest that 'upgrade grub2' (or checking "UUID=" lines in GRUB configuration) or 'sudo fsck -a' or 'sudo apt-get remove plymouth' helps. I'd say these bug reports hold enough leads for you to try. Else you could try booting another Linux distribution (Live CD?) and see if that works for you.