Firefox-3.0.7 'freezes' when trying to organize bookmarks

[Roberto Caro]

Binary package hint: firefox-3.0

Using: Firefox Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009030422 Ubuntu/8.10 (intrepid) Firefox/3.0.7 [info gotten from: Help / About Mozilla Firefox]

Problem is related to "bookmarks", and it seems that is related to the QUANTITY of folders / bookmarks created and when trying to organize them without the use of 'Organize Bookmark' option.

Description:
.I have many folders with bookmarks, they fill the entire screen and I glide the pointer on the 'little' arrow at the bottom of the screen, so the menu list of bookmarks scrolls up/down to get to the bookmarks I have way at the bottom.
.I discovered that I don't have to use the 'Organize Bookmarks' option for deleting, moving up/down, moving into folders, the bookmarks. So, I started deleting, dragging up/down, and dragging into folders, the bookmarks. This worked fine until the list of bookmarks must have reached a threshold in quantity, that whenever I 'drag' a bookmark to put it into a folder or to another place, the entire screen freezes; however, I can move the pointer which is different from the regular arrow, but nothing else works: can't change to another workspace, can't get to a terminal session, menus - including System- don't work.

The only way to get control back is to turn computer off and back on.

If you need more info, my email is: <email address hidden>, I check email regularly. I'm on PDT.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0.7+nobinonly-0ubuntu0.8.10.1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.27-11-generic i686

[drew212 (mstngdrew212)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 238542 , so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.