Wifi failed to create rfkill directory: Read-only file system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
High
|
Michael Vogt |
Bug Description
When using Wifi with Snappy, the system tries to start the systemd-rfkill service. This service does not exist in snappy.
● <email address hidden> - Load/Save RF Kill Switch Status of rfkill0rvic
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Tue 2015-09-22 18:28:38 UTC; 39min ago
Docs: man:systemd-
Process: 1447 ExecStart=
Main PID: 1447 (code=exited, status=1/FAILURE)
Sep 22 18:28:38 odroid systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill0...
Sep 22 18:28:38 odroid systemd[1]: <email address hidden>: main process exited, code=exited, status=1/FAILURE
Sep 22 18:28:38 odroid systemd[1]: Failed to start Load/Save RF Kill Switch Status of rfkill0.
Sep 22 18:28:38 odroid systemd[1]: Unit <email address hidden> entered failed state.
Sep 22 18:28:38 odroid systemd[1]: <email address hidden> failed.
This service gets automatically started, as soon as a wifi device comes up.
summary: |
- Wifi triggers not existing systemd-rfkill service + Wifi failed to create rfkill directory: Read-only file system |
Changed in snappy: | |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → Michael Vogt (mvo) |
Changed in snappy: | |
status: | Fix Committed → Fix Released |
I just found that /lib/systemd/ systemd- rfkill actually exists in snappy but fails:
/lib/systemd/ systemd- rfkill load 1
Failed to create rfkill directory: Read-only file system