> What happens when you start it from a command line? Have you checked > to see if there is a lock file in .mozill~? Doesn't start does not > give enough info to really know what is or isn't happening.
What happens when I start it from the command line is the same as when I don't start it from the command line. It doesn't give _any_ information what so ever why it won't start. This is the output: /home/psycho 0 $ MozillaFirebird /home/psycho 11 $ Sure, it gives an error code of 11, but that doesn't make me understand more of why it died on me. When I remove my ~/.phoenix directory (moz-firebird don't use ~/.mozilla) it initializes ~/.phoenix and for a moment shows me a the base window before it dies. If I remove both ~/.phoenix _and_ /usr/lib/MozillaFirebird/chrome (as someone suggested) it initializes ~/.phoenix, but not the chrome directory and it doesn't show the base window as when only removing ~/.phoenix, it just dies. This is with both 0.7 (which worked yesterday) and 0.7-r1 which I upgraded to during the night. Now I have 0.7 installed again as I thought it was 0.7-r1 that was fubared, but it didn't help downgrading it it seems. Patrick B�rjesson -- Public key ID: 4C5AB0BF Public key available at wwwkeys.pgp.net
pgp00000.pgp
Description: PGP signature
