You can edit your bookmarks manually .. press Ctrl+Shift+b then go to the All bookmarks > Bookmarks menu > recently bookmarked you can see all your bookmarks.

However try to resetting your firefox. Reset Firefox – easily fix most problems

Report us if any problem.

Thanks but I prefer to keep my add-ons. Is there any fix other than resetting Firefox?

Furthermore, I don't have a recently added bookmarks menu:

Screenshot: http://i.imgur.com/W7MOsEf.jpg

For osX go Cmd+Shift+b then go to the All bookmarks > Bookmarks menu > archive, now you can see all your bookmarks.

Does this also happen if you use the "Edit This Bookmark" item in the Bookmarks menu (Alt+B or press F10 to show the Menu bar)?

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

• Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
• Do NOT click the Reset button on the Safe Mode start window

• https://support.mozilla.org/kb/Safe+Mode
• https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

> Does this also happen if you use the "Edit This Bookmark" item in the Bookmarks menu (Alt+B or press F10 to show the Menu bar)?

Yes, the same.

I disabled my Zotero add-on [1] which resolved the issue.

I have no idea why Firefox Bookmarks is conflicting with Zotero.

Can someone confirm this issue by quickly installing and testing the add-on?

Thanks! [1] https://www.zotero.org/download/

Unless you are the same person who has reported this on the Zotero forums, there is exactly one other report of this (i.e. a conflict between the bookmarking functionality and Zotero) happening and this is on ArchLinux only and appears to be an issue with their build of Firefox. https://forums.zotero.org/discussion/40275/conflict-with-ff-32-bookmarking/#Item_7 It's probably best to follow this up with ArchLinux and potentially Zotero.

Yes, same person here.

I am still confused why this is an Arch-specific issue at all.

However, I now installed Firefox 33 Beta 6 and again the issue does not occur there...

For now I am not sure what to do about this except for sticking to the 33 Beta.