Closed Bug 539359 Opened 15 years ago Closed 13 years ago

Add a keyword for this search gives stack trace, old keywords no longer work, and window sized wrong

Categories

(Firefox :: Bookmarks & History, defect)

3.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: davidscottcohen, Unassigned)

Details

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

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.15) Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15

I have some searches set up with keywords using "add a keyword for this search" (for example, "w" to search my company's internal wiki).  Recently, all the saved keywords I had stopped working.  When I look them up in "organize bookmarks", there is no mention of the saved keyword.  When I tried to re-create one, I got lots of stack traces, like this one when I try to pick what folder to put the bookmark in (even though all of the options are blank):
ASSERT: Invalid menuitem in the folders-menulist
Stack Trace:
0:BPP__getFolderIdFromMenuList()
1:BPP_onMenuListFolderSelect()
2:oncommand([object XULCommandEvent])

And this one when I click OK:
ASSERT: Invalid menuitem in the folders-menulist
Stack Trace: 
0:BPP__getFolderIdFromMenuList()
1:BPP__getInsertionPointDetails()
2:BPP__getCreateItemTransaction()
3:BPP_onDialogAccept()
4:anonymous([object Event])
5:_fireButtonEvent(accept)
6:_doButtonCommand(accept)
7:_handleButtonCommand([object XULCommandEvent])



Reproducible: Always

Steps to Reproduce:
1.  Pick a site with a keyword you want to set for a search.
2.  Try and set it. 

Actual Results:  
Stack traces (copied from above):
When I tried to re-create one, I got lots of stack traces, like this one when I try to pick what folder to put the bookmark in (even though all of the options are blank):
ASSERT: Invalid menuitem in the folders-menulist
Stack Trace:
0:BPP__getFolderIdFromMenuList()
1:BPP_onMenuListFolderSelect()
2:oncommand([object XULCommandEvent])

And this one when I click OK:
ASSERT: Invalid menuitem in the folders-menulist
Stack Trace: 
0:BPP__getFolderIdFromMenuList()
1:BPP__getInsertionPointDetails()
2:BPP__getCreateItemTransaction()
3:BPP_onDialogAccept()
4:anonymous([object Event])
5:_fireButtonEvent(accept)
6:_doButtonCommand(accept)
7:_handleButtonCommand([object XULCommandEvent])



Expected Results:  
I should be able to set a keyword for a search.  Moreover, my old ones should not have been deleted.

I also have a windows box running firefox where everything works.  I have the same keywords set for the same searches.
i have to point out that you're using a pretty old (ancient) version of Firefox, we have fixed lots of bugs about bookmarking, and this could just be due to an old bug.

Also ensure that it is not caused by an add-on, trying in Safe mode (http://support.mozilla.com/kb/Safe+Mode)

For the most part looks like your bookmarks got corrupted, try creating a new profile and restoring your bookmarks from a bookmarks.html or a JSON backup (you should be able to export them from the Library in the old profile, or looking at the bookmarksBackup folder in profile)
See http://support.mozilla.com/kb/Lost+Bookmarks
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]
Version: unspecified → 3.0 Branch
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: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.