Hide Forgot
libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: /usr/sbin/pptp 59.41.70.180 --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-2319 comment: I was trying to connect via pptp ... which doesn't work for me. I don't know why - this might be one reason. crash_function: __GI_raise executable: /usr/sbin/pptp kernel: 3.1.6-1.fc16.x86_64 pid: 2330 pwd: / reason: Process /usr/sbin/pptp was killed by signal 6 (SIGABRT) time: Thu 05 Jan 2012 04:50:38 PM CET uid: 0 username: root backtrace: Text file, 8719 bytes var_log_messages: Text file, 11766 bytes build_ids: :3ed9e61c2b7e707ce244816335776afa2ad0307d :9879d60a6b06b11e0732e312489946561b4e3911 :9d1209fc79304f03cc839de1c0036c61b48dfff8 :374add1ead31ccb449779bc7ee7877de3377e5ad :aa733447f84020c94a66814e501a36e248cbb43d dso_list: :/lib64/libutil-2.14.90.so glibc-2.14.90-24.fc16.4.x86_64 (Fedora Project) 1325771317 :/lib64/libc-2.14.90.so glibc-2.14.90-24.fc16.4.x86_64 (Fedora Project) 1325771317 :/usr/sbin/pptp pptp-1.7.2-12.fc15.x86_64 (Fedora Project) 1316187140 :/lib64/ld-2.14.90.so glibc-2.14.90-24.fc16.4.x86_64 (Fedora Project) 1325771317 :/lib64/libgcc_s-4.6.2-20111027.so.1 libgcc-4.6.2-1.fc16.x86_64 (Fedora Project) 1320067244 environ: :SYSFONT=latarcyrheb-sun16 :PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin :GIO_USE_VFS=local :PWD=/ :LANG=en_US.UTF-8 :KEYTABLE=us :SHLVL=1 :BOOT_IMAGE=/vmlinuz-3.1.6-1.fc16.x86_64 :_=/usr/sbin/pptp maps: :00400000-0040e000 r-xp 00000000 fd:02 37504 /usr/sbin/pptp :0060e000-0060f000 rw-p 0000e000 fd:02 37504 /usr/sbin/pptp :0060f000-00611000 rw-p 00000000 00:00 0 :0150f000-01530000 rw-p 00000000 00:00 0 [heap] :39ccc00000-39ccc15000 r-xp 00000000 fd:02 40804 /lib64/libgcc_s-4.6.2-20111027.so.1 :39ccc15000-39cce14000 ---p 00015000 fd:02 40804 /lib64/libgcc_s-4.6.2-20111027.so.1 :39cce14000-39cce15000 rw-p 00014000 fd:02 40804 /lib64/libgcc_s-4.6.2-20111027.so.1 :7ff499eda000-7ff49a085000 r-xp 00000000 fd:02 38069 /lib64/libc-2.14.90.so :7ff49a085000-7ff49a285000 ---p 001ab000 fd:02 38069 /lib64/libc-2.14.90.so :7ff49a285000-7ff49a289000 r--p 001ab000 fd:02 38069 /lib64/libc-2.14.90.so :7ff49a289000-7ff49a28b000 rw-p 001af000 fd:02 38069 /lib64/libc-2.14.90.so :7ff49a28b000-7ff49a290000 rw-p 00000000 00:00 0 :7ff49a290000-7ff49a292000 r-xp 00000000 fd:02 38103 /lib64/libutil-2.14.90.so :7ff49a292000-7ff49a491000 ---p 00002000 fd:02 38103 /lib64/libutil-2.14.90.so :7ff49a491000-7ff49a492000 r--p 00001000 fd:02 38103 /lib64/libutil-2.14.90.so :7ff49a492000-7ff49a493000 rw-p 00002000 fd:02 38103 /lib64/libutil-2.14.90.so :7ff49a493000-7ff49a4b5000 r-xp 00000000 fd:02 4838 /lib64/ld-2.14.90.so :7ff49a69a000-7ff49a69d000 rw-p 00000000 00:00 0 :7ff49a6b2000-7ff49a6b3000 rw-p 00000000 00:00 0 :7ff49a6b3000-7ff49a6b4000 rw-p 00000000 00:00 0 :7ff49a6b4000-7ff49a6b5000 r--p 00021000 fd:02 4838 /lib64/ld-2.14.90.so :7ff49a6b5000-7ff49a6b6000 rw-p 00022000 fd:02 4838 /lib64/ld-2.14.90.so :7ff49a6b6000-7ff49a6b7000 rw-p 00000000 00:00 0 :7fffb5c82000-7fffb5ca3000 rw-p 00000000 00:00 0 [stack] :7fffb5dff000-7fffb5e00000 r-xp 00000000 00:00 0 [vdso] :ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Created attachment 550955 [details] File: var_log_messages
Created attachment 550956 [details] File: backtrace
Running pppd through valgrind I get ==3477== Warning: invalid file descriptor -1 in syscall close() ==3477== at 0x5F8D670: __close_nocancel (syscall-template.S:82) ==3477== by 0x11DC1A: safe_fork (in /usr/sbin/tmp/pppd) ==3477== by 0x11DF9B: device_script (in /usr/sbin/tmp/pppd) ==3477== by 0x13B839: connect_tty (in /usr/sbin/tmp/pppd) ==3477== by 0x12C8DA: start_link (in /usr/sbin/tmp/pppd) ==3477== by 0x11C284: main (in /usr/sbin/tmp/pppd) It is very likely that the connection (and thus stdin/stdout) is closed at an unfortunate moment. This valgrind error doesn't look serious, but perhaps it hits something more dangerous when the timing is unfortunate.
FWIW, the pptp launched by pppd warns ==3486== Invalid read of size 4 ==3486== at 0x4080DB: call_callback (pptp_callmgr.c:83) ==3486== by 0x404044: pptp_call_destroy (pptp_ctrl.c:412) ==3486== by 0x4040FB: pptp_conn_destroy (pptp_ctrl.c:449) ==3486== by 0x408D13: callmgr_main (pptp_callmgr.c:297) ==3486== by 0x402817: launch_callmgr (pptp.c:505) ==3486== by 0x402971: open_callmgr (pptp.c:474) ==3486== by 0x401E98: main (pptp.c:375) ==3486== Address 0x53f4f10 is 0 bytes inside a block of size 12 free'd ==3486== at 0x4C2962E: free (vg_replace_malloc.c:366) ==3486== by 0x408E55: callmgr_main (pptp_callmgr.c:238) ==3486== by 0x402817: launch_callmgr (pptp.c:505) ==3486== by 0x402971: open_callmgr (pptp.c:474) ==3486== by 0x401E98: main (pptp.c:375)
Can you repeat this with pptp-1.7.2-14.fc15 (just pushed to updates-testing)?
I can't reproduce the crash on demand, neither with the old nor the new version. I get the same (slightly changed) valgrind warning with pptp-1.7.2-14.fc16.x86_64: ==3814== Invalid read of size 4 ==3814== at 0x4082CB: call_callback (pptp_callmgr.c:85) ==3814== by 0x404254: pptp_call_destroy (pptp_ctrl.c:412) ==3814== by 0x40430B: pptp_conn_destroy (pptp_ctrl.c:449) ==3814== by 0x409023: callmgr_main (pptp_callmgr.c:304) ==3814== by 0x402917: launch_callmgr (pptp.c:527) ==3814== by 0x402A71: open_callmgr (pptp.c:496) ==3814== by 0x401F68: main (pptp.c:394) ==3814== Address 0x53f4f10 is 0 bytes inside a block of size 12 free'd ==3814== at 0x4C2962E: free (vg_replace_malloc.c:366) ==3814== by 0x409174: callmgr_main (pptp_callmgr.c:245) ==3814== by 0x402917: launch_callmgr (pptp.c:527) ==3814== by 0x402A71: open_callmgr (pptp.c:496) ==3814== by 0x401F68: main (pptp.c:394)
Thanks - I've reported this upstream: http://marc.info/?l=pptpclient-devel&m=132586093126446&w=2
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.
got this problem on fedora 18
Got it again on F18, please reopen
Are you able to get a backtrace?
abrt-gui went directly to "problem already reported" where i got the link to this bug. But now the problem doesn't appear in the "not submitted reports" list nor the "submitted reports" list, even if selecting "show all problems". I had at least two occurrences of it. How to get them back and do the backtrace?
(In reply to comment #12) > abrt-gui went directly to "problem already reported" where i got the link to > this bug. > > But now the problem doesn't appear in the "not submitted reports" list nor > the "submitted reports" list, even if selecting "show all problems". > I had at least two occurrences of it. How to get them back and do the > backtrace? Don't know I'm afraid. The original backtrace dates back to F-16 and I'd really prefer to see a current one. Perhaps you'll have to wait until it happens again?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.