Created attachment 1953819 [details] core file Description of problem: After updating liferea-1.13.7-2.fc36.x86_64 to the latest liferea-1.14.1-1.fc36.x86_64 now liferea crashes on startup. I'm attaching the generated coredump as well as journald output. Version-Release number of selected component (if applicable): liferea-1.14.1-1.fc36.x86_64 How reproducible: always Steps to Reproduce: 1.dnf update liferea (Fedora 36) 2.open a terminal window 3.liferea Actual results: Segmentation fault (core dumped) Expected results: normal GUI application Additional info:
Created attachment 1953820 [details] journald output
I had to downgrade back to liferea-1.13.7-2.fc36.x86_64 to continue using liferea as usual.
Did some tests with the newer version: 1) Created another user on my system. Logged in as that user and was able to run liferea fine. 2) exported OPML from my main user and imported the OPML into the new user...all fine 3) removed .cache folder from main user, restarted liferea and crashes... 4) removed liferea.db from main user, restarted liferea and crashes... 5) removed plugins* folders, restarted liferea and crashes... In a nutshell, it seems there's something wrong with my user profile/environment. If it's not evident from the submitted attachments, and it's not recreatable, you may close bug. Thanks.
FEDORA-2023-2239e7d731 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-2239e7d731
This update works. Thanks!
FEDORA-2023-2239e7d731 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-2239e7d731` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-2239e7d731 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-2239e7d731 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.