New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Debian bug 1016365] liferea (sometimes) causes WebKitNetworkProcess crashes? to be logged #1130
Comments
I can reproduce those crashes when running on Wayland. When I open the websites/resources causing them with Epiphany I get the same crashes. Usually they are highly reproducible both in Liferea and Webkit. Rarely retrying the load helps. When running with an XOrg session both Epiphany and Liferea successfully load the pages. I fear the combination of WebkitGTK+Wayland is the root cause here. |
I can confirm the bug with liferea 1.13.5-3 (Debian stable) and liferea 1.14-RC1, both running on Debian stable with Xorg.
This happens whether liferea is configured to use the internal browser or an external browser. Meanwhile, liferea --debug-all shows:
(As a side note, the "handle URL" printing code, located in src/ui/liferea_browser.c, reads:
There are three %s in the format string but only two strings are given. This should be fixed)
|
@strigops-kakapo Thanks for hinting on the wrong format string. Fixed. |
This is a forward of a Debian bug I got reported today. I have to admit I couldn't reproduce it myself, but the reported has it on two different systems on two different versions of Debian (and hence
liferea
).So, this applies to both
liferea
1.13.5 and 1.13.8.Original report
When openning Liferea it logs these lines under /var/log/mesages, dmesg, journatlctl:
Note sure if this is normal or expected, but to my eyes looks like a trace or some kind of error.
I experience no visible/noticeable errors on the application and this log is also visible on Debian testing.
Followup info
Try by setting «Open links in Lifea's window» and click on a feed to load. This way I always get the above messages.
The text was updated successfully, but these errors were encountered: