On Wed, Jul 6, 2011 at 9:01 PM, Dale <rdalek1...@gmail.com> wrote: <SNIP> > A little more info. After my last message, I opened Firefox. It locked up. > That runs as a regular user of course. So, I wanted to test a theory. I > logged into Fluxbox after my reboot. I opened Firefox and it locked up. > Nothing else was running. My first lock up in Fluxbox!! > > So, Firefox will lock up in BOTH KDE and Fluxbox. What do Konsole in KDE, > Fluxbox in both KDE and Fluxbox have in common? Keep in mind, Konsole > works fine in Fluxbox. > > I thought of something tho. I upgraded glibc a while back. I had some KDE > updates and a Firefox update just a little bit before this happened. Could > this be related somehow? > > Also, when Firefox locked up, I went to my old rig and tried to login to > this rig. The network connection was dead. So, that time at least, it was > a serious lock up. Sometimes the SysReq keys work, sometimes not. > > Thoughts? Anyone think of anything that could cause this? > > Dale > > :-) :-) > >
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
