firefox wont run?

[Lord foff]

Well, i'm on dual boot, and the options i get are:

Ubuntu 8.04.3 LTS, Kernel 2.6.24-16-generic
Ubuntu 8.04.3 LTS, Kernel 2.6.24-16-generic (recovery mode)
Other operating systems:
Microsoft Windows XP Home Edition

And it was the fact that i hadn't opened firefox previous to the error message.

[Clownpie]

It looks like your current problem has nothing to do with your Firefox problem.

For your current problem you should try:

fsck -r

to try and repair your /dev/sbd3

If that works then once you are all booted I'd expect your Firefox problem to go away. I believe the reason Firefox wouldn't open before is there was a lock on Firefox(for some reason). The way you would have fixed this is to just remove the file ~/.mozilla/firefox/*.default/.parentlock

[Lord foff]

Took clownpie's advice, and it came up with:

fsck 1.40.8 (13-mar-2008)
e2fsck 1.40.8 (13-mar-2008
/dev/sbd1 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage.
Do you realy want to continue (y/n)?

Do i say yes?

[Clownpie]

Hrmm. Well, I'm no expert on fsck, but you should for sure search the forums for this. It is completely unrelated to your firefox problem. Sorry I can't be of more help right now.

[Lord foff]

Thanks for trying anyway


What's the worst that can happen if i say yes , i have an instillation disk ...

[Lord foff]

/dev/sbd1: recovering journal
fsck.ext3:group descriptors look bad... trying backup blocks...
resize inode not valid. recreate<y>? yes

/dev/sdb1 was not cleanly unmounted, check forced.
pass 1: checking inodes blocks, and sizes
reserve inode 3 (<The ACL data anode>) Has invalid mode. clear<y>? yes

reserved inode 4 (<The ACL data inode>) has invalid mode. clear<y>? yes

reserved inode 6 (<The undelete directory inode>) has invalid mode. clear<y>? yes

Inode 8, i_blocks is 0, should be 262416. fix<y>? yes

reserved inode 9 (< reserved inode 9>) has invalid mode. clear<y>? yes

reserved inode 10 (<reserved inode 10>) has invalid mode. clear<y>? yes

deleted inode 100705 has zero dtime. fix<y>? yes.

(lots of text which scrolled too fast)

clone multiply-claimed blocks<y>? yes.
... to be honest, from here i just held the y button...

[Lord foff]

after it had "fixed" everyhting,

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: ***** REBOOT LINUX *****
root@ben-desktop:~# reboot

[Lord foff]

When i entered my username and password, a message popped up:

Your home directory is listed as: '/home/ben' But it does not appear to exist. Do you wish to log in with the /(root) directory as your home directory? It is unlikely anything will work unless you use a failsafe session.

I clicked yes and got:

User's $home/.dmrc file is being ignored. This prevents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $home directory must be owned by user and not writable by others.

I clicked ok and got:

Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions if you can fix this problem

I click on and it goes back to the login screen

Tried loging in with failsafe gnome, does the same thing pretty much, i shall just reinstall it... I'll keep you updated.