Closed
Bug 382827
Opened 18 years ago
Closed 17 years ago
Error Message in Linux Terminal when adding an RSS Feed (NS_ERROR_NOT_AVAILABLE) [nsIAnnotationService.getItemAnnotationString]
Categories
(Firefox Graveyard :: RSS Discovery and Preview, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 3 beta1
People
(Reporter: cbook, Assigned: reed)
Details
(Keywords: regression, smoketest)
Attachments
(1 file, 2 obsolete files)
1.49 KB,
patch
|
reed
:
review+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a5pre) Gecko/20070601 Minefield/3.0a5pre ID:2007060104 [cairo] Linux Fedora FC 6
When i start the Trunk Build via Terminal in Linux and when i add a RSS Feed to this Build i get a error message at the Terminal:
*** siteURIString: undefined
*** getSiteURI failed: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIAnnotationService.getItemAnnotationString]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///opt/firefox/components/nsLivemarkService.js :: LS_getSiteURI :: line 935" data: no]
Reproduced with several different RSS Feeds (example heise.de Feed and planet.mozilla.org)
STR:
- start the Trunk build in Linux via a terminal
- add a rss feed of your choice and add this feed as example to your toolbar
- go to the terminal
- see the error message
The Error Console don`t display this error.
Flags: blocking-firefox3?
Updated•18 years ago
|
Component: General → RSS Discovery and Preview
QA Contact: general → rss.preview
Comment 1•18 years ago
|
||
Looks like this was added intentionally for bug 381894.
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/toolkit/components/places/src/nsLivemarkService.js&rev=1.16#303
Should LOG really be printing to stdout in normal builds?
Comment 2•18 years ago
|
||
(In reply to comment #1)
>
> Should LOG really be printing to stdout in normal builds?
>
No, good catch.
Updated•18 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Comment 3•18 years ago
|
||
Seth, if we still need these, can we dump to error console instead?
Assignee: nobody → sspitzer
Target Milestone: --- → Firefox 3 M8
Updated•18 years ago
|
Target Milestone: Firefox 3 M8 → Firefox 3 M9
Assignee | ||
Updated•17 years ago
|
Version: unspecified → Trunk
Assignee | ||
Comment 5•17 years ago
|
||
Change LOG() to Components.utils.reportError().
Would you prefer I just fix LOG() to use Cu.reportError() always, or leave it like it currently is?
Comment 6•17 years ago
|
||
Comment on attachment 284781 [details] [diff] [review]
patch - v1
Just remove this, it's valid for siteURI not to be set (as opposed to feedURI).
Attachment #284781 -
Flags: review?(sspitzer) → review-
Assignee | ||
Comment 7•17 years ago
|
||
Attachment #284781 -
Attachment is obsolete: true
Attachment #284782 -
Flags: review?(mano)
Comment 8•17 years ago
|
||
Comment on attachment 284782 [details] [diff] [review]
patch - v2
I would replace they try block with an hasItemAnnotation check. r=mano either way.
Attachment #284782 -
Flags: review?(mano) → review+
Assignee | ||
Comment 9•17 years ago
|
||
Attachment #284782 -
Attachment is obsolete: true
Attachment #284784 -
Flags: review+
Assignee | ||
Comment 10•17 years ago
|
||
Checking in toolkit/components/places/src/nsLivemarkService.js;
/cvsroot/mozilla/toolkit/components/places/src/nsLivemarkService.js,v <-- nsLivemarkService.js
new revision: 1.26; previous revision: 1.25
done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Summary: Error Message in Linux Terminal when adding an RSS Feed (NS_ERROR_NOT_AVAILABLE) [nsIAnnotationService.getItemAnnotationString → Error Message in Linux Terminal when adding an RSS Feed (NS_ERROR_NOT_AVAILABLE) [nsIAnnotationService.getItemAnnotationString]
Target Milestone: Firefox 3 M10 → Firefox 3 M9
Reporter | ||
Comment 11•17 years ago
|
||
verified fixed using Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b3pre) Gecko/2008010710 Minefield/3.0b3pre
Status: RESOLVED → VERIFIED
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•