snapd

rfkill should be included in the core snap

Bug #1671266 reported by Tony Espy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Undecided
Oliver Grawert

Bug Description

rfkill should be included in the core snap as it's a critical tool to allow introspection and toggling of kernel rfkill switches. Without this tool, if a device is soft-blocked, an admin has no way to clear it.

For more information on rfkill, see:

http://linuxwireless.org/en/users/Documentation/rfkill/

This bug is being reported as of core snap version 16-2 r1337.

Tags: hwe
Tony Espy (awe)
summary: - rfkill should be included in core snap
+ rfkill should be included in the core snap
Tony Espy (awe)
Changed in snappy:
status: New → Confirmed
tags: added: hwe
Oliver Grawert (ogra)
Changed in snappy:
assignee: nobody → Oliver Grawert (ogra)
status: Confirmed → Fix Committed
Maciej Borzecki (maciek-borzecki)
Changed in snappy:
status: Fix Committed → Fix Released
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Why does one need rfkill, when systemd-rfkill exists?
I see that currently core snap ships both, which is suboptimal.

Changed in snappy:
status: Fix Released → Confirmed
Revision history for this message
Oliver Grawert (ogra) wrote :

does systemd-rfkill ship the rfkill binary that some users use from existing snap packages via the network-control interface ?

can systemd-rfkill be used on low RAM systems without running a service that permanenty occupies RAM ?
(if you have only 128MB and your idling OS already occupies ~50 (which is roughly the current state of an idling core) you really dont want to lose any extra byte for your applications on top)

if both of the above is true, we would indeed not need to ship rfkill, if it is false, we should rather consider not shipping another service that runs on all systems even though only a few will need it.

Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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