Ubuntu
firefox-3.0 package

problem with history and bookmark storage and retrieval

Bug #307476 reported by chinmayisk on 2008-12-12

This bug report is a duplicate of: Bug #241609: Firefox 3 bookmarks lost after unclean shutdown. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	firefox-3.0 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: firefox-3.0

back and front navigation keys dont work and bookmarks are not saved and also displaye
apart from that history is not stored and help crashes the browser
this.bookmarks is undefined
file:///usr/lib/xulrunner-1.9.0.1/modules/utils.js
line 884
[Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: file:///usr/lib/xulrunner-1.9.0.1/components/nsLivemarkService.js :: anonymous :: line 500" data: no]
file:///usr/lib/xulrunner-1.9.0.1/components/nsLivemarkService.js
Line 500

might be the reasons

ProblemType: Bug
Architecture: i386
Date: Fri Dec 12 21:47:50 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelModules: fglrx
Package: firefox-3.0 3.0.1+build1+nobinonly-0ubuntu0.8.04.3
PackageArchitecture: i386
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_IN
SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-19-generic i686

Tags:

Revision history for this message

chinmayisk (chinmayisk) wrote on 2008-12-12:

Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
ExtensionSummary.txt Edit (1.1 KiB, text/plain; charset="utf-8")
profiles.ini.txt Edit (94 bytes, text/plain; charset="utf-8")

Revision history for this message

drew212 (mstngdrew212) wrote on 2009-09-13:

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 241609, 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.