58936 - Helper Application not saved when add new types

Status: VERIFIED DUPLICATE of bug 50914

(SeaMonkey :: Preferences, defect, P2)

Description

[Xiaobin Lu]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
BuildID:    Netscape 6 PR3

I tried to add a new type in the helper application. Next time, when I gring up 
the helper application form preference menu, it is not there.

Reproducible: Always
Steps to Reproduce:
1.Go to Preference menu->Helper Application
2.Press New Type, add something in the four fields
3.Close it and bring up the Helper Application again, it is not there

Comment 1

[pmock]

Changing qa assign

Comment 2

[Anthony Baxter]

I'm also seeing this on Mozilla 2000112708 on Linux.

It appears to not be possible to enter a new helper application at all.

Comment 3

[Jean-Francois Ducarroz]

Nothing to do with Message compose!

Comment 4

[Viswanath Ramachandran]

nav triage: accepting for beta1. P2. paul chen. 

Comment 5

[shrirang khanzode]

Xiaobin, this works for me fine on 2001011104 trunk build. Can you please 
recheck ?Thx!

Comment 6

[Chuck Musser]

I'm seeing this in build ID 2001012208 for Linux as well. I tried adding a
handler for audio/x-pn-realaudio-plugin and when I clicked OK, the "New Type"
dialog didn't go away. The following message appeared in the console window:

JavaScript error: 
line 0: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIRDFContainer.Init]"  nsresult: "0x80004005
(NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://communicator/content/pref/overrideHandler.js :: anonymous :: line 242"
 data: no]

Even though, the handler never appears in the handler list, Mozilla seems to
remember it--clicking OK again results in a message that says: "Handler for
audio/x-pn-realaudio-plugin exists. Replace it?" Note that the handler doesn't
get invoked when I download content of that type--clicking on a RealAudio file
still results in the "You need a plugin for this MIME type" dialog.

Comment 7

[shrirang khanzode]

guys, pls use a new profile and try this, this should work fine. 5-6 months ago, 
this problem was introduced due to the change in  format for mimetypes.rdf. So 
any users who were using a old/migrated profile (which used the old rdf format 
would see this bug) . So the only workaround was to use a new profile and 
continue...
There are heaps of this same bug's duplicates floating around. I need to find 
them...humph...! Also, the bug that I was mentioning is bug 50914. Marking this 
as a dup of 50914. 

*** This bug has been marked as a duplicate of 50914 ***

Comment 8

[Pratik]

Is there any way I can keep the profile and get rid of the bug? If I were to
just delete mimetypes.rdf, would Mozilla recreate a new one? Better still if I
create a new profile nad just copy over the mimetypes.rdf file to my older
profile, would it work?

Comment 9

[shrirang khanzode]

Chek out racham's useful comments from bug 50914 that answer your questions -->
 "From [e-mail] 2000-10-11 16:30"

Comment 10

[Scott MacGregor]

yeah, try copying the mimetypes.rdf from a new profile into your current
profile. That should get around it. 

Comment 11

[Chuck Musser]

Yup, creating a new profile worked for me. 

Comment 12

[Xiaobin Lu]

   shrir:
      Yes ! 
      Using Mozilla 0.7 or current code in the trunk,it works for me now!

   Xiaobin Lu

Comment 13

[shrirang khanzode]

mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"