urfkilld segfault wifi function (Dell XPS 13 9350)

Bug #1764806 reported by J.D.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
urfkill (Ubuntu)
New
Undecided
Unassigned

Bug Description

With kernel 4.4.0-119-generic on Ubuntu 16.04.4 LTS (xenial) x86_64 and included intel_hid driver (which seems to be responsible for the key events), I get the following report when pressing the function key Fn+PrtScr which is supposed to trigger the wifi blocking state using rfkill interface via urfkilld daemon:

Apr 17 19:02:45 aton kernel: [ 387.963583] urfkilld[3119]: segfault at 18 ip 000055948349f46b sp 00007ffd26296730 error 4 in urfkilld[559483495000+19000]
Apr 17 19:02:46 aton NetworkManager[1099]: <info> [1523984566.0332] urfkill disappeared from the bus
Apr 17 19:02:46 aton kernel: [ 388.137360] rfkill: input handler enabled
Apr 17 19:02:46 aton kernel: [ 388.418242] rfkill: input handler disabled
Apr 17 19:02:46 aton NetworkManager[1099]: <info> [1523984566.3369] urfkill appeared on the bus

It seem that urfkilld crashes and gets restarted by systemd or similar. Nothing happens to the Wifi button state which can be shown via

rfkill list

0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

Another oddity is that the urfkill package in all Ubuntu versions is

0.6.0~20150318.103828

but upstream websites have

0.3.0 (https://www.freedesktop.org/wiki/Software/urfkill/)
0.5.0 (https://github.com/lcp/urfkill/releases)

only. Seems like almost abandoned software to me.

Since this was a distribution upgrade, I purged and reinstalled the package but without effect.

Any ideas?

Revision history for this message
Gerhard Gonter (gg-lp) wrote :

On my notebook, urfkill dumped core while starting the GUI causing it to loop in the GUI initialization, so I simply removed urfkill and did not install it again. I never missed that bugger ever since... (FWIW)

GG

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.