Description of problem: I was trying to close Pan after reading all new articles and it crashed. I reopened it, found that the articles in the last group were marked as unread. I marked them as read, and it crashed again. This time, when I reopened it, they were properly marked. Version-Release number of selected component: pan-0.141-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 3 cmdline: pan executable: /usr/bin/pan global_pid: 2281 kernel: 4.9.14-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000
Created attachment 1265525 [details] File: cgroup
Created attachment 1265526 [details] File: core_backtrace
Created attachment 1265527 [details] File: dso_list
Created attachment 1265528 [details] File: environ
Created attachment 1265529 [details] File: exploitable
Created attachment 1265530 [details] File: limits
Created attachment 1265531 [details] File: maps
Created attachment 1265532 [details] File: mountinfo
Created attachment 1265533 [details] File: namespaces
Created attachment 1265534 [details] File: open_fds
Created attachment 1265535 [details] File: proc_pid_status
Created attachment 1265536 [details] File: var_log_messages
Created attachment 1265537 [details] File: backtrace
Similar problem has been detected: Ever since I installed Pan on my F 25 X64 system, this happens every time I exit. It never did this on my 32 bit system. There is a report of this at https://retrace.fedoraproject.org/faf/reports/522761/ that's been there since 12/30/2014 and never formally reported or assigned. reporter: libreport-2.8.0 backtrace_rating: 3 cmdline: pan executable: /usr/bin/pan global_pid: 31439 kernel: 4.9.14-200.fc25.x86_64 package: pan-0.141-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: pan killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.