Description of problem: I was just trying to start Padre. Version-Release number of selected component: perl-Padre-0.90-10.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/perl /usr/bin/padre crash_function: boot_Cwd executable: /usr/bin/perl kernel: 3.18.7-100.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 boot_Cwd at /opt/ActivePerl-5.20/lib/auto/Cwd/Cwd.so #1 Perl_pp_entersub at pp_hot.c:2888 #2 Perl_runops_standard at run.c:42 #3 Perl_call_sv at perl.c:2766 #4 Perl_call_list at perl.c:4863 #5 S_process_special_blocks at op.c:7717 #6 Perl_newATTRSUB_flags at op.c:7681 #7 Perl_newATTRSUB at op.c:7354 #8 Perl_utilize at op.c:5139 #9 Perl_yyparse at perly.y:397
Created attachment 1014350 [details] File: backtrace
Created attachment 1014351 [details] File: cgroup
Created attachment 1014352 [details] File: core_backtrace
Created attachment 1014353 [details] File: dso_list
Created attachment 1014354 [details] File: environ
Created attachment 1014355 [details] File: exploitable
Created attachment 1014356 [details] File: limits
Created attachment 1014357 [details] File: maps
Created attachment 1014358 [details] File: open_fds
Created attachment 1014359 [details] File: proc_pid_status
Created attachment 1014360 [details] File: var_log_messages
Backtrace suggests you're picking up some non-Fedora perl code from /opt/ActivePerl-5.20, which is likely to be an issue.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.