292838 - Crash in bookmarks favorites converter due to folder name being too long

Status: RESOLVED EXPIRED

(Firefox :: Bookmarks & History, defect)

Description

[W Roberts]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Using the Bookmarks -> Favorites Converter -> Export command, a folder on the
local system was selected rather than a FF favorites folder. This was accepted
the first time and new Bookmarks do still get exported there regularly. However,
 when both attempting to use the Export command and on every exit of the FF
application, get the following two error messages:

1. Alert
Canceled cleaning up because the selected folder is not one of the Favorites
folders.

Clicking 'Ok' on this alert then brings up the following:
2. Alert
[Exception… “Component returned failure code: 0x80520011
(NS_ERROR_FILE_NAME_TOO_LONG) [nsIFileOutputStream.init]” nsresult: “0x80520011
(NS_ERROR_FILE_NAME_TOO_LONG)” location: “JS frame ::
chrome://booktofav/content/booktofav.js :: anonymous :: line 113” data: no]

In spite of re-install of FF version 1.0.1 and then subsequent upgrades to 1.0.2
and 1.0.3, the problem persists. During re-install or upgrade I have not however
deleted the profile.

Reproducible: Always

Steps to Reproduce:
1. Select Bookmarks -> Favorites Converter -> Export
2. Enter a folder and filename other than a FF favorites folder. Folder name was
set as 'Firefox bookmarks' including white space between the two words
3. Click ok. 
Any attempt to select Bookmarks -> Favorites Converter -> Export or exit the
application now re-produces the above errors

Actual Results:  
Accepted the folder and filename but then alerted that filename too long

Expected Results:  
Accepted the folder and filename specified or warned that file name is too long
but let the user modify it. There is now no way to modify so the error persists

Can not find reports in application event viewer

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.