firefox --help lists a DISPLAY option. Start it from a console and set $DISPLAY elsewhere, even remote if thats what it takes ...
BillK On Fri, 2011-07-08 at 20:53 -0500, Dale wrote: > Mark Knecht wrote: > > > > You should continue to investigate the glibc thing. There was a thread > > about how it's causing problems for someone running LibreOffice I > > think. > > > > You might also look more at what part of Firefox s causing the lockup. > > Is it Firefox proper, or is it something caused by your homepage? For > > instance, if they make use of Flash or Java it could be one of them > > causing the lockup and not specifically Firefox itself. Can yo erase > > Firefox preferences so that it opes to a blank page. Does it still > > lock up. Have you removed all cookies, etc., to see if one of them is > > causing the problems. Since fluxbox doesn't crash as often you might > > work there to clean things up and then come back to KDE to see if it > > has helped. > > > > Consider an emerge -C on things you don't absolutely need, like Flash > > or whatever you're using, to figure out what's involved. Also, are you > > using Firefox 3 or 4? Consider trying the other. > > > > As with other apps, try running Firefox from a terminal and see if it > > throws any error messages. > > > > Good luck, > > Mark > > > > > > > > > I haven't been ignoring your suggestions but I did try them a bit ago. > It's in another reply. Thanks for the suggestions tho. > > As for trying to run from a terminal, if I do that, I can't see the > errors and when the kernel panics, I lose the messages. Sort of a catch > 22 here. Would be nice if I could tho. > > Thanks. > > Dale > > :-) :-) > -- William Kenworthy <bi...@iinet.net.au> Home in Perth!
