527196 - Firefox doesn't know how to open this address, because the protocol (lastfm) isn't associated with any program.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Harold Walker El Bey]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)

Every time I log on to last.fm and attempt to play from my library, I get this message:

Firefox doesn't know how to open this address, because the protocol (lastfm) isn't associated with any program.

Reproducible: Always

Steps to Reproduce:
1. I log in to my account at last.fm
2. I choose a play list from my library.
3. I get the following message:  Firefox doesn't know how to open this address, because the protocol (lastfm) isn't associated with any program.
Actual Results:  
I cannot play music at the last.fm website

Expected Results:  
Play music as before.  


This problem began earlier this week.

Comment 1

[Matthias Versen [:Matti]]

And what did the lastfm people told you about the issue ?
Why DO you think that this is a browser issue ?
It looks like they are calling an external protocol handler lastfm://

I can not see why this should be a browser issue at all

Comment 2

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? 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

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.