Closed Bug 508463 Opened 15 years ago Closed 15 years ago

Awesome Bar Stops Working after Surfing for a While

Categories

(Firefox :: Address Bar, defect)

3.5 Branch
x86_64
Linux
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 507269

People

(Reporter: cb47492, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090718 Firefox/2.0.0.11 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090718 Firefox/2.0.0.11 I regularly have the experience with 3.5.1 that the awesome bar just stops working after a while. That is, I type in the address bar and I get no drop down suggestions. If I close firefox and restart it the awesome bar starts working again. I never had this problem with 3.0.x. I'm not really sure what causes this to happen. Reproducible: Sometimes Steps to Reproduce: 1. Surf around for a while. Actual Results: Awesome bar stops working, more often than not. Expected Results: Awesome bar continues to work.
Sounds like a broken extension. Give this a try: http://support.mozilla.com/en-US/kb/Troubleshooting+extensions+and+themes Also, I suggest you fix your user agent. It's saying you have Gecko 1.9.1.1 (Firefox 3.5.1) in Firefox 2.0.0.11. You may have set something a while ago and left it that way. You can go to about:config via entering it into the address bar, entering useragent into the filter bar, then right-click->reset on anything that's bold. Probably not related to this issue, however.
Component: Toolbars → Location Bar and Autocomplete
QA Contact: toolbars → location.bar
Version: unspecified → 3.5 Branch
Thanks for the tip about my user agent. I reset it. And thanks for the thoughts about extension problems. I'll try to troubleshoot that and see if it solves the problem.
this is probably a dupe of bug 507269
(In reply to comment #3) > this is probably a dupe of bug 507269 Yes, it is!
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.