Closed
Bug 813654
Opened 12 years ago
Closed 12 years ago
NS_ERROR_ILLEGAL_VALUE [nsINavBookmarksService.getItemType]
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
DUPLICATE
of bug 670069
People
(Reporter: klaus.kolle, Unassigned)
Details
Attachments
(1 file)
9.99 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121026114414 Steps to reproduce: I have been using Sync for long time now, but recently first one of my Firefox'es (running on Fedora 16) refused to sync. Today I discovered that another Firefox running on a Centos 6.something also refuses to sync. I tried to manually sync on both machines with no success. Actual results: Sync refuses to keep my Firefox up2date Expected results: My firefox should have been sync'ed
Comment 1•12 years ago
|
||
Can you please try this with Firefox 17 (released today) and let is know if that fixes it? We fixed a similar issue in 806460 and I'm hoping this is that issue.
Flags: needinfo?(klaus.kolle)
Summary: Cannot sync my Firefox'es → NS_ERROR_ILLEGAL_VALUE [nsINavBookmarksService.getItemType]
Reporter | ||
Comment 2•12 years ago
|
||
Gregory, thank you for your answer. I will try it, when its in the yum repository ready for my Fedora. |<
Flags: needinfo?(klaus.kolle)
Comment 3•12 years ago
|
||
I'm not sure how long it takes Fedora to roll out their packages. If you don't want to wait, you can download the "official" builds from https://www.mozilla.org/firefox/all.html.
Reporter | ||
Comment 4•12 years ago
|
||
I've downloaded v 17 from testing repo. Problem remains the same. Do you need any logs or otherwise from me, please do not hesitate to ask. Being a SW developer I can maybe gather information ordinary user cannot. |<
Comment 5•12 years ago
|
||
Pretty sure this is Bug 817445.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•