Version-Release number of selected component: pacmanager-4.5.5.7-11.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/perl /usr/bin/pacmanager crash_function: emission_find executable: /usr/bin/perl journald_cursor: s=c7750b429cc44b9c8d643012327cbf24;i=2e791;b=960c3187b18541a2a08a26e8a0ee022b;m=26f2cb991;t=57449dab5f93a;x=3c08b02ea0970a22 kernel: 4.17.17-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 emission_find at gsignal.c:824
Created attachment 1478754 [details] File: backtrace
Created attachment 1478755 [details] File: cgroup
Created attachment 1478756 [details] File: core_backtrace
Created attachment 1478757 [details] File: cpuinfo
Created attachment 1478758 [details] File: dso_list
Created attachment 1478759 [details] File: environ
Created attachment 1478760 [details] File: exploitable
Created attachment 1478761 [details] File: limits
Created attachment 1478762 [details] File: maps
Created attachment 1478763 [details] File: mountinfo
Created attachment 1478764 [details] File: open_fds
Created attachment 1478765 [details] File: proc_pid_status
it's still happening on Fedora 29. Please do not EOL in two years Step to reproduce : close PacManager after some use, get a report that the app crashed. Every time There is a bug opened on github : https://github.com/perseo22/pacmanager/issues/63 And someone there pointed to this related perl bug : https://bugzilla.novell.com/show_bug.cgi?id=1067117 Please fix; it has been many years and just get closed without investigation.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.