477473 - Download manager shows a error about "XML Parsing Error...." when opened

Status: RESOLVED WORKSFORME

(Toolkit :: Downloads API, defect)

Description

[sadat6396]

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

Today I had started a download, after sometime I paused the download. The next time I started Firefox and then I saw Mozilla Firefox was upgrading to 3.0.6. Every add-ons was compatible. All seemed well until I opened the download manager to resume my paused download and saw that it reported something about "XML Parsing error...." The exact error message is :

XML Parsing Error: no element found
Location: chrome://mozapps/content/downloads/downloads.xul
Line Number 86, Column 1:

I restarted Firefox and opened the download manager only to see the same result.

Reproducible: Didn't try

Comment 1

[Shawn Wilsher :sdwilsh]

In the past we've seen this caused by some add-ons.  Can you please try starting the browser in safe mode [1] and see if the problem goes away?  If it does, then one of your add-ons is causing the problem.

[1] http://support.mozilla.com/en-US/kb/Safe+Mode#How_to_start_Firefox_in_Safe_Mode

Comment 2

[sadat6396]

I tried in safe-mode, it shows the same annoying error.

Comment 3

[sadat6396]

wait. i had Java disabled (when the problem occurred), zotero disabled (i don't use it much, i keep it disabled almost all the time and it was disabled when the problem occurred) and only had Adblock Plus enabled. then opened firefox in safe-mode and wow, the problem was fixed. Then i opened it in normal-mode and saw no error. does this mean anything ?

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

I thought in comment 2 you had already tried safe mode and it was still showing the error?  Anyway, it sounds like this is working for you now, so I'm marking it as that; some add-on most likely caused this.