Dear Maintainer, I believe there is an issue where the GNOME/Wayland session crashes completely and forces a logout shortly after starting Liferea with the tray-icon plugin enabled. Steps to reproduce: 1. Use Debian 13 (Trixie) with GNOME under a Wayland session. 2. Install 'liferea' 3. Enable the "Tray Icon" plugin inside Liferea. 4. After a short period of usage or background activity, the entire desktop environment crashes and returns to the GDM login screen. Root cause analysis: The plugin utilizes the deprecated 'libayatana-appindicator' library, which seems to cause a memory/object reference failure under Wayland, leading to a broken display pipe that kills the compositor. Here are the relevant journalctl logs leading to the crash: liferea[35320]: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. liferea[35320]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed net.sourceforge.liferea[35320]: <sys>:0: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed liferea[35320]: Error flushing display: Broken pipe Unfortunately without the tray-icon liferea is not usable for me because I prefer my feed client to be running all the time in background. I also tried with Ubuntu AppIndicators extension without success, so at the moment I don't have a workaround besides trying another alternative. Thank you for maintaining liferea and for your help with this issue! Best regards,
Hi Fierro, Thanks for your report. Somehow I missed it when you submitted it. I have forwarded the issue to upstream. Let's see if they can and want to help fix the stable version. Paul
Hi, I interpret upstreams comment on the bug as saying he doesn't support the version we have in stable. Which means somebody else than upstream needs to debug this and generate a patch. I don't have enough C skills that I'll embark on that endeavor. While backports isn't supposed to be used to fix bugs, as the last version of liferea uses different frameworks under the hood and has been changed quite a bit, I think it's justified to provide a backports version of it (haven't checked how feasible that is). Would that help you out of the woods? Paul
The trayicon in pre-2.0 Liferea is written almost entirely in python [1]. If an alternative tray implementation has python bindings available, trayicon.py could be patched to use those. In 2.0 Liferea has moved to libstray [2] to create an icon via D-Bus API. While that could potentially be backported, it might be easier to backport Liferea 2.0 to trixie. I managed to backport Liferea 2.0 to trixie while working to fix various upstream issues. It was not too difficult. I had to change the libadwaita-1 version to 1.7 to match trixie. Upstream sets to 1.9 but 1.7 seems to work. I also had to revert the move to girepository-2.0, as the version in trixie is too old. There may be a better way to fix that, but reverting was quickest. gobject-introspection-1.0 still works with latest Liferea, though that could change at any point. [1] https://github.com/lwindolf/liferea/blob/master/plugins/trayicon.py [2] https://github.com/charlesrocket/libstray/
Hi Matt, I don't think the difference between the version of liferea in stable and version 2.0 meet the requirements for a stable update. As said, a backport to debian-backports might be an option. Interesting, can you share that as a diff? A bunch of the changes in that area in Debian were done because we wanted to move forward with the pygobject transition. Basically the changes that went into release 1.16.1+ds-2.1. Ack Paul
Patch attached. I haven't noticed any issues by lowering the dependency on libadwaita to 1.7; not sure if there was a reason it was set to that other than that was the version installed on the maintainer's machine. The girepository-2.0 change was clearly intentional but nothing from girepository-2.0 has been used yet, just the removal of gobject-introspection-1.0 compatibility. I could not get the version of girepository-2.0 in trixie to work with Liferea. Otherwise the tests pass and I've been running this on trixie for a few weeks now without issue.