Version-Release number of selected component: ppp-2.4.7-9.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /sbin/pppd pty '/sbin/pptp XX.XX.XX.XX --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-5149' ipparam nm-pptp-service-5149 nodetach lock usepeerdns noipdefault nodefaultroute noauth user XXX refuse-eap refuse-pap refuse-chap require-mppe mppe-stateful lcp-echo-failure 5 lcp-echo-interval 30 plugin /usr/lib64/pppd/2.4.7/nm-pptp-pppd-plugin.so crash_function: plugin_init executable: /usr/sbin/pppd global_pid: 5160 kernel: 4.5.0-0.rc7.git0.2.fc24.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 plugin_init at nm-pptp-pppd-plugin.c:328 #1 loadplugin at options.c:1636 #2 process_option at options.c:793 #3 parse_args at options.c:396
Created attachment 1142532 [details] File: backtrace
Created attachment 1142533 [details] File: cgroup
Created attachment 1142534 [details] File: core_backtrace
Created attachment 1142535 [details] File: dso_list
Created attachment 1142536 [details] File: environ
Created attachment 1142537 [details] File: exploitable
Created attachment 1142538 [details] File: limits
Created attachment 1142539 [details] File: maps
Created attachment 1142540 [details] File: mountinfo
Created attachment 1142541 [details] File: namespaces
Created attachment 1142542 [details] File: open_fds
Created attachment 1142543 [details] File: proc_pid_status
Created attachment 1142544 [details] File: var_log_messages
Similar problem has been detected: I tried to open vpn connection. Last time (a few feeks ago) it worked correctly. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /sbin/pppd pty '/sbin/pptp 213.169.1.116 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-16074' ipparam nm-pptp-service-16074 nodetach lock usepeerdns noipdefault nodefaultroute noauth user tiihmi refuse-eap refuse-pap refuse-chap require-mppe-40 lcp-echo-failure 0 lcp-echo-interval 0 plugin /usr/lib64/pppd/2.4.7/nm-pptp-pppd-plugin.so crash_function: plugin_init executable: /usr/sbin/pppd global_pid: 16088 kernel: 4.6.0-0.rc1.git0.3.fc25.x86_64 package: ppp-2.4.7-9.fc24 reason: pppd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
I've had this problem as well, but after installing the latest updates it seems to have disappeared. ppp is still ppp-2.4.7-9.fc24 but NetworkManager-pptp (which contains the nm-pptp-pppd-plugin.so library) has been upgraded to NetworkManager-pptp-1.2.0-0.4.rc1.fc24 .
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.