Closed Bug 342051 Opened 18 years ago Closed 16 years ago

RSS news delivery does not work in TB after Lightning install

Categories

(Calendar :: Lightning Only, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: digitrob, Assigned: mattwillis)

References

Details

(Keywords: regression)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4  - Build ID: 2006051612

TB RSS feeds account stopped operating ( it says it checks for news in the feeds but in fact it does not). It does not even connect to the URLs of the feeds.

Reproducible: Always

Steps to Reproduce:
1.Install latest nightly of Lightning
2.Click Receive button to get all new messages in TB or select just RSS subscriptions account
3. Mail delivery work but RSS news delivery does not



Expected Results:  
Lightning should not prevent TB from proper operation
I really don't think this is a Lightning issue.  Are there any errors in the Javascript console?
(In reply to comment #1)
> I really don't think this is a Lightning issue.  Are there any errors in the
> Javascript console?
> 

Yes here is what I get there:
----------
Error: Cannot modify properties of a WrappedNative = NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN
Source file: chrome://messenger-newsblog/content/Feed.js
Line: 124

Depends on: 325398
Confirmed with Thunderbird 1.5.0.4 and Lightning 0.1+ (20060620). The error happens in http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/mail/extensions/newsblog/content/Feed.js&rev=1.42.2.1.2.1&mark=159#157 
Removing xmlextras.dll from Lightning fixes that problem (not sure if it causes other problems)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Same error in TB 1.5.0.4 Extension Manager when looking for updates, at least on Windows. Seems that it cannot cope with the statically linked version of xmlextras in 1.5.0.4. Is it really (still) necessary for Lightning to come with an own xmlextras? Looking over calendar/lightning/Makefile.in, I am asking myself whether we can run into similar problems with storage and webdav. Opinions?
Hi 
Tried your workaround and it did not seem to work for me. I still have the same problem - cannot get RSS feeds messages. Also the status bar says Checking RSS items  and the progress bar keeps flashing.


(In reply to comment #3)
> Confirmed with Thunderbird 1.5.0.4 and Lightning 0.1+ (20060620). The error
> happens in
> http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/mail/extensions/newsblog/content/Feed.js&rev=1.42.2.1.2.1&mark=159#157 
> Removing xmlextras.dll from Lightning fixes that problem (not sure if it causes
> other problems)
> 

Flags: blocking0.3+
Keywords: regression
Assignee: nobody → mattwillis
Status: NEW → ASSIGNED
Attachment #228645 - Flags: first-review?
Attachment #228645 - Flags: first-review? → first-review?(mvl)
(In reply to comment #6)
Note that this charm depends on Bug 325398 that is filed long ago for that work.
*** Bug 344256 has been marked as a duplicate of this bug. ***
Comment on attachment 228645 [details] [diff] [review]
rev0 - removes xmlextras from lightning's makefile

r=mvl
Attachment #228645 - Flags: first-review?(mvl) → first-review+
patch checked in on MOZILLA_1_8_BRANCH and trunk

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
The problem seems to come back

Error: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIRDFService.GetDataSourceBlocking]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://messenger-newsblog/content/utils.js :: getItemsDS :: line 219"  data: no]
Source File: chrome://messenger-newsblog/content/utils.js
Line: 219
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I assume you don't use Thunderbird 1.5 and Lightning 0.1 anymore. Please report the exact version and build id of Thunderbird, Lightning you are using and the OS. In addition I assume that you don't see the issue fixed in 2006 but a new issue due to the different error.
According to the error message you might see Thunderbird Bug 369416, Bug 346736, Bug 301605 or Bug 322793.
Ropp, please report the details Stefan mentioned in comment#2, or we'll have to set this bug back to RESOLVED FIXED. Consider to file a new bug, and add a reference to your comment there, because re-opening bugs fixed years ago isn't desired.
Setting back to RESOLVED FIXED (see comment#14).
Status: REOPENED → RESOLVED
Closed: 18 years ago16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: