Description of problem: Whenever I open a new tab. It opens and I am able to type in an address. After that I get an assertion failed message. Version-Release number of selected component (if applicable): Firefox version 3 beta 5 How reproducible: very Steps to Reproduce: 1. Open a new Tab 2. Type in an url 3. Hit enter 4. Get an assertion failed message Actual results: ASSERT: *** Search: _installLocation: engine has no file! Stack Trace: 0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037) 1:() 2:() 3:() 4:epsGetAttr([object Object],alias) 5:() 6:SRCH_SVC_getEngineByAlias(127.0.0.1) 7:getEngineByAlias(127.0.0.1) 8:getShortcutOrURI(127.0.0.1,[object Object]) 9:canonizeUrl([object KeyboardEvent],[object Object]) 10:handleURLBarCommand([object KeyboardEvent]) 11:anonymous(textentered,[object KeyboardEvent]) 12:fireEvent(textentered,[object KeyboardEvent]) 13:onTextEntered() 14:handleEnter(false) 15:onKeyPress([object KeyboardEvent]) 16:onxblkeypress([object KeyboardEvent]) Expected results: Additional info:
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. First of all, could we get output of the command rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* Please also install firefox-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install firefox Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
You can go ahead and close this report. Everything is worked out.