livemarks
livemarks copied to clipboard
nt1m
feed summary not updated
Feed URL https://www.kernel.org/feeds/kdist.xml
Add-on version 2.4.1
Describe the bug The feed display is not refreshed
To Reproduce Steps to reproduce the behavior: Display the feed
Expected behavior The display shall be updated. The workaround is to add the feed as a new livemark and remove the previous one, which is not convenient
I forgot to write that I was on debian/jessie 32-bits with firefox 68.3.0esr
Thanks for reporting! Was the livemark displayed in red on the settings page ? Also, does this happen regularly ?
On 30/12/2019 11:41, Tim Nguyen wrote:
Thanks for reporting! Was the livemark displayed in red on the settings page ? No Also, does this happen regularly ? Yes. The other feeds are correctly refreshed (for instance, https://www.bpifrance.fr/rss/feed/Runformation_Nouvelles_Bpifrance)
I can confirm this. I'm using LiveMarks to show any incoming email on my Gmail accnts and at least on my main accnt it won't update. Some of my other feeds update just fine though.
@TheOncomingStorm I think that could be #195 where the problem is that the feed becomes inaccessible because Google requires you to login again. Can you access the feed preview for the relevant gmail feed ?
Still not sure why https://www.kernel.org/feeds/kdist.xml is broken though...
If I have LiveMarks enabled it says "failed to fetch feed" but if I disable it, the feed shows without problem.
If I have LiveMarks enabled it says "failed to fetch feed" but if I disable it, the feed shows without problem.
@TheOncomingStorm Do you have the feed link so I can give it a look? Thanks :)
I think this is another issue with tracking protection or similar:
Request to access cookie or storage on “https://mail.google.com/mail/ca/u/0/feed/atom” was blocked because it came from a tracker and content blocking is enabled.
Is that something I need to change on my side? I don't really have content blocking enabled AFAIK.
Ok, so I found what was blocking it(stupid tracking setting I hadn't seen before) but now Livemarks still doesn't appear to be loading the feed. Any ideas?