Version-Release number of selected component: dhclient-4.2.5-7.fc18 Additional info: backtrace_rating: 4 cmdline: dhclient crash_function: vsnprintf executable: /usr/sbin/dhclient kernel: 3.8.6-203.fc18.x86_64 uid: 0 ureports_counter: 1 Truncated backtrace: Thread no. 1 (6 frames) #2 vsnprintf at /usr/include/bits/stdio2.h:77 #3 log_fatal at errwarn.c:64 #4 get_hw_addr at lpf.c:730 #5 if_register_lpf at lpf.c:104 #6 if_register_receive at lpf.c:224 #7 discover_interfaces at discover.c:872
Created attachment 740868 [details] File: backtrace
Created attachment 740869 [details] File: cgroup
Created attachment 740870 [details] File: core_backtrace
Created attachment 740871 [details] File: dso_list
Created attachment 740872 [details] File: environ
Created attachment 740873 [details] File: limits
Created attachment 740874 [details] File: maps
Thanks vochomurko ;-) dhclient seems to had a problem getting hardware address of "mon0" device. Can you show me output of 'ip a' command ?
I see. Now I remembered what I was doing and reproduced: The problem happened when I started wireless interface monitor with # airmon-zc start wlan0 which was "partially" successful because the wireless card was disabled in NetworkManager. Output: " Found 5 processes that could cause trouble. If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to kill (some of) them! PID Name 3055 avahi-daemon 3056 avahi-daemon 5001 NetworkManager 5008 wpa_supplicant 31251 dhclient X[PHY]Interface Driver[Stack]-FirmwareRev Chipset Extended Info K[phy28]wlan0 rtl8187[mac80211]-N/A Realtek Semiconductor Corp. RTL8187B SIOCSIFFLAGS: Operace není možná kvůli zakázanému rádiu (RF-kill) command failed: Device or resource busy (-16) (mac80211 monitor mode enabled for [phy28]wlan0 on [phy28]wlan0mon) " This time there appeared a "wlan0mon" monitor interface, don't know why it's not the usual "mon0". Then 'ip a' prints: " 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1e:8c:fe:be:e6 brd ff:ff:ff:ff:ff:ff inet 10.0.0.33/24 brd 10.0.0.255 scope global em1 inet6 fe80::21e:8cff:fefe:bee6/64 scope link valid_lft forever preferred_lft forever 35: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:16:44:9f:34:f1 brd ff:ff:ff:ff:ff:ff 36: wlan0mon: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ieee802.11/radiotap 00:16:44:9f:34:f1 brd ff:ff:ff:ff:ff:ff " Then running (not as a superuser) $ dhclient gives: " Can't create /var/run/dhclient.pid: Permission denied RTNETLINK answers: Operation not permitted RTNETLINK answers: Operation not permitted RTNETLINK answers: Operation not permitted Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen]) " Running (as a superuser) # dhclient makes no SIGSEGV: " RTNETLINK answers: Operation not possible due to RF-kill RTNETLINK answers: Operation not possible due to RF-kill " I know I'm doing all this stuff a bit wrong way (especially not running dhclient as a superuser) but user stupidity shouldn't cause SIGSEGV :-) Thanks!
(In reply to comment #9) > ... but user stupidity shouldn't cause SIGSEGV :-) Should be fixed with http://koji.fedoraproject.org/koji/taskinfo?taskID=5317202
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.