Closed Bug 537587 Opened 15 years ago Closed 14 years ago

Firefox don't open page when songbird is running

Categories

(Firefox :: General, defect)

3.5 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: rdesgrange, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-2-25])

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fr; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; fr; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 After songbird is running firefox can't access to every webpages, he stop the loading or it don't loading. Reproducible: Always Steps to Reproduce: 1.Open Songbird 2.Open Firefox 3.try to access to a website other that google
If you open firefox in safe mode, or create a new profile (or both) does it happen? http://support.mozilla.com/en-US/kb/Safe+Mode http://support.mozilla.com/en-US/kb/Managing+profiles What error message do you see (If any), and have you checked your firewall settings. What version of songbird do you have, and does the page load as soon as you close songbird? This WFM with Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20100103 Minefield/3.7a1pre (.NET CLR 3.5.30729) ID:20100103050619
Version: unspecified → 3.5 Branch
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.